-
Suggestion
-
Resolution: Low Engagement
-
None
-
0
-
1
-
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Motivation
As a Product Owner I want to have more control over the Roadmap generated by JIRA Portfolio 2.0 to achieve the most useful and informative results for my stakeholders.
Background
The idea of generating data driven roadmaps via JIRA Portfolio 2.0 is awesome. Unfortunately the scheduler behaves "too smart" from time to time. Especially when it decides to prepone tickets that were prioritized lower for the sake of filling up sprints and to optimize capacity workload across sprints. The workaround of using dependencies is troublesome since you might end up chaining a lot of tickets to prevent JIRA Portfolio 2.0 to prepone some other tickets which is even lower in the backlog.
Also the automatic assignment of Teams to a Story or Epic is more often a burden than of help.
It's ok, that these functionalities are there. But I would love them to be optional and use only the criteria that I need.
- relates to
-
- Closed
- links to
[JSWSERVER-24892] Make scheduling criteria and automatic assignment of teams optional
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Labels | Original: Plan-AutoSchedule jpos_1029 ril | New: Plan-AutoSchedule cleanup-seos-fy25 jpos_1029 ril |
| Labels | Original: Plan-AutoSchedule jpos_1029 | New: Plan-AutoSchedule jpos_1029 ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 979495 ] |
| Component/s | Original: Scheduling [ 36491 ] | |
| Component/s | New: (Advanced Roadmaps) Plan - Auto-Schedule [ 73716 ] | |
| Key |
Original:
|
New:
|
| Project | Original: Advanced Roadmaps [ 16510 ] | New: Jira Software Server and Data Center [ 12200 ] |
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
| Labels | Original: jpos_1029 | New: Plan-AutoSchedule jpos_1029 |
| UIS | Original: 3 | New: 0 |
| Labels | Original: jpos_1021 | New: jpos_1029 |
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