I know the workaround that we can create fake sprints which can be further used as buckets but not in the favor of this workaround, any other way to acheive this?
Hi @Amit Bhola
At what scale / granularity are the items you are planning for 3, 6, 12 month planning horizons?
After timeframe-based planning, do delivery teams plan / work-breakdown items before build?
If these are large requests and a delivery team then executes on them, you may want to investigate using Jira Product Discovery. This is a newer feature of Jira Cloud, although it now has additional licensing costs. With this you could:
Please look at these sources for more information:
https://www.atlassian.com/software/jira/product-discovery
https://community.atlassian.com/t5/Jira-Product-Discovery/gh-p/jira-product-discovery
Kind regards,
Bill
Alternatives that come to my mind:
The disadvantage of both is that you have to manage the field value or the labels manually. Maybe if you create automation rules to help with it, and trigger each automation with a user-clickable button "Move to yearly bucket", etc. then it is more intuitive.
But it still doesn't support drag-and-dropping in the Backlog view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes! Custom fields or Labels is another workaround with the limitation of no drag and drop. Thanks @Aron Gombas _Midori_ for your input, I'll keep the forum open for other best practices.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.