For various reasons, we need the ability to not let a story's target start be earlier than a specific date. How can I configure Jira to let the PO the earliest start date for a story and have Advanced Roadmaps not plan to start it before that date?
Hi @Rick Olson ,
If you're using the "Auto-schedule" capability in Advanced Roadmaps to set the dates then one way of achieving this would be to assign the issues to releases with a fixed start date. The auto-scheduler will not set a start date before the release start date.
However, if you're just manually planning then I'm not sure that there's a great solution that I can think of. A warning isn't shown when the start date is manually set before the release start date so that option wouldn't work.
It might be possible to experiment with automation rules? So that when a start date is set you compare against some possible criteria (i.e. the start date of a release and force an update that way). It really depends on if we're talking about occasional issues or a complex set of rules for all issues.
If an issue has a parent then plans will show a warning when the start or end dates are outside of the parent start/end date - but again, this is just a warning and not enforced.
Sorry I can't be more help with this!
Regards,
Dave
Hi Rick,
Been a while since I've worked with Advanced Roadmaps in Cloud (mostly I use Data Center). Is there a Target Start field?
Following the docs, there should be the ability to specify a start date - https://confluence.atlassian.com/advancedroadmapscloud/adding-target-dates-998651513.html . There should be a start date column mapped to a custom field in your roadmap configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.