Jira Align Reviews

Mainly, we use the solution to maintain our backlogs, scrum processes, and project management. So, we create the entire structure. It is a brief project management tool. Regarding backlog management, the solution includes features apart from using the product for the product backlog, sprint planning, experiments, and defect management.

Jira Align is an intuitive tool that features a roadmap view. This allows users to see the entire program they have set up, following sprint planning. The portfolio summary view provides a user-friendly interface for operational users such as the scrum team, the scrum master, and the product team. In addition, it provides a management dashboard for leadership to monitor progress. The tool enables viewing the entire roadmap for an epic, and users can drill down to the lowest level, the product backlog item.

My company is in the process of moving out from Jira Align. We are planning to transition to another tool called Planisware. Though there are no issues with Jira Align, Planisware offers its users a complete package in terms of portfolio management. Jira Align fails to provide its users with a complete package in terms of portfolio management. In short, Planisware offers many different facilities making it a more comprehensive tool. In a company, we can use Planisware for resource management, especially at a portfolio level. Though it is expensive in terms of licensing, our company has decided to move to Planisware.

I have been using Jira Align for five years. I don't remember the version I am using currently.

We have around 500 users using this solution in our organization. In our company, we are using the solution extensively. Also, we do not plan to increase the number of users since only specific people in our organization use the solution.

In our company, we have a different team who deals with Jira's technical support team.

Previously, we used Azure DevOps in our company. Azure DevOps was earlier known as VSTS. Also, we still use this tool in our organization. So, we use Azure DevOps for all our product backlog items and overall product backlog management at a lower level. We use Jira Align to manage epics and features.

The initial setup was straightforward.

Its setup process is not complex since it's an intuitive tool.

I don't remember how long it took to deploy the solution in our organization since we started using it around four years ago. We did not face any issues during its deployment phase. Regarding the deployment model, I would say that we are using the solution on the cloud. Also, I won't be able to explain the steps involved in the deployment process since a different team did it a long time ago. We have a team of around three or four three members to manage the deployment and maintenance process.

There are two types of maintenance processes. In pure maintenance, if you have an issue with the tool, then you raise a ticket, after which you work with Jira's support team to resolve the issue. And the second type of support that you require is from people who understand the technicalities of the tool and know where to set up certain things in the tools that can get the tool to provide privileges, user access management, and identity management. In our company, we have various pillars. So, each pillar will have a small team of one or two people. There will be a team of those providing support to the people in a particular team on how to use the tool, especially if there is any required setup or administration-related activities. Since it is not our tool and we weren't involved in the coding process of the solution, we need to reach out to Jira if we come across any defects or need to make any customizations in the tool. So, we formed a small team of two or three members to look into such issues and needs.

Jira Align is definitely worth the money.

Even though my company has an enterprise license for Jira Align, I am unaware of the solution's pricing.

I recommend the solution to those planning to go for agile project management since it has all the features. We use Azure DevOps and Jira Align in our company. A lot of maintenance happens if you have multiple tools. So, sticking to one tool is better. So if one has Jira Align, one should develop everything in Jira. However, Jira Align doesn't have code management in it. One should choose only one solution between Jira Align and Azure DevOps as an agile project management tool. Sticking to either one of the tools for a specific or particular project is better. There have been instances when a certain tool does not support a waterfall project model. In our case, we get involved in many deployment activities using different tools. Taking one tool into consideration, it might have limitations. Hence, a person needs to understand the nature of the project before selecting the tool and using the same one for the entire project. In short, it is better not to use Jira for everything since it is meant to be used only for those things for which it was developed. Using multiple tools might create syncing issues or integration issues for its user.

