Jira

Streamlined Project Management with Jira

Comments: Once we got past the learning phase, Jira significantly improved our project efficiency and collaboration. I highly recommend it for teams seeking to enhance productivity.

Pros:

Jira’s flexibility and customizable workflows are fantastic for tailoring project management to any team’s needs. Its integration with tools like Confluence and Bitbucket enhances collaboration, and the reporting features provide valuable insights.

Cons:

The initial learning curve can be steep, making it overwhelming for new users. Configuring advanced workflows might also be complex.

The project management tool for anything & everything

Comments: To me, Jira has a very intuitive user interface and can be used pretty much for everything that could be a project. I also like that "everything is an issue" setup.

Pros:

Jira is the perfect project management tool for me. It has very much customization options for projects to perfectly match what I want to achieve. I like the different project types and the templates, they are useful to just get started. It also integrates perfectly in Confluence and other Atlassian products.

Cons:

The Web interface is a bit slow, especially when navigation much through different tasks. Although the mobile app is super clean, there are some missing features overall.

Alternatives Considered: GitHub, Microsoft Azure, Microsoft 365, Asana and Notion

Reasons for Switching to Jira: Each of these products had some missing features or was overprices for what I use. Some of them also were too complicated to setup and/ or use.

Abysmal quality for sky high price

Comments: We chose the data center product after the server product was discontinued because our users were familiar with it and did not want to move to something new. From the first install, it was a nightmare. Other products - if you want to move from one server to another, you just back up on the old server and restore on the new one. With Jira - we had to buy a plug in to import and export it all. That's where we started to see the data integrity issues. The plug in knew to check where dependencies were missing, but Jira never flagged any problems when something was changed that broke a dependency. I can't even begin to describe the endless stream of issues we've been facing for months. Atlassian is after your money, not your satisfaction with their product.

Pros:

It supports two-factor authentication now.

Cons:

This company ignores every software development best practice. Unresolved bug and feature requests on their support site are often more than a decade old. They rely on plug-in developers to make broken things work, and the plug-ins generally come with a ridiculously high price tag. No admin tasks, from the simplest data validation to proper relationships between Assets objects, can be accomplished without work-arounds. And the workarounds generally break other things. Data integrity is a joke in Jira and JSM, especially in Assets. If you want your data to be clean and accurate, be prepared to learn a lot of code.

JIRA allows us to align the entire team in a single direction!

Comments: In general, I consider JIRA as a tool that after being adopted, we simply cannot stop using it. In addition to being very intuitive, coworkers can be informed or report the progress of activities from their mobile device.
It is excellent for involving all departments of the organization in a single direction, when we talk about executing a project with own, contracted or external resources.

Pros:

Jira is a very complete tool for tracking tasks, sharing work and, in general, for project control. Getting started with it was very simple and requires practically no learning curve. A very useful feature is that it can be adapted to almost any type of project and the use of templates makes it easier to adapt to the way we want to manage our resources. Notifications can be configured automatically or specifically for a person and we can share documents and photographs as evidence of our work.

Cons:

Its licensing may not be as flexible or accessible for small businesses. Therefore, it is important to consider the total number of licenses for which we must pay to use all the functionalities of the tool. It is important to understand that we are storing the historical memory of our projects and even many times contractually, we are obliged to keep this information available several years after finishing a project if the contract requires it.

Getting Things Done with Jira

Comments: We have single-signon enabled which makes it easy to access the tool without additional overhead. Collaboration with external partner is a lot easier with Jira as it helps keep all of us accountable for our work.

Pros:

There are many views available, ranging from the Kanban board, to the list view of all issues. This enables one to easily slice and dice issues any way one prefers. Also, the email alerts let you know when colleagues and partners, both internal and external make updates to the issues we are working together on.

Cons:

There is not much to dislike at all. We are able to make good use of the tool.

Alternatives Considered: Trello

Reasons for Switching to Jira: Other folks felt more comfortable with Jira than with Trello, though different tools make sense for different workstreams. Trello might be a better fit for smaller groups than for larger wide-ranging initiatives/deployments.

Power-house of a Work Manager

Comments: My experience with Jira has been very positive. It's an efficient tool for project management, offering great flexibility for tracking tasks, bugs, and progress. The customizable workflows and integration with other tools make it ideal for me to manage my projects and clients

Pros:

The ease of use for handling multiple projects and clients

Cons:

The tasks not being a more subset part of projects; I do not want them to become part of the workflow associated with projects.

Alternatives Considered: Trello

