What needs improvement with AgileCraft?

The platform's communication features could be more robust for better team integration.

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

One area where Jira Align could improve is in its licensing model. There was a significant change in the licensing module about six months ago, which resulted in increased costs for customers like us. This change wasn't communicated clearly, and it made it challenging for companies to adopt Jira Align without facing higher expenses. In terms of features, I would like to see improved workflows in the next release, as that would greatly benefit our organization.

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've encountered limitations in using Jira Align for certain aspects, particularly in implementing OKRs. Jira Align's highest hierarchy is Epic, which may not always align perfectly for specific initiatives. Additionally, while Jira Align offers functionality for tracking OKRs and generating dashboards, I've found that it lacks in some areas. As a result, we've explored alternative solutions that better meet our needs in these areas. Its Kanban feature is also limited.

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.

AI is utilized worldwide; they could implement the functionality for notifications and other organizational operations in the product. It would be beneficial in planning, issues tracking, and setting reminders.

Jira Align's cost needs improvement.

One feature that needs improvement is the tool's ability to change schedules automatically. Users can't simply drag and drop tasks to reschedule them without notifying the entire team. This lack of functionality can hinder project management control, as changes should be communicated transparently to all team members. The solution cannot currently alert users when changes occur, which I believe is a function that it should provide. I hope that Jira Align will introduce AI functions to address this issue in the future. We hope to utilize it further to establish connections between the development, production, and sales marketing teams for better alignment. There seems to be a gap between product design and final mass-volume production, possibly due to cost constraints or missing models. It should also improve the support.

The product needs to improve its configurations.

The solution’s stability could be improved.

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.

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.

For an ITSM tool to be maximized in an organization, it should be tailor-fitted. Unfortunately, some are not good at programming these applications. For example, we've used Jira for some time but never configured the SLA. It depends on the person who is programming the software. When it comes to a weakness, I don't know if Jira provides training for people who want to be certified with the solution, so that is one of the problems. We depend on the vendor, and the vendor doesn't have enough time to support us, so we need training from Jira. ServiceNow has a lot of resources. So that may be the game changer there.

One area where Jira Align could be improved is mobile accessibility. Right now, it is mostly for laptops, but it would be more user-friendly if it had a mobile-friendly interface. This way, senior management and others could easily check progress on their mobile devices when they are not using a computer.

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

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.

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.

An area of room for improvement is related to Jira Align's simplicity. Someone who is new to Jira or doesn't have many years of working experience in Jira Align gets easily lost because everything looks the same in the product. The navigational and other workflow features in Jira Align aim to provide ease of use that sometimes creates difficulty for a newcomer or someone new to Jira to get to know where they are once they are in the system. In Jira Align, the navigational feature or the ability to cross over to each screen should be made more precise, and then it would be much more helpful for someone new to Jira.

The tool's corporate pricing is expensive. Continuous planning is non-supported. Only the quarterly "PI Planning" model is available for many of the most useful road mapping features. Dependency management is like throwing work over a wall from one team to another and does not help with engineering-level orchestration of work in delivery.

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.

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.

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

I am really focused on identity access management and getting access to the vendors. Right now, I'm setting up vendor access through Azure. You can do that or with the IAM. Sometimes we have to create several different types of access because we have vaulted databases. We have the Unix databases, I have MySQL, and we have Mongo, where I get access to those user classes or to the databases in the host group. Those are all different access scenario forms that I submit after I do the configuration in the form with the security team. I need clarity on the IAM. I'm not clear on PAM eighter. Is there a form that they have to submit to get access to the internal cyber-risk teams to get their access for people to be able to use the tool on the Confluence side? Do they have to send some kind of form to the operation's security or enterprise security? To be able to get the access for privileged access, do they need to be working on projects that have vaulted databases? I still need to figure out how that works. Other companies that are competitors of Jira and Confluence, are able to create their active directories for the vendors that don't come in internally. They only do access through the cloud and through third-party, two-factor identification. That's something I was wondering if that was already implemented in the packages, the package for Confluence. It would be nice to have that right in the solution.

It should just have the integration with Jira. We haven't looked at it since Atlassian bought the product.