If you are looking a tools for ticket and escalation, Jira is the best for you.

You can separate those prioritize ticket.

Sometimes there was a lot of updates with Jira.

Our preferred project management tool these days is Jira. For our team, it functions as a kind of central nervous system, keeping everything visible and orderly. The Kanban boards are an excellent tool for visualizing process, and the collaborative elements facilitate teamwork. Without a doubt, Jira aids in keeping us responsible and on course, which eventually results in meeting deadlines and surpassing expectations. Although there was a slight learning curve at first, the increase in quality and efficiency that we have observed makes it well worth it.

For our team, Jira has been a project management lifesaver. Our workflow is kept quite clear by the Kanban boards, and it is extremely inspiring to watch jobs go from "To Do" to "Done". Additionally, since everyone is in agreement and can readily monitor progress, teamwork is a snap. Jira helps us stay accountable and organized, which is very helpful in meeting deadlines and producing high-caliber work.

For our team, Jira has been a project management lifesaver. Our workflow is kept quite clear by the Kanban boards, and it is extremely inspiring to watch jobs go from "To Do" to "Done". Additionally, since everyone is in agreement and can readily monitor progress, teamwork is a snap. Jira helps us stay accountable and organized, which is very helpful in meeting deadlines and producing high-caliber work.

The thing I liked most about JIRA was it's focus on supporting software development protocols (as a software business).

However, the system is clearly not meant for general project management, especially outside of software development, so there are probably better options.

some of the best features are: 1. Task creation and their category (analysis task, execution tasks , bug etc) 2. Tracking of each tasks using kanban board 3. Effort Estimation of tasks 4. The report like burn down chart.

1. Sub tasks (e.g Defect sub tasks) should also have points to track the time taken by each sub tasks. 2. Macro creation to get some graph created for managers should be easy to configure. 3. May be a common forum where we can go and ask our query.

JIRA has a basic building block which is the "Issue". On top of that you can build like LEGO additional functionality. You could use JIRA for pretty much everything that needs some sort of tracking. There are customizations and automations that will transform the way a team works.

The API could be better. Automating some tasks at scale needs to be supported out of the box.

I love Jira's customizable workflows. I have leveraged this key Jira provision to setup triggers within my departments software project management processes. This triggers enable my team automate minor , repetitive tasks thereby saving us critical work time.

Jira is not an intuitive project management software. This lack of intuitiveness does create problems for beginner users, especially those who have very little experience using a project management software.

Jira is a very detailed tool. There are many ways to track, label, and route work.

The tool is fairly complex to use much less administrate.

We love using JIRA—it's been a game-changer for our team. Sure, there's a learning curve, but the customization options and integration make it worth the effort. It's become our go-to tool for keeping projects on track and everyone on the same page.

JIRA is awesome for keeping track of projects and tasks. You can tweak it to fit your team perfectly, and it plays nice with other Atlassian tools like Confluence. Plus, the reports and dashboards give you a clear picture of how things are going.

It can be a bit tricky for newbies to get the hang of JIRA, but once you're in the groove, it's smooth sailing. Some folks wish the interface was a tad simpler, and costs can add up if you're not careful.

Mix with an extensive variety of outside devices and administrations, improving cooperation and efficiency

It can be costly for larger groups or associations, particularly when considering additional items and high-level elements.

I use it to coordinate large spaces . I use it in developing my own product and I use it in creating my own boards. I use it a lot and find it easy to use

I like how easy it is to coordinate between large spaces. Capable of diversity in project management. When you use it every day, you will notice how easy it is

Sometimes the file size is limited for downloading. Sometimes using the filter system is difficult

I love JIRA. I use it professionally and personally. Even though it is primarily a task manager for software development, I have found that it is flexible enough to be used for all sorts of projects. It is amazing how customizable it is; you can configure your project settings to your already existing workflow, whatever it may be. While the initial setup can be time consuming, once you have your settings configured, using the tool is a breeze. It takes seconds to create tasks, start springs, evaluate progress, etc. I find that this makes JIRA standout from other task managers. In most cases, if the software allows for detail-oriented task management the process of inputting and tracking the tasks themselves is cumbersome. Entering and tracking tasks should not have to be another time-consuming task! The JIRA web application is also excellent, making it easy to enter or track tasks on-the-go.

I think there is a lot of potential with Jira's NextGen projects, however, the software rollout has been uneven and often not well documented. I wish this process would have been better thought out to make transitioning to NextGen projects smoother.

My overall experience is excellent, it is the best project management software ever. I have used a few others in the past, but there is none that can compete with JIRA. with a integration of slack, confluence, it is very hard to refuse.

