Jira Align Reviews

I have used Jira Align for project management. 

Jira Align improves working efficiency for every project manager or customer by providing utmost transparency. Project managers can easily obtain a comprehensive overview of tasks using Jira Align, and their working speed or efficiency drastically improves with the product. 

The interface of Jira Align is very easy to use and manage. In comparison, the interface of Microsoft Azure DevOps is complicated with too many items and options. 

The vendor should implement automation features in Jira Align. The solution should allow simple integrations with other applications like Microsoft Office. 

I have used Jira Align in our company projects. 

I would rate the stability a nine out of ten. I haven't faced any service interruptions with Jira Align. 

It's a scalable product. 

In our company, we have received tech support for Jira Align. 

At our company, we didn't find Jira Align to be useful enough, so our company has presently migrated to a competitor tool known as Microsoft Azure DevOps. 

In our organization, we were previously deploying the solution on-prem, but in the past few months, it's been deployed on the cloud. 

At our company, we were concerned about the cost of Jira Align, which is expensive. 

I would rate the solution as eight out of ten. I would recommend every company working on Google Suite or open-source solutions use Jira Align. For small and medium-sized companies, Jira Align is a more suited product than large enterprises. 

I use Jira as a tool to keep everything in check for our projects. It helps me track and fix any issues that pop up during development, whether it is sorting out problems with the product or organizing tasks for the team. I also use it to store and manage user stories.

What I like about Jira is that I can easily keep tabs on the status of different issues and what the team is working on. It helps me see if there are any bugs or tasks that need attention before we move on to the next steps. Additionally, it is great for team collaboration. We can pass things back and forth smoothly, from the technical team to testing and the project manager. This way, everyone stays in the loop, and we get a clear view of how things are progressing in the project. It has become a really valuable tool for us.

For future releases of Jira Align, I would suggest making workflows simpler and more user-friendly. It would be helpful to have improved tools for visualizing workloads and an easier way for users to collaborate with administrators to streamline complex workflows. Simplifying communication and customization, especially for managing bulk storage and intricate projects, would enhance the overall user experience.

I have been using Jira Align for five years.

I would rate the stability of Jira Align as a nine out of ten. It is quite stable.

I would rate the scalability of the solution as an eight out of ten. We have approximately 150 users at our company. If the company expands in the future, we will likely use Jira more for upcoming projects.

For those looking to use Jira Align, my advice is to explore its intuitive user interface and ease of use. If any issues arise, don't hesitate to reach out to the admin team for solutions to enhance workflow and performance. Open communication within the company can lead to a more responsive and effective use of Jira Align for project management. Overall, I would rate it as an eight out of ten.

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.

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.