I have an automation set up where the due date of a ticket is updated whenever the sprint field is updated and the end date of the sprint is later than the due date mentioned in the ticket.
Here’s a screenshot of the automation:
This works well, but there’s an issue. Whenever I complete a sprint, I roll over all the tickets that weren’t completed to the next sprint. The automation sees this as a change in the sprint field and runs the rule for all the tickets that were moved to the new sprint, which is unnecessarily eating up our automation limit.
I realised I could update the due date when starting the new sprint, and it would only take one automation call to update the due dates for all the tickets in the new sprint.
Here’s an image of the second automation:
This approach would drastically reduce the number of automation calls. However, there’s a catch: I’d need to disable the first automation before closing the current sprint. Otherwise, it will trigger for all the tickets and waste automation limits. After starting the new sprint and having the second automation run, I could then re-enable the first automation.
This issue could be resolved if I could add a condition in the first automation to check if the sprint was updated by a person (manually) versus being updated during sprint closure. However, I couldn’t find an option for this. Also, since the actor for closing the sprint is always the person who closed it, I can’t set a condition like “If user who triggered the rule = Abhishek Chaudhary” because I update the sprint field of tickets on occasion as well.
Any suggestions or thoughts would be appreciated. Thanks!
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.