1. It is very flexible and fitted really well with agile development work. whether you are using kanban or standard sprint planning work flow, it supports all of those. 2. It is extremely useful to do project planning and creating stories, they will be saved in backlogs and you can access them with weight, estimate and priority. 3. It is quick to create a bug ticket to track bugs. 4. It is very easy to plan for a new sprint, by adding task, stories from the backlogs, it helps with the total points you want to target for a particular sprint, it automatically sum up the story points and make sure you don't over plan. 5. great report tool to help you analyse the project completion and nice burn down chart as well. To help the team retrospectively go back and review.

1. It is a big over complex by providing such flexible functionalities. But it is worth the time and learning curve. 2. As a developer, I don't have to pay the bill. But it is not very cheap if you have a large development team, the bills add up quickly.

Overall, JIRA can work. It seems to require knowing what you're doing - including understanding Agile theory, your team's preferences, and how deeply you want to use the myriad features. This is not necessarily a bad thing, of course. If you don't know how Agile works, maybe take a class and figure it out. That said, most of the people I've worked with don't have the 20+ years of process study that I have undertaken, so JIRA is configured very lightly or customized to a point where it becomes a hindrance. The UI could really stand some updates for consistency and - yes - some hand-holding for configuration.

JIRA certainly has a lot of features that should make Project Management easy. The mobile app is adequate, and the web site works well enough. There are a whole lot of places to enter data, which ends up being a bit of a downfall. When JIRA is set up well, it does support PM. When it is used as a vanilla Agile product, I think it falls behind other offerings.

JIRA has so many configuration points that it takes forever to get it working properly for your team. They have also been changing the UI a lot recently, which has obscured where some data is, which - predictably - has slowed down our use. If JIRA could get a more consistent UI, I feel it could be a much better product.

I love JIRA because I am an organizer and I spend the time getting it right. But you need that kind of commitment for the best experience.

The powerhouse controls that allow you to configure exactly the solution you need. JIRA is unmatched in customization. For controlling workflows, getting status updates and clearly understanding what's on your plate, JIRA is amazing.

The use of JIRA without properly configuring it. Without that commitment, JIRA can be offputting and seem like a heavy mess of a system. You need to remove what you don't use, need to set everything up for individuals and you need to educate your team about how they can use the system. It's so open that it can overwhelm people without management.

I'll focus on the experience of moving from JIRA Classic to Next Gen project types. Basically, over 19 years of existence, Atlassian made JIRA so customizable, that it was difficult for new users to get started. You had to spend months learning the platform just to make simple changes to process management. So Atlassian started over with Next Gen projects. Next Gen projects have some cool features like a road map. Even though I'm experienced with Classic, I decided to try Next Gen. 95% of the time, it works fine. However, there are frustrating limitations: * Workflow transitions rules are very limited. Next Gen allows transition to any status. * Custom fields are project-levels, so moving issues between projects is a pain. * You can only do Sprints or Kanban * Epics are just grouping issues. They don't do much else and don't show on the board. * Single board per project

* Allows the issue flow to be perfectly configured to match your software development practices. * Highly customizable process management - define the properties of issues and how they transition between states. * Integration with many other products, like Slack & GitLab

* "Next Gen" project type lacks many features of Classic projects. * Classic Project configuration is full of bloated features and complexity * Next Gen projects sometimes have frustrating bugs and limitations that don't get fixed for years. * Issue transition between Next Gen and Classic projects is not smooth (custom properties don't carry over)

Overall, I really like the flexibility that Jira provides. The one feature that I most appreciate when I use another PM tool is built-in support for Fix Versions. Being able to assign a fix version for a sprint and for each build, makes it easy to see all the tasks and bugs that are in a given full release or an individual build.

A lot of folks, especially artists, have a general disdain for the Jira UX. It is not as ergonomic, clean, and tactile as Trello or Basecamp. I would love it if there were a way for Boards in Jira to be as simple and powerful as boards in Trello.

My overall experience with Jira is good and I do not plan to switch to other tool right now.

I like that I can really easily navigate between the projects because I am in multiple projects at once. I really like the possiblity to customize a lot of things, mostly the kanban board lanes and tickets details. I love linking feature, I find it really useful and I use it a lot. What is very important to me is also the Tempo application and I like how it's integrated in Jira, so I can really easily log my time into proper tickets. In our company we also use the Bitbucket and Confluence and I really enjoy that I can easily create feature branches, commits or pull requests from Jira itself. I also like the report tools to control my overall work.

I have a lot of diffuculties with Tempo application search issues feature. Since I am participating in a lot of different projects it is really hard to search proper ticket, neither using ticket code nor ticket name is not functioning good enough. Sometimes I feel also overwhelmed with the amount of features which I don't use at all and I am getting lost in the user interface.