Reasons for Switching to Jira: It was more useful to me with its set of features.

One of the best Document MGMT tools in the market.

Comments: Very well designed, especially for medium-to-big team. Although for the teams in such sizes, a dedicated admin would be required to streamline the processes and keep things neat and under control.

Pros:

A robust and constantly-evolving application with lots of side features and integration options.

Cons:

The configuration can be confusing sometimes.

Reliable work horse

Comments: It simply works and we can rely on it. We use it for a lot of things.

Pros:

We can use it for multiple things in our business

Cons:

Sometimes you need to dig really deep in the user forums to find a solution

Jira the perfect too for Agile Teams

Comments: In our case, we are using for development teams and service IT team to share issues between ops and dev teams.

Pros:

It's the perfect tool to implement and manage an Agile methodology.

Cons:

The cloud price was raising on the last years.

Alternatives Considered: Asana

Reasons for Switching to Jira: Jira is more agile focused and it's really helpful

Great software project management platform

Comments: Great tool that can be used as a great software project management platform.

Pros:

I like how it fits the SCRUM process and is a useful backlog management system.

Cons:

I preferred and prefer Azure DevOps because of it’s automated deployments.

Alternatives Considered: Azure DevOps Services

Reasons for Switching to Jira: We wanted to try an alternative to DevOps to get something outside of Microsoft.

Finest application for the Agile software lifecycle

Comments: I use JIRA in all the Agile software development for classification and bug tracking for every user with Dashboards. I am satisfied with the JIRA features but I think JIRA needs to provide more integration towards CICD tools so that user can get more idea about the bug tracking.

Pros:

Easy to create Agile dashboards to track bugs in different development life cycle. We can also extract informations regarding the user specific tickets created and worked for any period of time. Also we can attache documents to gives an entire idea about the the bugs and time tracker in comment section provides how much time it takes to fix the bugs. In the software industry JIRA is one of the widely used Bug tracking platform. The idea of classification of tickets like EPIC,Task are very useful to identify the work load needed for that ticket.

Cons:

Need exact date and time of the ticket creation and comments when the ticket gets older, right now it describes like the ticket is "created more two weeks ago". JIRA also needs to integration with CICD tools for more information regarding the bug tracking and fixing. JIRA should provide a dashboard for each user how much time he worked on a ticket to track the overall work time and also it will be very easy for the Administrator also.

Alternatives Considered: Redmine

Reasons for Choosing Jira: Redmine lack Agile development life cycle features like an effective dashborad , exact classification of tasks and the work time logging.

Switched From: Redmine

Reasons for Switching to Jira: JIRA provided more features for the Agile development Lifecycle that suited our work environments and continues to give more features everyday.

Works great for Software Project Management, I wish the configurations were easier to set up.

Comments: We are overall very satisfied with the product as the user side of the things are very solid. The administration is quite complex and if you are doing it on your own, it will take a long time and a lot of hours reading their forums to get things right.

Pros:

The task tracking and overall reporting are pretty solid. If configured properly, you will not miss on any updates and can proactively resolve blockers.

Cons:

The configuration. They are very complicated and you cannot expect a new user to get it right and that's why there are dedicate people who set up this. We did it on our own and it took us a couple of months to get things right.

Alternatives Considered: Pivotal Tracker

Reasons for Choosing Jira: DeskPro was slow and confusing. It's the opposite - the admin interface is pretty solid while the user interface was a lot to wish for.

Switched From: Deskpro

Reasons for Switching to Jira: I have been using it for 6 years at different companies so it was the most comfortable choice to make.

The best option available, and a great value

Pros:

This software is so great, that you really don't need to train people on how to use it. Project managers will be familiar within a day, and users will understand it quickly because Atlassian put a lot of work into an intuitive user interface. This is the best option on the market if you want something that scales across your company without draining your energy. Not only will you run projects through here, but you can also setup all your standard business processes to run through here. Using the marketplace, there are some great extensions for Jira. We built our entire accounting team into Jira, and used it to know we were following through with our key daily, weekly, monthly processes. Using a scheduler plugin, we were able to create tasks, with subtasks, delegate them, follow up with progress, and print a custom summary report at month end outlining completion, completion date, user, and notes.

Cons:

You will likely want confluence or google sheets to keep overall big picture notes.

Alternatives Considered: Airtable, Basecamp and Asana

Switched From: Smartsheet

Reasons for Switching to Jira: All the features you need already exist. It's mature, but fully cloud, and feels fully cloud.

Jira : Collaboration of multiple people on same platform

