Hi @Lucas Ferreira
Unless something was fixed recently, that may not be possible from an automation rule in Jira Cloud without some workarounds...I spent a bit of time on this more than a year ago and here is what I learned:
There are known defects where the changelog for list fields like Sprint, Fix Version, etc. are not accurate when values are added / removed over time. This is worsened for version fields because the are multiple paths to create a new version and assign it to an issue. What this means is the {{from}} and {{fromString}} smart values are not reliable for the changelog when the Sprint field changes.
One possible workaround requires three rules:
- The first rule, triggered on Sprint Started, branches to the issues in the sprint, and adds an indicator Label value (or sets a custom field) to mark them as "In_Current_Sprint". Let's assume we use a Label value.
- Another rule, triggered on Sprint Completed, branches to the issues in the sprint and removes the label
- The last rule, triggered on any changes to the sprint field uses conditions to check...
- Is the label present
- And with the JQL condition, is the issue not in openSprints()
That last rule is the one which determines an issue was removed from the original sprint scope.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.