JIRA is easy to use and great for managing work tasks on a project, however customization options are often only available to admins.

Our company uses JIRA to manage work tasks. It has all the important features for assigning work to team members, tracking how long each task takes, notifications, capturing comments and hours worked. The tools allows for the flexibility to create your own JIRA ticket types or categories, with any kind of number of input fields. Data fields may be dropdown boxes, tags, values, or free text. Fields inherently have the ability to recognize hyperlinks and add those in once you type out a link, and it also recognizes JIRA links, such that if you enter a JIRA ID tag, it automatically creates a hyperlink to that JIRA entry. JIRA supports Agile development schemes and tickets could be easily tracked through a JIRA Dashboard. JIRA filters are also easy to use. You may use the basic query that provides you with simple dropdown fields for common elements, or you can create more advanced queries using JQL.

Being a JIRA user can be limiting as you only have the ability to enter data for the fields that are currently configured. You have to go through IT or the admins for any form of customization such as adding/removing/hiding fields, setting what kind of text format is in each field (e.g. plain text vs rich text) and modifying which fields are required vs optional. When you have rich text formatting, sometimes it can be frustrating getting the text to show up the way you want. The workaround for this would be to use the Text tab instead of the Visual tab so that you can modify the formatting tags.

My experience has been great with JIRA and I have setup the product in my last two organizations. In my current role, the entire company has moved all their projects to JIRA. Despite some pesky UI bugs here and there, JIRA does everything that I need and has become a critical piece of my day-to-day work. It's never easy to build a product for product people, but JIRA has found a way to do most of what I need. I only wish the business would invest a bit more effort into their support team, but since many companies are already using JIRA, the internet has become a great substitute.

JIRA gives me so much functionality out of the box. Within five minutes, I can create a board and invite my whole team to start working with me. It doesn't take long to customize your presentation of work to make it specific to your business. It has become the standard for the industry and with good reason; JIRA gives me everything that I need to track performance and ensure a timely release.

There are occasionally some annoying bugs that will present themselves, but it's never something that really prevents me from using the product effectively; usually it's an annoying UI bug that looks messy or ugly. For the most part, many of the people that complain about the product just don't know how to use it 'as is out of the box'. The more configurations you try to make, the more problems you can create for yourself. Aside from this, their customer service is quite lackluster and it often takes days if not weeks to hear back from support - usually the bugs are fixed before you even get a response.

We've been using using Jira since the begining of the company about 5 years ago and we are happy with it. Their integrations with bitbucket and other atlassian software is also a plus for us. It delivers almost everything a software company needs to develop projects, and you can find almost everything else in their marketplace. However we are likely going to change software soon due to their pricing jump after the "startup" tier.

Jira is an incredibly large and flexible tool to the point that you can virtually have any kind of project - software or not - managed inside it. But though it is large, it is also relatively simple to being with and can accommodate simple workflows even for smaller teams, with some neat ready-to-go templates. But its abiity to grow into a platform that can support a large corporation is amazing. Scalability is definitely their main power. Jira also bennefits from a very large marketplace of plugins that can bring more functionality and fit the granular specificities of each company or project. It also has a very cheap pricing for smaller teams.

Some basic functionality if just not there, which is rather unbelievable considering the size of this tool. For example easily planning a sprint, doing capacity tracking or even moving or changing issues can be very difficult and you may need to resort to plugins in their marketplace (with their own pricing). Some of the more advanced functionality (like workflows) is a bit complex and confusing and requires quite a bit of studying. Their pricing after the first tier (for startups) is just unbelievably expensive. It's a jump from $10 to $1000 when you add your 11th team member. Because of this we will sadly not keep using the software after that threshold.

I started project management with this in my toolkit and it has remained my favorite ever since. I have seen other options such as Kanbo or Monday, I believe Jira and its related ecosystem remains far superior. Its pricing scheme is pretty good as well, you can try it for free, adopt it in small teams almost free (10$/m) and can scale it up transparently. It gets pricier when it comes to enterprise grade, yet that is the norm and i believe it is money well spent.

The software is made around the idea of AGILE collaboration on projects for the entire team. It brings transparency to the processes and is a great information radiator for the entire team. It facilitates commonly used methodologies such as SCRUM and KANBAN and makes project management significantly easier. It is also very versatile and adaptable to particular needs. Although the standard fields are great, you can also create your own to fine tune your processes. Workflows are also highly customizable, giving the user-base great flexibility on how work is set up. Based on this, teams which work in areas not related to software development can also reap the benefits. I've seen implementations in recruitment, data analysis and more. Another great feature is its integration compatibility with other ecosystems such as Microsoft's which makes it easy to pick up. In terms of services, Atlassian offers multiple ways teams can use Jira: Cloud or Self-managed (Server or Data Center) making it an adaptable offering that can withstand the highest level of corporate security scrutiny. Another great feature is the marketplace which contains a great number of apps that provide added capabilities to the app. Last but not least, Atlassian has developed an entire ecosystem geared towards solving projects (especially software ones)like: Confluence (Info silo), Bitbucket (code management), Service Desk and more.

