Hello,
I'm trying to create an automation to set an Epic's due date to the last day of the sprint to which the Epic is assigned to.
If possible, an even better automation would set the due date at the last day of the sprint + 16 days, to include other processes that need to take place once dev is completed.
The trigger would be any change to the Spint field, for the action, I guess I need a smart value and would appreciate assistence with it.
Thanks
May I suggest this is a bit of a strange use case, for many reasons:
Also, sprints are meant to be planned up-front and then run with a minimum of scope changes. That's why you have automation events specifically linked to the creation / start / completion of the sprint. There's no specific triggers to respond to an issue being added to a sprint. If you absolutely want to set the due date to issue, it may be a more scalable idea to do so when the sprint is started:
Visually, the rule would look like this:
Hope this helps!
Thank you for your response.
I think I may have not made my intention clear, though I agree there're definite cons to assigning Epics to a sprint.
The idea is to assign an Epic in advance to the spint in which the dev part will be complete, this will mark QA to plan feature testing to the following sping.
To show the Epic on the advance roadmap timeline I must also have a due date (sprints aren't showing as my source is a filter), so I'm looking for an automation to add the due date to the last day of the sprint + 16 days.
I hope that's clearer.
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.