Comments: Jira is an extremely useful product to work with a very large team and many project at the same time. Jira supports Agile and Kanban both the types of project management strategies.

Pros:

It's a very powerful tool. It provides many advanced features to collaborate with people. We can easily tracks things on Jira through our mobile devises and other gadgets. It helps us to plan the projects with tasks and sub-tasks.

Cons:

It is an expensive software compared to other open source software. I have worked with many software Jira is one of the most expensive product that we have used in our projects.

Alternatives Considered: Salesforce Sales Cloud, Asana and HubSpot CRM

Reasons for Choosing Jira: Salesforce was not suitable for our requirement and the type of business that we are doing. So, we have shifted to Jira and it's a very important decision for us to collaborate our exciting team.

Switched From: Salesforce Sales Cloud

Reasons for Switching to Jira: Jira is developer friendly, easy to work with, easy to collaborate with multiple people on the same task, have features to same attachments and issue tracking with notifications is very helpful to complete tasks on time.

User Experiance

Comments: My overall experience is this service does what it is supposed to do and that is to give you a ticketing system in the cloud that can integrate with thrid-parties and give our users access to the system no matter where they are in the world.

Pros:

The service which is the Cloud version is just as you would expect from the Helpdesk Type system. You have the ability to manage permissions to what access users have. You have plenty of third-party integration options. Also, one of the most important services is the ability to integrate Azure SSO.

Cons:

One of my pet hates with this service is the tickets themselves in that on some tickets their comments can get lost in that the system starts to hide the older comments so if you are in a rush to get some info you need to unhide those comments

Alternatives Considered: ServiceNow Customer Service Management and ConnectWise ScreenConnect

Reasons for Choosing Jira: We moved from the application due to the number of other third parties needing to get involved. The Jira is widely used so we decided to move the Project-Based tickets into a Cloud-Based Jira system. There was also a cost involved.

Switched From: ManageEngine ServiceDesk Plus

Reasons for Switching to Jira: We have used the On-Premis version of Jira in the past plus most of the Third-Parties we are dealing with also use the Jira Cloud Platform

Jira, the eldest son of the Atlassian family

Comments: Very positive experience and without any bugs. this has always favored teamwork which has benefited from a time consuming point of view.

Pros:

a complete and very user-friendly workflow management tool that allows you to optimize work times with a perfect management of all tasks, collaborators, project delivery times and more generally "who does what" on each single activity. Thanks to the easy connection with Trello it is possible to have a complete and easily accessible platform also from mobile for the management of team work. once discovered you will not be able to do without it because it has a free version available complete with all the features you need to manage even complex projects.

Cons:

I have been using this software for several years and I have never encountered a problem either at a technical level or at the interface with the different businesses that I have managed. Implementations are always welcome so I look forward to testing some new features that they will release in the future for now everything works great.

Alternatives Considered: Fullstory, Trello and Nylas

Reasons for Switching to Jira: It is a complete and easy to use tool in a team, especially with creatives and developers. Sometimes I integrate it with the use of other software that may already be used in agencies or private individuals.

Best at small scale delivery

Comments: Unmatched in capability and ease of use. Pricing structure makes it easy to make accessible to every business size. Integrations with online collaboration tools have made WFH seamlessly easy. People can overcomplicate how projects are built, so it needs at least one experienced or continuously curious employee to keep benefits > overhead.

Pros:

It’s highly customisable- can be as simple or as complex as you need (which means it will work for you and not you for it). Usually, with this though, come specialist roles that you need to hire for (e.g. ‘salesforce specialist), but jira has easily the most extensive publicly available knowledge base. Every question or issue you may ever have, someone has had (and solved) before. Excellent community that also ways has a step by step for you. Continuous intro of new functionality. Integrates with pretty much everything out there

Cons:

Not so great when required for large scale delivery. Planner tries to do this, but feels like it doesn’t have the same level of user insight as the rest of the atlassian suite.

JIRA - The monolith everyone uses

Comments: We use JIRA to plan monolithic projects across our organization and communicate with teams in multiple time zones and regions. We have a tier 1 tool plugin that allows our tier 1 support to escalate tickets for tier 2 and that is where we perform our work. I work indirectly with our JIRA administrator and project managers to support them while they support the JIRA platform for our organization. I have worked with JIRA in numerous organizations and while I've given it a mediocre score overall, it is a useful and irreplaceable tool overall.

Pros:

