Jira Review

We use it mainly for Scrum management.

Most of the projects which we have taken in were using a waterfall model, which is very hard to convert into an agile or Scrum model. It helped our customers have visibility into requirements and reporting, since they were mostly using spreadsheets. We could help give them a clear cut view of what was happening on ground with development and the test database.

Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on.

JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless. 

You can do a lot with the tool but again, but it is not a 100 percent solution for everything. We have a lot of acceptance criteria coming through it, but JIRA doesn't support it. Therefore, we have go to different user stories and break them down. 

Using a cloud instance, it is always stable for us. It is not a problem at all.

We use a cloud instance for most engagement, so scalability has not been an issue.

My company has a 100,000 people, so we always can find someone within our organization who can help fix an issue.

I was not involved in the initial setup.

I understand JIRA is quite expensive.

Most important criteria when selecting a vendor:

1. Usability: It should be easy to use. People should not have to undergo a lot of training because it should be intuitive.
2. It should be scalable and a cloud solution. 
3. It should not be expensive. Cost is a major driver because I work in pre-sales.