If you use Jira Align for agile project management, you will undoubtedly have a better user experience and more capabilities. On the other hand, if you choose to use Azure DevOps for the same purpose, you may have to make some compromises since it cannot manage agile projects as effectively. However, Jira Align is the recommended solution if you have a larger project with several integrated components and require portfolio summary or roadmap features. Azure DevOps can be a good choice for smaller projects that do not require much visibility. For instance, if there are several MVPs like, let's say, there is a road map of three years for a product. In such a case, Jira works out better from a project management perspective. If you have a support project where you mainly use Kanban or require an operational perspective without the need for extensive visibility for senior management, Azure DevOps is a suitable tool. This is especially true if there are more operational users on the tool than management users. The choice between Azure DevOps and Jira Align will depend on the type of work being done, project size and complexity, number of people involved, levels of management using the tool, and cost considerations. Since enterprise licenses are typically negotiated, Microsoft may offer better pricing due to its existing Microsoft 365 OS license. It is important to make an informed decision by considering the project requirements and ease of tool management.

Overall, I rate the solution an eight out of ten.

Our use cases for Jira Align are particularly project-based. Whenever we go on a project, we utilize the solution, and at the end of the project, we drop that subscription. If needed, we go for a new subscription again.

Jira Align is an easy-to-use and user-friendly solution.

The solution’s stability could be improved.

I have been using Jira Align for four years.

I rate Jira Align an eight out of ten for stability.

More than 50 users are using Jira Align daily in our organization.

I rate Jira Align more than eight out of ten for scalability.

I rate the solution’s technical support a seven or eight out of ten.

Neutral

We also use Azure DevOps.

The solution’s initial setup is easy.

We implemented the solution through an in-house team, which had a couple of people.

We have seen a return on investment with Jira Align.

Jira Align is an expensive solution.

I am using the latest version of Jira Align. Jira Align is deployed on-cloud in our organization.

Overall, I rate Jira Align a nine out of ten.

We use Jira Align for project management, product planning, and reporting.

The most valuable features of Jira Align are its product roadmap and reporting.

Jira Align's user interface needs improvement because its user experience is really bad. It takes around a week to onboard any team member in Jira Align because it has a lot of nuances. The materials used to go through the Jira Align tool are time-consuming and academic. I have used Jira Align for eight years, but I had to keep doing many things with Jira for at least three months to understand everything.

Jira Align doesn't recommend anything. Jira Align should improve its AI offerings because it currently has zero AI. The solution's release notes, user stories, and templates are far more boring.

I have been using Jira Align for eight years.

Jira Align's technical support is very bad. It takes around three days for the technical support team to even reply to a customer on how to resolve some issues.

Jira Align is an expensive solution.

Jira Align is deployed on-cloud in our organization.

Overall, I rate Jira Align six and a half or seven out of ten.

The solution can be used to track and update testing progress. We can use it for test management, creating stories, and grading test cases and plans.

I have been using the tool to write test cases, prepare test plans, and create bugs. I like the way the UI functions.

The initial setup was a little bit complex. It involved many things.

I have been using the solution for three years.

The product is quite stable.

The product is scalable. More than 100 people are using the solution in our organization.

The admin team deploys and purchases the license. We use it whenever there is an account created in our name. We simply log in with our credentials and use the tool.

The tool is moderately expensive.

I recommend the solution to others. Overall, I rate the tool an eight out of ten.

Our clients use Jira Align for new development and defect tracking.

Defect tracking and dashboards are the most valuable features of Jira Align.

Jira Align should reduce the many information fields we need to provide while closing defects.

Jira Align should improve the ease of use for developers.

I have been using Jira Align for the last five years.

Jira Align is a stable solution.

I rate Jira Align an eight out of ten for stability.

Our clients are mostly medium-sized businesses.

I rate Jira Align an eight out of ten for scalability.

I rate Jira Align an eight out of ten for the ease of its initial setup.

Initially, Jira Align's deployment takes some hours. Otherwise, it is quick to deploy. Initially, to deploy the solution, we had to check the prerequisites on the server and connectivity. Based on these factors, we can install and set it up.

On a scale of one to ten, where one is cheap, and ten is expensive, I rate Jira Align a seven out of ten.

I suggest users go through the free training first, understand, and then start using Jira Align instead of using it right away.

Overall, I rate Jira Align an eight out of ten.

