I'm trying to run a check each time a sprint's start or end date is updated.
The goal is to get issues assigned to the sprint based on a date field of their own.
I have the automation working, but only with a trigger of Sprint started as the start/end dates of the sprint are not populated until after it is created.
Any ideas on an alternate trigger to use that would allow me to access sprint.endDate and other sprint smart values?
Hi @Ellis Coon
First thing, I am assuming that you are trying to automatically assign issues *before* sprint planning, and that during sprint planning the team would make adjustments based on capacity.
On to your question...
There is an open suggestions to add a "sprint updated" trigger, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-22637
Until that becomes available, one work-around would be below. Please note I have not tried such a rule to solve this specific problem.
Depending upon how this rule is implemented, it could take several seconds to run. For example, if this happens based on an issue Due Date change, that would be several seconds per issue. If instead this ran on a schedule, it may be possible to use just one call to the REST API to update several issues.