Jira Reviews & Product Details

I like the intuitive "project board" UX. It's easy to see what still needs to be completed vs. what is already completed, and the configuration options are plentiful.

UI changes can catch the team and me by surprise. Sometimes lesser known options (i.e. "below the fold" details) can be hard to find when needed.

Our different team functions (Product, Engineering, QA) are all on the same page now. We all have clear ownership of our processes, and as a result, shared ownership of the whole process.

We use Jira Software to manage and assign tickets and tasks, track work progress, and help with our internal QA process. It is used for our entire engineering team. It allows us to manage and time estimates of project work, which is necessary for assessing projected costs across multiple projects.

Sometimes Jira occurred bugs, like when we assign the task to another person and close the ticket by cross icon; it refreshes the page and reopens that ticket on the screen.

With Jira, our task management has improved. All the tasks can be tracked on jira to overcome problems like what caused a delay in delivering the feature.

I like the fact that all the user stories, spikes, bugs, and epics be interlinked and used as a traceability matrix. Sprint goals and reporting also can be done very accurately.

So far, there is nothing which I dislike about JIRA

I use JIRA to write stories, map stories, and update bugs. It helps in keeping track of product details in one place.

The usability in the JIRA is outstanding. Custom plugin support is excellent. Best software for scrum management.

Performance needs to be improved. Can improve UI architecture.

Complete scrum solution. End-to-end project management tool.

I like how we can integrate our workflow in Jira to our daily priority google sheets. Helps keep us on track with projects.

Sometimes things are hard to find and there are way too many email notifications on projects you are watching.

We have many steps in our processes for our projects, and Jira helps keep track of every step and integrates with our other products we use.

Creating multiple projects, assigning quick products to releases, and tracking issues are possible. A wide range of details is available in the form of giving an owner to each delivery, as well as accompanying images/videos/text/comments can be incorporated to illustrate the deliverables/bugs. A second advantage is that we can measure the time spent on each deliverable, which will assist you in defining your project plan and estimating the length of unpredictable durations for each deliverable. Additionally, it would be helpful to categorize issues as "Bugs," "Stories," or "Epics," as appropriate, and maintain a database of bug statuses by date and by application version.

The potential of Jira has not yet been fully realized. New users may find it challenging due to its complexity. While most of the processes can be simplified, I believe that some can be streamlined.

For my organization, I am responsible for the end-to-end management of all projects. To accomplish my daily tasks in the most structured manner possible, I work with multidisciplinary teams, organize sprints into deliverables, assign responsibilities, track time, and finally release.

We can distribute teams to smaller groups and create boards to track the progress on issues. Can create Development boards to track progress daily in stand-ups. Provides real-time tracking of stories in the sprint. Consolidated platform for all defects, so planning on the work is easy. For Agile and for Waterfall model as well we can plan on Jira. We can design and develop our own workflows as per our need.

If we create sub-tasks in one story, it is not easy to track the story in Sprint. Creating and maintaining the board is heck tick work. Sometimes if you do not have permission to perform a specific action, you have to wait to complete it. If team members are on leave, we can not track it in Jira for effective planning.

We can not think of Agile development without Jira. Jira is easy to use and effective for real-time tracking of stories. Team bandwidth is planned effectively in Jira; it will be excellent for effective planning of sprints. Custom workflow development.

Jira has an easy-to-use interface and makes running features fast and convenient. You can easily manage your sprints, complete sprints, create requirements backlogs if you are part of an agile team. Jira is fully customizable, allowing you to add any labels and filters and manage stories with ease. Agile frameworks use the Jira model to facilitate all ceremonies.

I believe that the Jira mobile app can be improved.

Our project meetings and product planning are done using Jira. JIRA is the platform where we create all the task for the product team to work on. Our favorite feature is the ability to add custom fields for specific purposes.

Jira is highly customizable, allows for wonderful automations, and expands with your team / effort. I love the ability to create a huge number of customer views, search filters, and boards for task management. JIRA allows you to focus from the small to HUGE with everything from sub-tasks to EPIC projects management efforts. Included in each of these is built in features to help you track time, help size efforts, and look at burn-down rate. Beyond the default features JIRA allows you to HEAVILY customize your workflows, ticket templates, teams, etc. to fit into how you want to use it.

The highly customizable nature of JIRA means you can get into some headaches if you don't think through options. The UI for JIRA continues to improve and change, but some changes can be a little dramatic and overall the UI seems to shift each release towards more simplicity. At times this can remove a feature your reliant on, and will make you go searching for it again. The complex UI for JIRA also means that you might encounter some slowness when running it in your browser. Our team was able to create our own UI to help speed up certain views and make sure we only saw what we needed without slowdown.

We use JIRA daily to help with team coordination. This gets us on the same page with documentation, search, and automation features we need to react quickly. We also use JIRA to track product feedback and roadmap the future.

Most of our external and internal services are managed with JIRA . That's the reason I like JIRA—because it's so flexible. JIRA allows you to assign issues to the right team in the workplace and flag and resolve issues based on their status. A great feature of JIRA is its ability to share internal team communication via a blog.

In order for the system to work properly, there may be a need for training. This is especially important for administrators who are responsible for configuring JIRA in their workplace.

Managing projects has become easier with JIRA. Collaboration between departments is better and production has improved overall.

The customizable workflow is one of the most attractive features of Jira that drew my attention. Advanced search and filtering are also much appreciated. The speed at which search results are provided is commendable. Dashboard customization and the ability to showcase in several forms is one of the other attractions. I just like the pie chart view and the bar graph view.