JIRA is an industry standard tool, due to this it's very well known and a colloquial metaphor for "tickets" in and of itself. JIRA is able to handle monolithic projects and the many related projects with regard to them. JIRA is very good at allowing and automatically building self-referencing tickets within it's comments and ticket parts, if you put a ticket title into a ticket it will automatically reference the actual ticket with a link. It is also very good at adding to existing tickets with related tasks, sub-tasks, and prioritization. JIRA also is considered in almost every third party tool with a massive volume of software that offers "JIRA plugins" considering it's high stature with the IT community.

Cons:

JIRA is "the tool" but it's not "a good tool" for every project and company size. JIRA is like other commercial grade products that just aren't designed for simple day to day use. While it opens up nicely and begins to make tons of sense in larger projects, larger organizations, and larger teams it often doesn't show the same beauty with simple projects and day to day ticket tracking. Additionally, the JQL language is ridiculous follows in the foot steps of many other proprietary languages that are only great for constant users of JIRA. While that's the implied scenario because as mentioned JIRA is "the tool" it's not always the case. When my day is split 20 ways, I have little time to sit down and do more than plug in a JIRA ticket number to get to the issue to investigate, review, get sign off on a fix, and apply. JIRA is also having what appears to be a lot of difficulties this year staying online with their new data center providers. I don't remember ever having these issues prior to their most recent move.

Review on Atlassian JIRA

Comments: Overall, JIRA does the job for our team and even though I am on the Systems Team, we ourselves are mostly users as well. That keeps the headaches in check (as things could be very frustrating when trying to administer the applications. See above for the reasons).

Pros:

A team needs a ticket/issue tracking system and JIRA Atlassian seems to be used widely in the industry. As a user, it's easy to use for the most part. Besides having the option of hosting the application in-house, it also has the Cloud edition so from the Systems Team perspective, there's no need for servers, backups, security, keeping the service up (with fault tolerance), etc.

Cons:

From the administration aspect of the software, JIRA still has a long way to go: 1) As an administrator, as far as I can see, one can *not* even do such a simple thing as change the Display Name for a user (I suppose it's a "feature" but I can't see why that's a good feature). Instead, an invite is sent out to the user, who can then set the Display Name after signing up. 2) As an administrator, one can login as another user to test permissions. That's normally a nice functionality for administrators. However, for some functionalities, while you are still logged in as another user, you suddenly go back to your normal identity. That's very confusing and thwarts the purpose. One potential good use is being able to login as another user to set/update the Display Name (see #1). 3) Setting permissions is not that easy. I tried to set permissions for an account that's used for scripting (using the REST API) but it seems very difficult (really, it should be easy) to get the permissions done correctly -- sufficient but minimal privileges. 4) The REST API is not great. The online documentation is often outdated and sometimes things don't work (with errors). Even when things run without errors, it might not actually do the thing that it's supposed to do (so you write the code for nothing when you expect it to work).

Perfect tool for large scale and small scale projects workflows

Comments: Great experience working with this tool and transforming the business workflows. Its valuable tool for any organization for managing all the business workflows.

Pros:

Jira is the great tool when comes to administratering the custom workflows. We were able to define and automate most of the workflows tasks thus reducing lots repetitive manual efforts. As an administration, we have so much of knowledge base available from Attlassian. Out of the box, we get generic yet useful workflows and features which can onboard most of the software and agile projects instantly.

Cons:

Able to import and export workflows from one instance to another Jira instance is missing.

Alternatives Considered: ServiceNow Customer Service Management

Reasons for Choosing Jira: More user-friendly tool

Switched From: ServiceNow Customer Service Management

Reasons for Switching to Jira: Cost and ease of use

Everything You Need to Know About Jira

Comments: Almost every software team uses a project management tool like Jira. The importance of a well-managed development process cannot be stressed enough. A streamlined workflow is vital to ensuring that a development project doesn’t spin out of control and that your client will always receive high-quality work. Being able to keep track of multiple projects, clients, and deliverables simultaneously is key to improving overall productivity as well as maintaining an airtight workflow.

Pros:

Pro 1: Easy Time Tracking One of my favorite things about Jira is its time-tracking feature. You can easily track which team members spent their time working on certain issues, giving you insight into how your projects are progressing. (This could also be a con if you work in a more collaborative environment). Pro 2: Easy Project Management Prioritizing tasks is an essential aspect of project management. With its dashboards, Jira allows you to prioritize projects by quickly identifying which are progressing well and which need help. With a quick glance at your dashboard, you can easily prioritize what’s next for your project teams.

Cons:

