Jira Align Reviews

The solution was useful in monitoring and observing the status of different environments.

We have a dedicated team to monitor the solution and keep everyone updated about the status of our environments, tools, and applications. The tool enabled everyone to see the status of each environment. Based on the availability, they could decide whether to use the environment at a particular time or set up some test sessions for a day and block the environment for themselves or the team for testing or maintenance. The board meetings took much less time to figure out where we would be at a point when we needed to do some activities. Everyone was aware of the status. We could be better prepared for the meeting.

It takes a lot of time to maintain the product. There were a lot of changes in our environments during the day. Using the tool might have been more convenient and productive if we did not have hundreds of different environments. The tool must provide better bulk editing features. It must provide more flexibility to make a wide range of changes to many things at once.

I used the solution for a few months.

The product was pretty stable. I rate the stability a seven or eight out of ten. The solution is not the perfect tool for a complex environment.

The tool’s scalability was good. We have around 250 to 300 users in our organization. The technical team had three members.

The setup was straightforward.

The solution increases the productivity and awareness of the team members. It also saves the management’s time.

The tool is good if we do not have many applications or environments to monitor and handle. It can be really useful when we have to make a roadmap with the management team. Sometimes, it can be too much to maintain and handle if we have too many environments. We will always keep forgetting something. To keep everyone using the product and updating it was challenging. Half of our team used it and performed all the necessary actions. Overall, I rate the product an eight out of ten.

I use the solution for task reporting. 

In our workflow, we utilize a dashboard. Our product development backbone relies on two-week sprints. At the beginning of each sprint, we conduct a planning meeting to discuss and challenge the backlogs. Throughout the sprint, we conduct daily sessions to review code, ensure alignment with coding standards, and address any issues. Once all tasks are completed, we proceed with the deployment process.

We conduct daily requirement meetings to facilitate communication.

The product should improve its communication. My English proficiency is not high, but writing in English is another skill that you need. Maybe AI can help here. Because I can see in some other applications, they have AI helpers. So when you write something and you want to do something, it can help. For example, Google Cloud Platform has it. They have a helpdesk for it. When you want to create a cluster, it can help you. 

I have been using the product for more than five years. 

Jira Align is stable. 

The tool's scalability is fine. My company has more than 10,000 users. 

The tool's deployment is complex. While the user interface is fine, when you want to report and obtain information about the previous experiences of a task, you need to search extensively. The search functionality is not effective, especially for accessing historical data on tasks and sub-tasks from, for example, one month or three months prior. It's not perfect for searching.

Our in-house integrators did the deployment. 

Regarding the team, we might benefit from implementing codes for psychology and communication. The presence of people from various countries can lead to challenges in communication. Therefore, it would be valuable to bring in professionals to assist in establishing communication practices. 

We have a team that helps us to plan and fix the product. We have our project reports every month. We email them to our managers and CEO. 

Jira Align stands out as the best product I've ever encountered in my professional life, especially in production and development. It captures the activities of the development team.  Personally, I find the timesheet feature within Jira highly effective.

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.

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 generally use it for reporting. It's to have transparency, to get to the incremental values. We do have value streams built up on Align and we get the metrics, how the program works, or the dependencies, not just between the teams, between the programs, or between the portfolios.

What you have in Jira are the scalability and the agile approach. It's all about getting to all the stakeholders or the enterprise users so that they can see what is happening from the bottom to the top or from top to bottom and how it's happening. 

When it's all other agile tools, you could just view what each team is doing, and how the work is delivered within the team. However, it is going above and beyond the teams. When you are doing a scaled agile, when it all involves the whole enterprise, you use the Jira Align. It's a combination when you try to do the scaled agile combining the teams, combining the programs, and combining the portfolios, that is when the Jira Align is of most use.

We use Jira Align on top of Safe 4.0 right now. They're not supporting Safe 5.0 yet, however, they are using it as VR; I used it on top of the framework as Safe 4.0.

We brought it for a very big program. Before that, everything was all silos. The teams were independently working and there was a lot of dependency from one team to another team, which was either tracked in Jira in the roadmap, and it was all over the place. Once we bought the two and tried to combine the teams, depending on what their objective is or what they're working towards, combine the teams and make them into our programs and combine the programs and make into our portfolios, what we saw was a huge value-add. It was transparency. You could see the vision, and the transparency is what was the most beneficial thing - that, and dealing with the dependencies.

.For example, if you have so many teams working towards one goal, not everything can be understood, done in silos. You have to group them in a value stream so they can work towards that one value, and even when they're working towards that one value, you would see a lot of dependencies between the teams and between the programs. Managing that and delivering that on time is what when we push it towards a scale agile with the Jira Align as the thing that holds everything together is what we saw most beneficial

Of course, after that, you would get further enterprise agility, business agility, et cetera, when you start using it more and more.

