Jira Reviews & Product Details

The notifications and integrations in the aplication

The way that the interface work inside the app

Talk directly with the devs

Jira has best ticket management platform where I can easily track ticket and get relevant data of particular tickets

there is nothing disliked services at jira all tools are very helpful for developers

when we work with large team members or large products Jira provides a one-stop solution for me and my organization, I am more productive with jira where can find the necessary information for the development

Features for properly managing a project including test management add ons like Xray.

Editing multiple jira tickets capability is for paid variants, it should be available with normal user also

Managing project that includes test management add ons

1.It mostly help for assign task for particular person. 2.it reminds the process of the project what we need each and every details. 3.its minimalistic message to fill the requirements.

1.its requires each and every panel to fill the requirements.so it's consume my time more. 2.need notification,the person who i assigned the task see or not, or atleast get noticed in blue tick.

1.In my day to day work it's makes easy and simplified to assign the task. 2.its helps to prioritise my work and also it's makes monitoring the project. 3.the project delivery is an short and sweet.

It is very easy to use and get started, its integration with other tools such as bit bucket is very helpful.

There is nothing major dislikes, some integration would be very useful like Jenkins.

Its helping us see a overall view of the project and helps in collaboration with teams easily.

Jira is the best project management tool due to it's excellent user friend User interface and best custom options

Both web application and mobile application works well and good. I don't see downsides here

Management of projects. Task assignment. Daily updates. Options to upload the files etc.

The ability to break projects down to the smallest tasks and track all the minutia

As we're running the cloud version, sometimes performance can lag.

Tracking multiple projects and tasks across different teams

Complete bug tracking and maintenance with accuracy with time .

some clear user interface with seamless experience

jira has the complete analysis of all the bug with on point details.

I like the project dashboards with drag and drop of the issues

i hate the complexity in creating filters

I help me project management with attached plugins like testing, analysis, automation etc

Jira has the best management of the bugs

some things with respect to users it lacks.

Tracking bugs to the analysis time taken each and everything it keeps the records.

Ability to view work flow and time reports

I have nothing to dislike about Jira, at first it was a little bit of a learning curve but that was more on my end. Very user-friendly.

Time reporting, it has been a great tool to measure project spends

I like the fact that it is a way to track projects and have requests well organized in there. The SLA on the Jira Service Management helps us prioritize and see which requests are urgent and which are not.

What I dislike about Jira is that it is not very smart in the integration with Slack. When you create a ticket in Slack you are not able to change who is the reporter, so you end up going into Jira and manually changing it. Another thing is that in the integration with g-suite, it is hard to change a user's name if two users have the same name but different emails. (ex. We had a former employee whos name is John C. so his email was john@. When he got deleted and a new employee came on board, his name was also John G. so his email was also john@ but on Jira, it would show that his name is John C. instead of his name John G.

Jira is solving many requests we get from users promptly. We get a lot of requests and some we miss on Slack, so with Jira, everything is recorded and assigned to someone so that they can see how many requests they have.

The best thing about it is that we can quickly add issues when they come up or are reported to us, prioritise them accordingly, or assign them to the best person for the job. We also use Bitbucket so having it integrate into that nicely is a great bonus and really makes our dev more efficient.

There are a lot of features and charts and all sorts you can twiddle with on Jira which can make it feel a bit overwhelming and/or cluttered. I personally prefer the Bitbucker integration of Jira issues as it's a bit simpler and feels less cluttered.

Using Jira has completely streamlined our issue tracking, which used to be tracked by email and then Trello, which wasn't as efficient for our needs as Jira is. Using Jira means we can properly prioritise our roadmap and upcoming projects and updates.

The customization almost seems unlimited and to the point at the same time. Creating workflows and practicing agile methodologies could never have been easier. It has been bossing the market since early 2000's.

For a beginner assigning tasks to teams and users could be quite a hassle. It definitely takes some time to get used to, especially on integrating other software.

