Jira Reviews

Jira makes it very easy to make sure no aspects of a project are overlooked or skipped when moving with speed within our organization! Every step is documented and visible, keeping organization throughout time sensitive projects!

It took me a bit to understand the different dashboard views within Jira, jumping to see just my tasks, all projects I'm apart of, and kanban views. I know it well now, but I remember some initial frustrations with that when first learning the system

We use JIRA online and it's dead simple to create and manage complex tasks. I love the ability to integrate with great packages like Confluence (which is SOOOO much better than Slack!).

Getting new employees up to speed on using the software is more time consuming that it should be. I'd prefer a more intuitive UI.

Jira is an immensely powerful issue management tool. It's JQL language provides ultimate flexibility to satisfy the needs of all roles on a product/project team. It's easy to use (if agile concepts are familiar to you and semi-intuitive if they're not), easy to deploy (especially if you're using Jira Cloud) and easy to integrate with.

The pricing model for add-ons. You could have a 100 users registered to your Jira instance, have an add-on that is used by a small handful of power users, and still be paying a license fee for all 100 users. Very annoying!

I love Jira's ease of use. Jira allows our staff and business partners to request from us using Jira Service Desk. Engineers track their effort using Jira Software. We use the default settings for the most part and that works great for us. There is no need to train anyone on how to use it because everything is self-explanatory. That cuts down on confusion and allows us to get/enter accurate information.

It is slow. It is very slow at times. Jira's makers - Atlassian - have not paid much attention over the years about its slowness. If you are into full-fledged project management, portfolio planning and more, you will have to buy add-ons to get additional functionality within Jira. Did I say that Jira is slow? While the ease of use saves time in accurately recording information in Jira, all that saved time is wasted away waiting for pages to load.

The ability to manage tickets day to day was a must. Some of these were coming from external parties and others internally. We ended up using it across the company in many departments so the ability to have multiple projects was a must.

Cloud version support for plugins and customisation is limited to only the basics. Its not possible with dive in to it inner workings and develop your own without tapping the APIs externally.

1. Different user roles can be defined to allow for segregation of duties.
2. Epics can be defined to assist with long and intermediate project planning.
3. Duration of sprints can be defined according to project requirements.
4. Statuses for user stories can be used for tracking progress as well as workflow management.
5. Allows for bulk import of epics and user stories which can fast track administrative tasks where this information has been captured elsewhere e.g. CSV format

1. Only users from within the organization can be assigned to tasks and user stories. This can cause unnecessary delays where external users need to provide urgent input or contribution.
2. Statuses (user stories) cannot be defined specifically for a board where multiple boards exist within a project.
3. Only two types of users can be assigned to user stories, which are assignees and reporters. JIRA does not allow for multiple users (assignees) to be assigned to one user story.

It's rich in features it offers and it's amazingly configurable, two organizations can have Jira installations that are nothing alike!

It's not a big issue for me, but I think they should offer more best practices in terms of templates for less experienced users to save them from headaches - they are already taking steps in this direction.

Since it's a very large product there are some inconsistencies, doing the same thing in two different parts of Jira can feel like a very different experience.

Jira is the most professional ticketing solution I found so far. It is by far the easiest to use and is the golden industry standard.

Some options related to sprints can be hard to find in the context menus, but once you know where they are it becomes much easier to use.

One of its strengths is its flexibility and customization. Jira allows teams to create and track issues, assign tasks, set priorities, and monitor progress through various workflows and dashboards.Another advantage of Jira is its integration with other tools and platforms. Jira can integrate with tools like GitHub, Bitbucket, Confluence, and many others, which makes it easier for teams to manage their projects and collaborate seamlessly.

One of the main criticisms of Jira is its complexity. Jira has many features and customization options, which can be overwhelming for new users. It can take some time to learn how to use Jira effectively and configure it to suit your team's needs.Another potential challenge with Jira is its pricing. While Jira offers a free version for small teams, its pricing can be relatively high for larger organizations or teams with more complex needs. Some users may find it difficult to justify the cost of Jira compared to other project management tools.

Jira helps team discover agile foundations with the guide of a scrum master or project leader. The sprints provide guardrails to teams take smaller chunks of work. Jira provides a centralized location to work in and can reduce the amount of communication gaps.

The greatest opportunity Jira has is that the user experience is rough in the fact that the product needs in-depth training to properly use it. For example, there aren't any youtube tutorials or best practices documents on why the end user would use label or a component. Most project leaders I know do not have a standardization why they use that and it causes confusion on project teams. The product isn't a plug and play, it is more that any user will need several lessons on simple actions such as creating a story, creating a Jira board, and creating Jira JQL. At the end of the day, there is a steep learning curve for this product and that increases the resistance for enterprise teams to go agile.

Features such as Scrum boards, kanban board, sprints, and backlogs are great for teams who follow agile methodology. We can customize workflows, fields, and issue types as per our needs. Most important feature is that it enables us to track the project progress in realtime. In addition, it is compatible with many external apps and facilitate the smooth workflow.

Extensive features and customization options can make the initial setup complex, especially for newcomers to project management tools. Its lacks built-in idea management functionality, we need to use some additional tools for brainstorming and concept development. Also, the pricing seems to be bit high and it may not be an affordable option for small teams or startups with limited budgets.

