-
Suggestion
-
Resolution: Low Engagement
-
None
-
1
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Problem
JIRA Portfolio allows very fine-grained configuration and setup of plans, making sure that customers can adapt the tool to their complex planning requirements. However, this complexity leaves room for errors and often times it is difficult to figure out what may have been misconfigured.
As an example, there are a number of possible causes why a certain issue or issues do not show up in the plan. This Atlassian Answers thread lists a number of them.
Suggestion
Following the success of the JIRA Admin Helper, it would be very helpful to have a JIRA Portfolio Helper that could be used to determine the answers for the questions like (but not limited to):
- Why does X issue not show up in my Portfolio plan?
- Why is my release red? (Suggestions on possible solutions)
- What else would fit in this release with fixed release date?
- Why does my capacity report show bottleneck?
- What changes I need to make to my existing projects X and Y in order to see them on the same plan? (suggest on missing releases/fix versions, large delta between teams' velocity, incompatible capacity measures)
Through this feature, customers could self-help and adjust issue sources accordingly, determine the logic behind specific scheduling "decisions" by the algorithm.
- relates to
-
JRACLOUD-89258 JIRA Portfolio Helper
- Closed
-
JSWSERVER-24878 Report on how scheduling logic was applied
- Gathering Interest
- is related to
-
JPO-7950 Failed to load
- links to
- mentioned in
-
Page Failed to load
Form Name |
---|
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center