Please share with the community what you think needs improvement with JIRA Portfolio.
What are its weaknesses? What would you like to see changed in a future version?
We would love to be able to have direct contact with Atlassian. Currently, they are not working directly with West African countries. We are considering using JIRA Align, but when we contact them, they say that as we are in West Africa, they don't directly work with West Africa.
Converting a task into an epic is very troublesome. As it is now, if you make the mistake of creating the wrong thing then you just have to delete it and start again. If you could convert between things such as features and tasks then it would be helpful.
Some "help" on each tab should be included in the tool, for those people who do not have previous experience with it like how to filter part of the portfolio or project, how to easily set the versioning based on Release management best practices, and in my opinion, nobody should delete a task inside the team. There should be a log to track all movements of cards, any change on dates, due dates, responsibilities, etc. Another thing could be to have an easy way to manage the Portfolio and have more ways to share and to show graphics and reports
Today, when we want to prepare PI planning, we have a dedicated plugin, which allows us to print a ticket. We have beautiful tickets which is an advantage. We can print tickets and put them right on the wall. It's better for PI planning due to the fact that you can read information, and it's always written in the same way. On each ticket, you can see priority, version, et cetera, always written in the same way. If you write it directly, however, it's not always readable. JIRA Portfolio can help you during PI planning because you can write your dependencies directly. However, it would be better if you didn't have this manual part of the process. If we don't have to print a ticket and to put a ticket on the wall, it would be easier. It's very difficult, for example, for sizeable companies to find large rooms to do PI planning. With coronavirus, we have to work from home. PI planning needs to be re-imagined. It needs to be virtual, not physical. It would be better if it was more like Klaxon, where your ticket is pushed to a blackboard. JIRA is very poor at reporting.
I think their view needs to be more user-friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using. There are many issues, but I would say the UI needs to be improved most. Also, some training documents need to be there with respect to their configuration. They don't have training documents easily available. You really need to figure it out by yourself. That is something they must improve.
The workflow needs improvement. The product itself could be improved in many ways, but at the moment I don't have anything very specific to discuss. It might be helpful to have a simple version of the solution built for a small number of users that would be fast and have a straightforward installation process.
I think to improve the product they need to work on integration. I think what I call heterogeneous integration into other tools will be important. It would be nice to work with data modeling from any tool. From an enterprise reporting perspective, you definitely want to be able to take core data, put it into any sort of raw database and be able to manipulate it to get the information you are looking for. I think the reporting side is probably where JIRA is not the strongest product in my view. Needed improvements just boil down to an improved integration. I know it is always going to be a challenge to add new features, but I think better integration around Microsoft or other core applications would help. I think big data warehousing is important. Enabling RPA for the benefits that can offer would help as well.
The stakeholders have to decide to use JIRA and that's the problem. Not all the stakeholders are in touch with JIRA but we need their budget for the whole team to get the opportunity to use JIRA. It's not a problem with the tool, it's our organization. Some of the stakeholders have other opinions and they like to use other tools. The initial setup could use improvement.
I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear. Now we are using next-generation projects, so it's simpler to set the projects up than it was in the past. There is some work to be done there to have a clearer interface and workflow of how to organize a simple software project.
We would like to have an option for a secure board that we can give to our clients that would allow them to see certain aspects during development, but not so much that they can steal all of our information. A dashboard specifically for customers would improve this solution. Sometimes I have a customer-solution in addition to the more general solution. I would like to be able to differentiate these using perhaps a different color. If I get a feature but there is not a user story, and I want to know which epic it belongs to, it is really hard to figure out. It is hard to work from the bottom up. If you tap on your epic you can see its features, and if you open its features you can see user stores. If you go on, if you are going from top to bottom, it works well. However, if you want to go from the bottom up, it is very hard to do.
I would say that there's a lot of reporting on the dashboard so something that can be improved is the project level visibility because it is a little unclear. Especially when you compare it to JIRA Central.
There could be many things that could be improved but we haven't been working with it long enough to accurately find the weak points. The pricing of add-ons could be improved. You should have the option to pay only for the users concerned, that would be fine, because of the dashboards everybody has access to the dashboard. This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing.
Generally, I'm a happy customer when it comes to this product. The product's speed could be improved. However, there is really no software that can ever be fast enough. I would like to see more flexible reporting and the ability to customize reports. If the pricing could be reconsidered by the company, that would be helpful to all users and organizations using the product. On a scale of one to ten, one being the worst and ten being the best, I would rate JIRA Portfolio as an eight. That is based on German skepticism. To be a ten is not even being a silver bullet, it's being a gold bullet. Very rare if it even exists. The only product I use that is a ten is TeX (or LaTeX). It is public domain software, 30 years old, absolutely stable, it never crashes, it uses a minimum amount of resources because it has no GUI. That is as close to perfect as a product can be.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.