It's easier to manage your code on a UI level, otherwise, me and other developers at my company would check logs, commits, readme's, etc to understand the workflow.

It allows us to define a release procedure and make sure all tickets (issues) go through the same predefined steps. It also can be linked to deployment software to allow automatic builds of the software as the ticket moves through different stages.

Jira cloud has missing features from what was initially provided by Jira, although they are working on this to bring Jira cloud in line with the original software.

We have issues tracking issues from the user through to deployment. Using Jira issue collector we can track these changes, while also automatically informing the use of the work being done on the ticket.

It makes it easy to track stories, tasks, and bugs effortlessly while grouping them under one theme/ story. Super helpful for startups and early-stage companies in creating standardization apart from maintaining their documentation, training material/ ops manual for sales, marketing, and operations departments.JIRA is very extensible and there are thousands of add-ons to customize and easily integrate with other software without much-complicated code. However, this can be started using right from the out-of-the-box features. Customizing workflows is not too hard. There is a good software development kit and good documentation for developers who want to write add one. Some of the best parts include 1. Tracking the workflows and milestones for the product roadmaps 2. Tasks can be assigned to any particular member of the team & tracking them is easy. 3. Helps create sub-tasks in QA and testing services.

1. Lack of Integration/ collaboration with Microsoft teams for chat and communication purposes. 2. No built-in timelines and reminder features to track project progress. Some of the teams do it manually in scrum calls. 3. Takes a good amount of time to understand and familiarize yourself with the features. 4. lack of feature: Bandwidth visibility tracker to showcase at a personal level and dashboard to show run rate ( stories executed / week) 5. Costly to build complete suite of solutions. Limited file size upload 6. Missing feature: it lacks features to manage costs or assess risks, features often needed in a complete project management experience.

1. Helps in controlling software development lifecycle including developing features & specifications. 2. it is an ideal tool for teams that use iterative approaches (Agile Methodology). 3. The platform integrates with many test management tools for a seamless quality assurance process. 4. Teams can optimize Jira’s issue tracking functionality using custom screens, custom fields, and workflows to handle both manual and automated testing. 5. I used it extensively to maintain sprints, and backlogs and integrate with Github.

JIRA is one of the best workflow management tool, which has been set as an Industry standard and is being used my most of the Multi National Companies. It is really in terms of tracking of work on a project , status of a task at various stages with integration with Git for Developers as well.

There should be some features that gives limited access for a JIRA to the people who have been added as developer or tester or reporter to delete a subtasks or a defect etc. For some features, you need to have admin privileges. The UI and Project Integration takes some time getting used to.

JIRA has really helped in tracking the Status of the tasks one is working across different projects and manage the workload according to the status of tasks and their Drop Dates.

The template for creating bug, creating epic, story, task are so well defined. The best part is we can customize and add new fields and values based on our need. Also we can create multiple dashboards and different ticket boards for easy tracking

Once if by mistake user create any subtask or item by just air it don't allow the user to delete the same. Ideally it should allow to owner to delete the item created by the same user with condition that if the item created has any comment from any other user then the created user loose access to delete the same.

It's solving hell lot of problem. Help in systematic loogging and tracking of bugs and it helped the entire agile world to run things so smoothly. It's must to have tool for all the it professional.

The clarity between the teams regarding specific features and products. The tool is useful right from the planning phase to support and maintenance. The document attachments are supported which is very helpful.

The inbody images attachment is not proportional and often breaks the indentation of the message. It will be great if the attachment is aligned properly with the message body.

It is a resource book for us to keep track of the development work of new upcoming features. We can engage R&D with suggestions and feedback on the new features.

The way it is used for assigning tickets for tasks.

No dislikes as of now. Sometimes I myself get a lot of ticket to resolve thats the issue 😜

Tickets assignment by PM Tickets assigning to different teams: testing team, DBA's etc.