Overall Satisfaction with JIRA Software
Since the company I belong to is working on Agile, JIRA is used for the following purposes:
1. Create tasks, epics, stores and requirements for different projects.
2. Reports issues.
3. Create deployment tickets.
4. Maintain Agile sprints.
5. Integrate with TestRail application for test planning and execution.
6. Prioritize tasks and maintain reasonable backlogs.
7. Update documents and make timing follow ups.
1. Create tasks, epics, stores and requirements for different projects.
2. Reports issues.
3. Create deployment tickets.
4. Maintain Agile sprints.
5. Integrate with TestRail application for test planning and execution.
6. Prioritize tasks and maintain reasonable backlogs.
7. Update documents and make timing follow ups.
- JIRA is a very good planning tool.
- JIRA is a very good issues reporting tool.
- For me it's pretty convenient.
Previously I worked in the company that used a proprietary application for project management, test planning and reporting. In my current company, I did not choose JIRA Software and, honestly, in the very beginning I did not like it. But all this is a matter of habit. Since my position is related to QA, I cannot evaluate alternatives from a project management perspective.
Using JIRA Software
500 - Top management, product management, development, deploying, customer services and QA.
People that have knowledge about overall procedures in the company, have knowledge about JIRA structure and project planning processes.
- Project planning.
- Issues tracking.
- Deployments and releases.
- Timing follow up.
Evaluating JIRA Software and Competitors
Recently I don't see any reliable alternatives.