Right now I have an automation set to update the Planned Start and Planned End Date fields when the Sprint value is updated on an issue, it will copy it from the Sprint dates in the backlog.This is working as intended, however if we go to update the sprint dates in the backlog - it won't update the issues within the sprint. Is there a workaround for this?
Here's the automation:
Is the automation being triggered? Is so, is there any information in the audit log for the automation?
If the rule is set to update the issues only when the Sprint value in the issue is changed, then it should not be getting triggered by a change of the Dates in the Sprint itself.
The only triggers that I see available for automation based on the sprint itself are Sprint Created, Sprint Completed, Sprint Started. I don't think you can create an automation rule that will be triggered when the dates in the sprint are changed.
The workarounds to investigate that I can think of are:
1. A manually triggered rule (or scheduled rule) that would look at a sprint and then update the start and end dates of the issues in it if they don't already match the sprint dates.
2. For not started sprints, a rule to do the same thing but triggered by Sprint Started.
Hi, Jira users! Do you use Jira alongside Microsoft Teams? We want to hear how you’ve used the power of Jira Cloud and Microsoft Teams (via the Jira Cloud for Microsoft Teams app) to achieve a team...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events