The objectives are good. If you do use a scale agile, the concept of moving objectives and moving your team's work towards the objective is what is going to give you the most value. You plan around the program increments. That's what the program is about. You plan around the program increments, you do the inspect the workshop, you do the retrospective and all those things. However, for example, when a stakeholder doesn't understand the feature, or they don't even care about it, yet they have an objective or a theme, they move towards it. It makes the objectives very clear, and very obvious.

When you try to move work where the stakeholders know what it is and what they're moving towards, at the same time, when you break down the work, the team can understand what they're working toward. A program manager would understand what they have to deliver in a particular timeframe. That kind of split, you could see. There's great visibility there. 

I really appreciate that Jira Align gives the concept or the functionality of what is called a work tree or a roadmap, which brings it all together and gives you a view of what the company or team is moving towards and who is contributing to what. The OKR experience is great.

There are fewer customization options in Jira Align due to how it was designed.

For example, in Jira, you can combine stories and you can create an epic. However, in Jira Align, they combine the stories and call them features you can combine features and call them capabilities. You can combine capabilities and call it epic. It's structured differently from Jira.

You just cannot buy Jira Align and just started using it. You can, however, the most beneficial thing comes when you start using Jira, and then integrate it with Jira Align, and bring in all the work done together as the actual work is done in Jira, and Jira Align is just a representation of that work.

It's the naming convention that everyone is struggling with. Jira is more widely used and has a bigger customer base. They shouldn't change the terminology if people need to use Jira in order to get the most out of Align and then have the two different naming designs. It's very confusing.

The UI needs work. We are part of the pilot team who are testing the new UI. Jira Align is trying to change the UI so that it is just like Jira. We didn't like it as the UI makes the functionality kind of change. If you have never used Jira Align and you are a brand new customer who used Jira, the sales pitch would go better.

There are lots and lots of reports and it's very hard to understand exactly how we can use all of them. It's quite dense. They need more documentation.

I started using the solution in 2020.

They have done a lot of work fixing bugs and making all types of enhancements. They are working to make everything more functional for agile. 

The stability is very good. Our company was very mature and they have 800 programs in it and ten big portfolios. Jira Align does handle everything with no issues. We don't often have big performance problems. However, for example, if you try to load the roadmap for one big portfolio, it does take time. That is understandable as it's loading huge amounts of data. Other than that, it is actually good.

It is very good at scalability. It's not complete scalability, however, Jira getting integrated with Jira Align is great and it scales that way. If Jira Align is open to getting integrated with other team levels, and managing the work tools, then it would be easier. Right now, to use the Jira Align, either you have to use it as a silo, or you should have Jira in the backend. You cannot have other tools. A lot of enterprises would have other Azure tools or Microsoft tools, from which they manage the team's data, and they would be hesitant just to move to Jira Align as they are using some other tools which cannot be integrated. 

Right now, we have more than 5,000 users on the solution. On Jira, we likely have more than 20,000 users. Not everybody needs to be on Jira Align. It is being used extensively, however.

The support was good. They recorded all of the training sessions, for example. They really helped us learn the tool early on and were very supportive. 

In terms of ongoing support, we do have weekly calls where we go over support tickets, issues, bugs, et cetera. We have regular productive TAM meetings. 

Positive

We did not previously use a different solution. 

I was not part of the deployment. That said, looking at it, it seems to be very user-friendly and would not have been a hard setup. I'd rate it a four out of five in terms of ease of setup.

The deployment took more than two months. It's not full-time and we didn't rush through it. We didn't do it enterprise-wide either. We had a lot to consider and we were being strategic. Likely, if you were aggressive, you could do it in a couple of weeks. For us, bringing in the scale agile concept did take a lot of time. Once we figured that out, there was just connecting and creating and mapping the states and all of that was pretty straightforward. There's pre-work to be done, however, it's worth it to take your time. 

We do have a solution architect from Atlassian that helped us with the setup. It wasn't a hand-in-hand implementation. there were training sessions. 

The person who helped us and ran the training was very supportive and very pleasant to work with. What they taught us via training was about Atlassian, however, the setup was so specific to our company, that without having an extensive background in our organization, they really didn't have the capacity to go beyond training. We'd have questions like "what if we did this, or that?" and they would have to circle back to a program manager to get the answers. That said, they did cover all of the topics. 

I can't speak to the exact pricing. 

We are customers and end-users.

We are using the most recent version of the solution. We're using an enterprise edition cloud.

I'd advise users, if they have Jira, to just go for Jira Align. Just start off with a small number of full licenses. You don't need to have a lot of full licenses just to implement Jira Align. With us, we could actually see what's happening in the organization. The silos disappeared. People can see deliverables and objectives more clearly. It helps bring a lot of motivation.

I'd rate the solution nine out of ten, having never used any other enterprise agility tools.