Con 1: Technical Issues Projects created in Jira have an issue type called technical that is often confused with bugs. Because issue types are pre-defined by default, it’s hard to use your own words to describe what a technical issue is. When you create an issue for a bug or technical problem, there’s no way to group it with other issues about similar problems so users can focus on problems across several projects at once. Con 2: Difficult to Get Support The biggest negative about JIRA is that it's tough to get support when you need it. This is due to Atlassian's heavy reliance on their community forums, which are frequently inundated with low-quality questions from new users. If you have a complicated issue, or your problem isn't being addressed in any forum threads, Atlassian's usually helpful but small team of professional service agents (PSAs) may be a better bet than waiting for help from other users.

A great planning tool for business processes used by agile teams

Comments: 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.

Pros:

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.

Cons:

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.

Alternatives Considered: monday.com

Reasons for Switching to Jira: I adore how straightforward the program is.

Enhancing Productivity and Collaboration with Jira Software

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

Pros:

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.

Cons:

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.

Powerful tool once you know how to configure it

Comments: This software helps us to follow the process the team agreed to, and see the progress on issue and sprint level. We manage several projects there.
JIRA by itself is a perfect solution for IT teams when it comes to managing projects. Not only you can create issues there, but also you can build workflow this issue goes through. It is perfect to see the bottlenecks of your process. Scrum and Kanban are supported. In case you need some enhancements, there is an add-on market available, where you can find a big amount of third part addons available, either paid or free. Paid once have a trial period during which you can see if this is really what you need for your business.
Along with JIRA we use other Atlassian products, such as Service Desk and Confluence. Easy integration with these, makes our daily job much easier.
I advice my customers to use JIRA for their business. There are several types available: Cloud and Server. Each one have their own payments depending on the size of the users. However, in some cases price might become an obstackle.
In my opinion, this application can become really helpful if it gets into right hands.

Pros:

This software can be used by any type of company. I have configured JIRA to be used by publishing company, by law firm, and of course, IT companies. And it was possible to make everyone happy with what JIRA provides. Even though sometimes it was hard to teach people how to use it, after a month or two they could not remember how they lived without it.

Cons:

Recently JIRA started to update its design. My users complain about new design, I get crazy when I can't find things. And JIRA doesn't want to stop at that and is updating its design further and further. I would really prefer that they look through bugs that were raised on comunity portal and do something regarding new features instead of doing design updates.

Jira is a project management software

Pros:

Jira is a task administration programming that is very mainstream among numerous organizations. With an extremely high score of 9.4/10 and client fulfillment at 99% it is as of now one of the best 3 best task administration arrangements looked into on our site. The primary spot in this class is held by Wrike which has an aggregate score of 9.8/10 and is the champ of our Best Project Management Software Award for 2017. You can experiment with Wrike for nothing here. You can likewise contrast Jira and Wrike and see which one is better for your organization. Jira is intended to enable clients to catch, dole out, and set needs to their work. It enables you to deal with the entire procedure of use improvement ensuring that everything is secured, from idea to dispatch. Its straightforward, natural interface empowers joint effort with partners and enables you to take care of business in a viable way. Jira tailors itself to fit to the necessities of the business and gives fantastic help to finish everything. The level of customization enables the product to properly fit distinctive business needs. This product can be utilized by an organization. I have designed JIRA to be utilized by distributing organization, by law office, and obviously, IT organizations. What's more, it was conceivable to make everybody content with what JIRA gives. Despite the fact that occasionally it was difficult to encourage individuals how to utilize it, following multi month or two they couldn't recollect how they lived without it.

Cons:

Jira is an amazing programming, however with a lot of capacities comes a large group of devices and assignments to learn, especially for new clients. As of late JIRA refreshed its outline. My clients whine about new outline, I get insane when I can't discover things. Furthermore, JIRA wouldn't like to stop at that and is refreshing its plan further and further. I would truly incline toward that they glance through bugs that were raised on comunity entryway and accomplish something in regards to new highlights as opposed to doing configuration refreshes. It is imperative to realize that Jira gives us awesome help to the client, and their consideration is a need, however ordinarily they don't figure the issue. It is a component to survey in Atlassian. - The prologue to Jira's reality is required to be as mysterious as its interface and execution. Actually it is intricate to fabricate channels and move around in the application when the client is new. - You need to run a right download of the reports toward the finish of the month or toward the finish of the week, the reports are conveyed in spreadsheets, however with an introduction that fails to impress anyone, thusly, when setting the dates they ought to have pretty much days so you can play out the download effectively.