What is our primary use case?
We use Jira for the overall issue management in development projects. We use it to maintain a high level during each sprint, which is a requirement. We also use Jira for issue management during testing. We create a test plan and manage it all with Jira.
What is most valuable?
Jira is very user friendly, easy to install, and easy to access. The most valuable feature in Jira is release management. You can also manage a consolidated dashboard that can be accessed globally by all the team members. We can do all this with Jira while engaging in development.
One of the key benefits is that it's a single repository for all your SDLC. Based on the user ID and password, anyone can access it, and they also have a single sign-on. It's not that very complicated to do issue management with Jira. We can also pull Jira data and generate quality metrics that can be used for the overall optimization of the test execution.
What needs improvement?
Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature. Because right now, we're using third-party tools to test executions.
If there are multiple projects, it could be a good thing if they had a reporting method where you have a portfolio view with predictions and so on. If there were a way to manage all the SLAs, that would be helpful too.
What do I think about the stability of the solution?
Jira is stable and meets our requirements. You don't have to use it out of the box as you can customize it to your requirements.
What do I think about the scalability of the solution?
Scalability isn't a problem because we have used it with over 200 users. You don't have to stick to any out of the box features as you can customize them.
How are customer service and technical support?
Almost everything is covered in their documentation. As payment is required for support, we mostly follow the documentation.
Which solution did I use previously and why did I switch?
We used Microsoft DSP before. We were looking during a licensing phase for something where the non-licensing cost wouldn't be more, and the system requirement would be minimum. That's what qualified Jira, and we went with the data.
How was the initial setup?
The initial setup is very good. I wouldn't say that it's very complicated. They have customization options for things like issue management. You can customize it based on your terminology and project.
For a simple set up, it may take around four hours. If it's a 20 member project, it's quite easy to set up Jira. But if it's to be made available enterprise-wide, it takes longer. I had complex projects where it took anywhere from three to four days or a week to set up. You should also note that it may take new users a week to understand it properly.
We tried to do a total uniform deployment, but it's not always possible because every project has some customization. A single user can deploy Jira. I have deployed and managed 20 to 22 users in a Jira instance. Basically, the Jira administrator creates the template. But if the project requires customization to write queries and run tests, that will require some additional skill.
What's my experience with pricing, setup cost, and licensing?
As a company, we get a subsidized price, and it's lower than what's quoted on their website.
What other advice do I have?
To a certain extent, maybe 70% to 80%, Jira will meet your project development budget. It has integrations with other platforms, so if you want to put it in your DevOps continuous integration flow, it can be done.
If you're engaging in software development, there should be a single repository where you store everything. Then you can start managing it with Jira based on the business requirements and the user stories.
On a scale from one to ten, I would give Jira a seven.
Which deployment model are you using for this solution?
Which version of this solution are you currently using?