The plethora of fields and customizations available can make a new user feel a bit overwhelmed. In this regard, it takes a bit to get used to it. The interface could use a revamp to make things cleaner, clearer and more crisp for the more casual user at least. (ex: easier to find timekeeping, task transitions, new task coloring schemes and more) The workflow engine can also be upgraded to be more user friendly and provide more administrative options (create, apply, delete, manage versions) The security administration section also needs a revamp in terms of adding or removing users, groups, roles into or from project (ex: if you create a new group, you can't bulk add it to all existing projects without some scripting in the CLI)

Jira is an incredibly powerful tool that takes administration investment to really harness its power - identifying or designating a "Jira Champion" would be necessary, IMHO, for companies with a user-base larger than 75 people. While I understand where others may not be so keen on the time it takes to implement and customize, professionally, I am a believer in the power of Jira now and as we continue to grow. I don't see us moving away from it, even with the additional investment in Jira education, any time soon - its power is unmatched in the space.

Jira is *incredibly* versatile. You can customize almost every aspect of your Cloud instance, Project, Boards, & Workflows to fit nearly any use case, and across multiple departments. Permissions to your Jira instance can be restricted at a very granular level if need-be, but can be more broad if the occasion calls for it. Additionally, and probably the largest reason we transitioned from enterprise Jira to a Cloud Jira instance is the pervasive availability of integration across the market. Speaking of market - Jira has a growing 3rd-party market that offers enhancements to the Jira platform that Jira does not natively provide or are too complex for an untrained Jira administrator to script themselves. Of those that are "approved" by Jira, we are extremely happy with the breadth of functionality, integration and ease of use. With all that I do have to say that our favorite thing with all project leads is Jira Automation. Once you understand the "SmartValues" language that automation runs on, the use cases for automation are truly endless. It is one of the many strong features from a project management perspective.

Jira takes a village. Atlassian has an incredible resources in the "Atlassian Community" and they do a great job of having experienced users there to answer questions but, because each instance can be set up so differently, the actual customer support request portal is limited to bug fixes. As a result, much of my time administering Jira is spent researching how to fix a roadblock or how to modify permissions - a lot of "learning by doing". Generally speaking, Jira can be difficult to use from an administration perspective, *but* for the purposes of moving ticket along, the UX is pretty good and the UI is fairly intuitive.

Jira differentiates itself from competing project management software by providing robust capabilities like issue tracking, project planning, and workflow customization. It is also very adaptable, enabling teams to customize their workflow to meet their unique requirements.

It comes with a ton of functionality by default. It contains several levels (Teams, Projects) that may support the structure of the entire business, creating just the correct amount of separation while also allowing for the proper linkages between the various teams inside the business. May be easily integrated with the entire Atlassian ecosystem (Bitbucket, Confluence), and I highly encourage doing so because you'll have a ton of places to store any piece of your project (code, backlog, sprints, documentation). It provides you with all the tools you need to manage any Scrum or Canvas team, albeit I must stress that you will benefit more from adopting Scrum. It makes for incredibly inventive automatic build ticket systems and is simple to incorporate via code.

It's expensive and difficult to say whether it's the best tool for tiny independent teams when there are many free choices available that can manage numerous users. That is in fact the best option for businesses, but for low-budget teams, it's definitely safer to use a free alternative with no membership cap.

It simplifies project management, issue tracking, and agile development, resulting in increased productivity, faster delivery, improved collaboration, and data driven decision making.

It has some really useful features like customizing how you work, support for different ways of managing tasks, and keeping track of your work. It can also connect with other tools you use. While it's powerful, it might seem a bit tricky at first. Making it work smoothly with the tools you already use depends on how complex your setup is and how familiar you are with the software. But the good news is, Jira gives you lots of options to connect things together. You might need some help setting it up perfectly, but it can be a valuable tool for getting work done efficiently.

Some people might find It a bit tricky when they first start using it, especially setting up projects and making custom workflows. It's become easier to use over time, but it can still be a bit challenging for newcomers or those who aren't tech-savvy. Making it work smoothly with the tools you already use depends on how complicated your setup is. Sometimes, you might need help from experts to make everything fit together perfectly.