My day to day with JIRA!
March 12, 2018

My day to day with JIRA!

Eliz Marvic Melicio Carvajal | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with JIRA Software

In the software development department of the company, we control projects under the agile methodology. We manage all the development and maintenance projects of our internal applications using JIRA. We control development times and assign priorities to projects.

In addition to this, we receive feedback that comes directly as pending issues in Jira of the users, to more efficiently manage the improvements and failure reports of all applications in use and in the process of testing.

  • It is excellent for the control of development projects under agile methodology.
  • It allows you to reprogram issues, attach images, set subtask to each issue, which later depending on the complexity you can convert into an issue to execute later.
  • By closing each sprint you can graphically view the Burndown Chart, which allows you to analyze with the development group, if the sprint was under what was planned or what caused the deviations.
  • It would be ideal to have among the notifications one that alerts when a sprint is about to finish and still has tasks to do and in progress.
  • The user interface for Jira in the cloud and Jira on server versions should be the same.
  • It should have an integration with the Outlook calendar, iCal or any other calendar so that everyone has calendar programming in a single application.
  • It significantly improves the management of the activities of the team of developers.
  • The planning of the area works efficiently, because, through agile reports, the scrum board can more easily determine the delivery times and start phases of the different projects.
  • When you have a male hours control application in the company that is general for all employees, it is very complex to have the developer use the time tracking and the other application because they feel that they are doubly charging the information and what has happened is that a of the two applications is outdated at the end of the month, and you must invest a lot of time in leaving both lists
  • Agilefant

Comparing JIRA with other products, JIRA has more features. It shows more information in each issue, it is easy to use when you have users of functional tests that must enter the application to update the issues in tests or when they must enter acceptance criteria, the collection of information, add documents, perform the comments.

In addition to this, the control of the sprint and the backlog in JIRA is more comfortable and easy to use and modify, as well as the creation of new projects and the use of the time tracker to control the time invested as planned.

When you have planning meetings for the development activities, the scrum board is an excellent ally to see the status of the issues and the workload of each developer.

When you need to analyze the month's work of the department, and you rely on a list of issues (where input the issues product suggestions or errors reported by users and those entered by the development team) is not easy to filter to organize them by project and in some specific status, this is to quickly determine the number of issue that you have for example by making one or several projects.