-
Suggestion
-
Resolution: Unresolved
-
None
-
136
-
Problem Definition
- Advanced Roadmaps allows Grouping Issues by assignee, projects, components, and teams. Allowing Advanced Roadmaps to Group by any custom field would provide flexibility when grouping issues into separate swim lanes.
Suggested Solution
- Expand this grouping capability to Group by any custom field.
[JSWSERVER-25190] Allow Advanced Roadmaps to Group by any custom field
+1
Another feature which is only available in Cloud.........I'm so fed up with Atlassian on the lack of DC features currently!
https://support.atlassian.com/jira-software-cloud/docs/group-issues-on-your-advanced-roadmaps-timeline/#When-grouping-by-custom-field
Delivered a year ago.......https://jira.atlassian.com/browse/JSWCLOUD-21708
How F#€&& hard can it be to implement the same simple grouping functionality for custom fields?- It is the 80% to 100% the same development change that needs to take place here!?
I have +10 missing features, which is ONLY made available to cloud customer only........it is now clear to me, that you are slowly forcing customers into Cloud edition(Which I as customer DON'T want....and Cannot have)
Don't fuck the customer Atlassian! If you keep this shitshow up, i'll end up as an Admin on BMC Remedy, HP Service Manager or even your worst competitor........SERVICENOW!
Is there any update if this JIRA will be progress as it will significantly help planning.
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
Please add this feature to Jira data center Advanced Roadmaps. It would be very helpful to be able to group by a custom field. In our case there's a custom field to identify the team that owns it. Being able to group by this field would help immensely in organizing the roadmap by team. It's not an option to use the AR "Team" grouping, due to the overall design in our large scale instance, Components would also be duplicate work and create a risk of mis-matching. I've also ruled out the other "out of the box" options, they just won't work cleanly. But being able to group by a custom field would be soooo helpful!
+1 for Cloud, would love to see this work for multi-select fields (okay for it to show up twice per the previous comment)
group by filter under plans is very inadequate. Most of the fields are not available.
Since AR essentially doesn't have an API, this would allow us to drive Plan organization from the Jira API side, providing a workaround.
+1 also for the good comments above. Labels are fragile and have undesirable additional scope visibility.
We have a similar situation where we use a custom multi-select Team field in Jira as initiatives may cross multiple teams. I need to be able to group by these custom teams - NOTE it is OK for the issues to show up twice this is exactly how it works with sorting by Labels which is the only work-around I have found - however using labels carries a lot of additional overhead for users to add them to all the issues manually in the heirarchy.
Yes, yes, yes we need this in Advanced Roadmaps.
Imagine the situation... I have a set of teams grouped by discipline (iOS, Android, RW...etc) that are organised as to manage their sprint planning by capacity, but across those teams I have a vertical 'feature groups/workstreams' which I want to view progress on. Yes I suspect I could use filtering of component/label, but that leads to unnecessary complication or misuse. Creating a custom field which is then administrator controlled gives me the option of creating standard views across our various Portfolio of projects/programmes.
+1
Using labels as a way to group things in the Portfolio is not ideal, the group config being a list of "OR"s instead of "AND"s make it even worse, creating the need to have weird labels that don't mean anything, they just exist for a specific group in Portfolio.
+1 for cloud
This would be extremely valuable and means we don't need to use components and labels for things they're not intended for just to group properly in plans.
Definitely a requirement to add dimensions to delivery plans.
I think there should be a way of enabling groupings at different levels of the hierarchy (as you might want to group tickets in different ways when considering lower level entities)
Same here! Would like this for cloud on Advanced Roadmaps on JIRA
Hello Mauro,
I have recently faced the same situation and found the following workaround: I created a Select List with themes that are pretty static for our company, and a labels list custom field with themes that projectleads could define and extend themselves.
These fields have a field context that only allows usage on epics. After I added the fields to my roadmap I can group epics by those custom fields.
Hope this helps,
Andrej from greenique
Please do include this ASAP.
I'm struggling with setting up Advanced Roadmaps and having the flexibility of having Epics connect directly to Themes, without the need to have an Initiative. I believe that is impossible right now, so, grouping by a specific custom field, would allow a similar view.
This feature will help us see our roadmap view across our primary goal for the quarter. Thank you for implementing it!
Yes, please enable it, it's critical for many roadmap views on the portfolio views.
+1 to getting this feature added; this would help a major roll out across teams to use Jira plan
only just started using this product and am shocked this wasn't already included,
+1