Jira Core Reviews & Product Details

It can be very useful for running projects, tracking assets, and basically anything that requires work moving through a workflow. It provides for workflow management system.

Workflows are made up of statuses (issue states) and transitions (issue actions). So It become more difficult for understanding.

Solved many problems regarding running projects, tracking assets

The following are things I like about the Jira Core It is Easy to use It is Fairly Priced Helps with Project Management Supported by multiple platforms for integration

The following are things I dislike about the Jira Core: There is no in-person training or familiarization that we found. This made it necessary for the training to be managed by the internal teams.

Jira Core has helped us streamline the work that goes into completing a single task where multiple work streams and functions need to collaborate together. The system makes execution and clarification of tasks simple.

The organisation of the topics and the user friendly view

Cumbersome and confusing user interfaces

Solving the production bugs

The ability the track my tickets in a clear and digestible way.

For a software that is made for software development management the UX should be better. The story points tracking isn't great and the ability to organize the backlog isn't great.

Managing software development tasks. It is good at allowing you to label different tasks as bugs or spikes or just tasks, but only once you open it. It's not great at showing those labels outwardly on the backlog.

Easy task tracking, create and assign tasks, monitor achievements

I guess the interface need some work, GUI also.

Tasks control

1 :Clear indicator on ownership of work item 2: watch on defect : assign diffrent user as watcher

Not clear indicator of state. Comments are not trackable.

JIRA as defect tracker

User-friendly but customizable interface

Limited customization options, some features are permanent

Cross-functional collaboration and accessible documentation

The way do admin work, roles, tasks, times. It´s simple to configure and to use for administrate your work.

Nothing, thw software is intuitive and cumtom the workflow on the company

The integration with Agile workflow, specifically with SCRUM, to implements CI/CD on IT projects

Easy to keep track of the requests created by myself.

Navigation toggles are a bit confusing and not user-friendly. I wish there were more tutorials for the users.

helps me to keep track of the status of diffeerent request/tickets

The kanban board is easy to visualize all the tickets to a specific project

too much colours make it difficult to find the exact issue i would like

project managment and handling bugs and ticketing

I have used another version of Jira in the past and this is much easier to use. I really like that it is web based with tons of documentation on how to do things. I also like the templates for different types of projects. I'm still learning how to use them all but so far they fit our needs well.

The hardest thing to work with are the setting screens that open on top of what you are working on . It's difficult to know what you are changing or what the setting was previously because I can't move the screen. Another annoying piece is needing to use the Jira specific language to do customizations. It's close enough to html and css I don't know why Atlassian didn't just go with those.

We are setting up a help desk ticketing system as our company has grown to where we need one. We also want to move our documentation from a free for all file sharing system to something more structured. We are using Confluence on top of Jira Core to create web pages for all our documents.

With our current terrible experience with Jira it's really hard to think about features that we like. Due to how Jira behaves and how often they force changes in the design in a work-distruptive way, we developed a feeling that anything that could land in the "like" bucket either has flaws or works in choppy way (as Jira in general works) or it will be moved/removed/changed soon by the Jira team.

Oh, there are many: - Disruptive forced changes to the software - Jira is complex software and you have to first set it up, which takes a lot of time, and then learn the setup and the software itself, which also takes time. That alone would be fine IF Jira team would not change what you just set up or learned in a way that you have to change your setup or at least you have to relearn it - to find out that they moved, removed or changed that button that you use each day. And most frustrating part of it is that Jira forces you to move to their changes - you cannot stay to the design and functionality you've spent so much time setting up and learning about. - Slow, choppy performance - it is very often when you see how the page jumps, freezes which in turn makes you wait until it stops before you can move on with the work. This happens on 2017 Macbook Pro with 3,5 GHz Intel Core i7 and 16GB of RAM. Also there are times where Jira makes my laptop super-hot and spins fans like crazy. - Very chaotic UI - few examples: editing: some items you edit by clicking on it which brings up inline editor, sometimes you need to click Edit button and you won't ever remember what you edit which way; Features access - for example ticket's "Add flag" function is probably (I couldn't be bothered to find out all possibilities) showing only in one specific view (the board's ticket preview mode) but it's impossible to find in other ticket views - Jira forces you to memorize where you can do something; Sorting of comments - in some places it's ordered in ascending order while in others in descending order. - Search sometimes is unable to find tickets - Ignorant approach to users requests - just check their page for feature requests - there are features with thousands upvotes not being implemented or even commented by Jira team for years now.

We are trying to keep track of the project progress that could be used across different teams in our company. We realised that we are very close to take the huge effort to move to some other service which might improve the way we work - it is probably just another one forced design change in Jira away.