My company uses the solution for processing claims, specifically motor claims.

In my company, we found the solution to have many issues regarding its ability to handle claims and other processes since the solution is not available on a single window. The solution needs to be more simplified and should have more integration capabilities.

In my company, we found that the solution has a lot of integration problems between the communication channel and other related areas, because of which we cannot find any dashboards to connect directly from our client. It is difficult to integrate Jira Align with other products. We currently use Smartflo for communication purposes offered by Tata Tele Business Services since we want to integrate it with Jira Align to get our toll-free number as 1800. We face issues because of the integration problems between Jira and Smartflo. The aforementioned areas can be considered for improvement in the solution.

In the future, Jira Align should integrate and include an Indian toll-free number in its communication channel.

I have been using Jira Align for about six months. I don't know the version of the solution I use. My team uses the solution in our organization. My company is a customer of Jira Align.

In my company, ten people use the solution.

My company has contacted the solution's technical support. My team is not updated about the current situation regarding support since our company's IT manager handles the part related to technical support. Compared to the past, the support has improved a bit.

I read the technical support team of Jira Align a five out of ten.

Neutral

The deployment phase of Jira Align wasn't difficult. Jira Align does need a third-party component, like Twilio, that doesn't work in India if I want to integrate Smartflo's phone dialer in Jira Align.

The pricing aspect of the solution falls under the higher side of the spectrum. I have been looking at solutions available at lower rates.

My company pays approximately 399 USD per month for the solution. Maintenance and support are already included in the monthly costs paid towards the solution.

I am not satisfied with Jira Align, and because of this, I am looking at other solutions, like Zoho Desk, since it offers a complete ticket management system. Zoho Desk provides a single window compared to Jira Align, so we can integrate every solution in a single window. Jira Align is a little bit complicated to handle my ground-level work since it is a project management tool and not a ticket management system. My company is specifically looking for a solution that functions as a ticket management system.

Our company is currently looking at Zoho Desk since one of our technical members can easily handle the product going to previous experience with the tool.

My company is looking for a tool with a single dashboard that allows us to integrate Smarflo's phone dialer, but Jira could not provide any API links for such an integration.

I rate the overall product a six out of ten.

The solution helps me with real-time data visibility. 

The tool helps us to stick with the timeline and budget of our projects. It also helps me to identify dependencies and red flags and intervene wherever possible. I have found the key metrics tab also useful. 

The solution needs to improve its pricing. It also needs to provide an integrated view of how other tasks are to be tracked. It would be also useful to see the integration of Confluence, Teams, and Slack into the product. I want to be able to communicate directly with others while using the product. I am also not sure if the integration of third-party alternate workflow tools like SAP would be possible. 

I have been working with the product for two and a half years now. 

The product is stable and I would rate its stability a nine out of ten. 

I would rate the tool's scalability a nine out of ten. My company has more than 100 users for the product. 

The tool's customer support is responsive. 

Positive

The product's deployment was seamless. The tool's deployment completes within 30 minutes. We have a team of four to five people who are responsible to maintain the product. 

I would rate the product an eight out of ten. 

We use Jira for scrum-related activity and 80 people use this solution within our company. 

In my current organization, there are limited features that we have adopted. In my previous experience, the Portfolio and Structure feature in Jira is really valuable because it assists with forecasting for projects. 

We have experienced errors with the internal server that occurs frequently. 

I have been using this solution for eight years. 

This is a stable solution. I would rate it an eight out of ten. 

In my previous organization, I contacted the Jira support team for a particular feature and they suggested that we upgrade Jira because there was a bug in that particular version. After upgrading, the issue was resolved.

Jira offers very good GUI. The solution is easy to learn and there is a lot of functionality related to boards and project management-related activities that is offered. There is also good synergy between all the Atlassian products which is why we decided to switch to Jira. 

I would rate this solution a nine out of ten for pricing. The price of the solution depends on the number of people using it and the projects you are working on. 

I would rate this solution a nine out of ten.