Jira is clean and it is simple yet powerful. You can use it for your basic ticket workflows from the get go and expand as you grow or the tasks you wisch to cover branch out. It is easy to customize the ticket views to contain the information you want to use and avoid cluttering. The Workflow editor is one of the most powerful I came across in all my professional career. It might not seem so much of an importance but believe me, when your business grows unexpected necessities will arise and you will suddenly be required to track tasks you never though about. Jira will have you covered and allow you to add different task types which traverse task-type specific phases and have corresponding stati. Also you have all the world of notification and responsibility tracking ping-pong covered as you go. Two further things are woth mentioning: First the Atlassian World (the Wiki Confluence and build system Bamboo and many other products) integrate flawlessly and it actually really makes using them fun. Jira is one of the tools, that make you smile when you are required to use it no matter the task to track, its jus smooth, convenient and above and beyond provides a rich ecosystem for free and commercial plugins even for rather exotic use cases.
Also, the license Model behind it scales fantastically. When we introduced it we were a small company with 8 people (we are now going strong towards the 200) and it was critical to keep cost for our tools reasonable. Jira got us covered.

When we scaled, the License was not as flexible in higher user tiers as it was in the lower ones. Also once upon a time an update went wrong and we had to invest a bucketload of time and brain power to get everything back up to speed. We did run jira on premise and hat some custom plugins so there might be some of the tripwires: In case you use plugins they must be available in the version you wish to upgrade to and this might require some research prior to updates. Also, you can make a science out of the workflow and notification configuration. In case it is not documented well when you do it it might get you into trouble.

Jira is highly customisable, and also has plugins. It allows you to monitor your projects and provided granulated access to individuals. You (or your admin) can set roles for the project and associates those roles to certain activities and then associate the roles even further to individuals.

You can organize your tickets in sprints and releases as well as monitor workload and task assignment to your team during sprints (or whatever other form of software delivery you wish to choose).

Pricing model. Currently, you have a choice of server vs cloud setup. If you have a team that can maintain the server instance, I'd recommend going to server because you have a lot more plugins you can use on server and you can set it up the way you want. The best thing is the licenses are a one-time cost, as opposed to lower, but monthly and forever costs on the cloud portion.

The other thing that is to be considered is that the plugins you choose need to have the same level of range for hte user count. i.e if your jira is for 101-250 users, all your plugins will need a license level of the same range, i.e 101-250 users. Something to consider if you are thinking about moving to Jira.

Jira is a fantastic tool for managing projects. It is the finest choice for managing agile projects and bug tracking. Jira makes it possible to utilize several teams at once, creating a lot of connections. Teams from the product development, product design, and product strategy divisions may collaborate to better projects. Using the filtering and searching tools, each team may keep track of its own deliverables, milestones, and tasks.

If you are leveraging the Agile Scrum framework, implementing custom views will help to assist your daily stand-up sessions. You might create your own distinctive points of view to talk just on the important components of the assignments. This function is efficient and saves time for a daily ten-minute stand-up. Other new features that make Jira a must-buy include alerts for due dates, assignment distribution, labelling, assigning task priority levels, and generating epic connections that display the user narrative and project progress.

Jira has Kanban boards where you may choose between showing and hiding features from other team members. Due to its capacity to integrate with many frameworks and maintain task and deliverable backlogs, Jira offers a great level of flexibility. Jira has excellent organization in its sprint planning, sprint release, and history structure. Any type of project management may use it. Customer assistance is offered by Jira, which is quite helpful.

My own opinion is that it's a fantastic tool; one of the dew drawback is the cost per user, which initially looks good but increases overtime.

Another drawback I've seen when using Jira is that there isn't an option to have audible notifications. When a new ticket is created, Jira, for instance, doesn't make a sound. So, if a user leaves the system, they risk missing a vital ticket.

First of all, this product offered a free trial to experience the features first-hand without any strings attached. It was great to have the ability to go and play in a sandbox environment and carefully evaluate what it can and cannot do for me and how it can add value to my organization. Set up and gaining access was easy and quick. The different permissioning levels make sense to stay organized and maintain accurate information. Some of the features I liked the most was having a great UI for exploring and learning without much training. I was personally tasked with setting up a couple of projects and the respective boards for my teams and I was able to do that in a pretty self-serve way. The design is minimalistic and doesn't feel overwhelming, it is clean and navigable. Easily creating backlogs, sprints and administering those are also my favorite features because it makes it so easy to implement an Agile project management and software development culture. The categories of initiatives, epics, stories, tasks etc. align very well with the Agile methodologies in following the same hierarchy. I love being able to get a quick summary view of the tasks before diving deep into the details. Assigning owners, labeling, story points to track work effort needed, description fields, attachments, comments and seamless integrations with other products make it all the more user-friendly. Kanban Board views in Active Sprints tabs provides a clearly easy to understand view of progress.

Managing boards within each project is the first that comes to mind. Jira does not offer a standard naming convention for the projects and boards and this can cause some major confusion. I have hard coding this manually and training people to do the same to ensure consistency. If you attached Lucidchart diagrams or embed other important document within tasks or epics, they don't update in real-time or even with refresh which is frustrating. This runs the risk of people getting outdated information which can misinform their actions. The search functionality within Jira is also something that I like the least. It does not return optimal results or even close to optimal results. Sometimes it does not search for metadata and you have to remember the actual word you're searching for to track down a task. It returns an overwhelming amount of results and the filtering or sorting options available are confusing and hard to understand. Another limitation is that even though one project can have multiple boards within, it can only have the one same backlog of items which does not make sense to me. There also cannot be multiple sprints running across different boards and all of this makes me wonder what the actual difference between projects and boards are. Jira also lacks some automation in moving tasks to different statuses upon completion. The workflows are suboptimal and don't work as intended most times. The reporting capabilities within Jira are also quite weak in my opinion.