The mobile app variation of Jira requires strict attention. The application is not at all user-friendly and often hangs when multiple operations are attempted. The documentation part needs to be improved. Sometimes it's a bit tricky to figure out how some features work. I have felt that Jira is designed mainly for cloud-based solutions. Generally, I think that Jira is primarily meant for cloud-based applications rather than other kinds of applications.

Progress tracking was a pain when the team size was more significant. Jira helps me ease out the tracking process when the team involved is considerable. Sharing the progress report clearly and concisely, which is easier for a non-technical person, was another issue that I was facing. Jira also gave a solution for the same.

Jira is one of the best tools for issue tracking that I have worked on. You can define a customized workflow. You can follow the teamwork with the defined SLA. The integration with almost all the dev tools is a huge plus.

The move from a version to another, especially with significant changes on users interface, could put the users sometimes in complex manipulation issues.

Customized workflow to follow the projects, tasks, and issue tracking. Integrating Jira with other tools to raise issues to a designated team to fix them. Following and splitting the teamwork.

Easy to see, analyse and filter out team tickets which helps in easy management. Easy to use interface. Drag and drop features helps to save a lot of effort and makes things more easier. Dashboards and filter makes it super convenient to analyze and asses the projects at multiple levels. Easy to add comments and screen shots/images with tickets for making it more informative. Easy integration with Microsoft products is quite handy and useful.

It is not possible to delete tickets which are once created. Difficult to review and manage swimlanes., this option could have been made a but more easy to manage. Help options are not available at all the user levels. Sometimes become clumsy and complex. No quick help docs for new users.

We have been using Jira to collaborate between teams across different departments and different time zones. Extensively using the Kaban board to manage project execution. Eliminated a lot of team effort and paperwork. Cloud support on browser makes it very convenient to load and use.

Great for cross-function communication. when working with our engineers we like to have a fair amount of visibility into what stories we have on the road map, individual tasks that need to be accomplished, and who is responsible for each.

It's pretty complex, so navigating is a bit complicated. It's not that I dislike it, just that I'm a new user and I'm not a project manager, so I don't have the background with terminology and the processes that inform the logic.

Product management and engineering management has been made easier with Jira. It is easy to communicate through comments and assign tickets back and forth. One of the key benefits is being able to have the organization use the same tool for different departments. This solves the issue of maintaining different tools and saves time from having to create additional integrations.

Agile implementation, customized flow process control, task and subtasks, integration with Git

There no option for offline mode. We need to connect to the internet or open form mobile app to do an update or view the progress

Tracking for the project progress and collaboration problem

Jira makes working across multiple teams very easy and helps to keep everything well documented. Projects are easy to organize and link to different brands ("epics"). Makes it simple to assign tasks to people and also keep people in the loops on progress as a "watcher" of a ticket. I find looking through past tickets as an easy way to keep track of information or find resources and references for new projects. It is also easy to update workflows and make lists of priorities for teams.

Jira recently changed the way comments show up. While this is not a big issue, I find myself spending much more time now looking for the information I need. It also now shows all URLs "inline" and while this looks much cleaner, when I am working with developers I need them to see the full URL and parameters and need to always switch these manually.

Jira helps us complete projects and work across teams to do so. It is easy to communicate through comments and assign tickets back and forth. I enjoy how customizable the program is so you can really make it fit to what you need and what works best for your organization.

1. Custom defined workflow that are present in the JIRA which can be leverage to automate any usecase for Software Management, IT Helpdesk Managament, Bug Tracking etc. 2. Dashboarding features and pre defined Gadgets.

1. Little Expensive on pricing part. 2.Unsecure Additinol Plugin available on marketplace

1. Manage Sofware Development Lifecycle 2.Ticket Management for Request and Problem Management and Change Management 3.Track Project Status

First of all, I would like to say that one of the most useful features for me is easy to track all the tasks or issues related to the project is very efficiently done. Secondly, You can generate statistics report from the Jira at any time for checking the overall performance of the Project. We can also give a Provision to the member of creating some limited type of task. So, that's how we can prevent the members from creating the task types which are not allowed for the members. and Security Provided by the Jira is very good.

By Talking about the negative points of the Jira, I can say that It may be very complex for the new users. There is also a limited number of gadgets available in Jira, So I suggest there must be more gadgets that should be supported.

"We are following the agile method in our company, My Overall experience with Jira is Very Good. It can be highly recommended if your company is following an agile fashion for Project management. "

I like the implementation of agile in the tool. It is flexible to accommodate any agile framework and still manage to give the level of customer experience that can keep you engaged and productive. I have been using Jira to track requirements and drive tasks to deliver the requirement and i cant imagin how difficult it would be for a developer without this tool. The automated deployment shows the extent of integration with devops tools and makes a lot of manual processes streamlined.

I believe one thing about the product's success is its governance, and sometimes I feel that comes as a put off factor. There are a little bit of ambiguity in the types of issues that can be created but may be that because of implementation rather than the tool itself. I also dislike the fact that every update triggers a communication email to everybody in the ticket.

I use Jira for the following 1. Review and help manage Product backlog maintained and owned by the PO 2. Leverage the Backlog section to sprint plan for the next two sprints. 3. Use the Burndown chart to carry out sprint execution 4. Deployment through DevOps integration 5. Manage Bugs as a Bug ticket which is typically owned by the Dev team if not solved by the L2 6. Manage cases that are raised by the business users and take it to deployment

Its best for tracking issues, links various sub-issues and prioritize them.

Sometimes it shows some token issues which needs to reload the session.

The best problems solving is you can use it in bug tracking, link various sub-issues. It is good to be used in project to work on sub-modules and project specific requirements. It is fast and we can link up various types of files. It has some good text propmt in order to see the good output results.