This is a few years late, but I have a solution that works. It is tested in Jira 8.20.10 and A4J 9.0.3. I used web request instead of Slack for notification.
The hardest scenario is sending notification when an issue is moved between an Open and Future sprint. IMHO, the following is a difficult:
from: closed-sprint, active-sprint
to: closed-sprint, future-sprint
Finding the delta between the 'from' and 'to' list using smart values requires using some Set theory and basic math.
The solutions that use the smart value "{{opensprints()}}" do not work for all scenarios. As of version 9.0.3, A4J does not how to call a JQL function inside a smart value tag. So, what you get from {{opensprints()}} is actually a null (or EMPTY) value, because opensprints is undefined.
Solution
I put the solution in github: send-notification-add-remove-issue-sprint
- README.MD - brief description of the rule
- exported A4J rule that you can import into your system
- screenshots of the rule
- low resolution demo video
Premise
An issue's "sprint" field contains all previously participated closed sprints, plus possibly an open or future sprint.
When an issue's sprint is changed, the {{fieldChange.to}} and {{fieldChange.from}} records contains a string of comma delimited sprint IDs.
During any sprint change in the A4J rule trigger there could be at most one sprint change, either one is added, removed, or changed (from open to future, or future to open).
Implementation
My solution uses Jira and A4J features. It does not use JQL or ScriptRunner functions, which someone may have solved it using them.
My solution treats {{fieldChange.to}} and {{fieldChange.from}} sprint IDs as two Sets. By using basic math and set theory (union and intersection), we can find the 'changed' sprint, then we call the REST API "agile/1.0/sprint/{{sprintID}}" using a web request action to get the 'changed' sprint's state to determine whether it's Open or Future.
summarized steps in the rule
-
fromList = list of previous sprints
-
toList = list of current sprints
-
mergedList = fromList union toList
-
removedSprintId = mergedList - toList
-
addedSprintId = mergedList - fromList
-
if a sprint was added then
a. get the 'added sprint' record via REST API
b. if the sprint is active (open) then send 'add' notification
-
if a sprint was removed then
a. get the 'removed sprint' record via REST API
b. if the sprint is active (open) then send 'removed' notification
The solution uses a web request for notification (instead of slack). You can easily replace it with another action such as email or slack.
Notes:
1) We need to update the following to make the rule work for you:
- Replace the web request Jira REST API URL with your Jira's base URL.
- Update the bearer token with of a Personalized Access Token from an account that can access project sprint information: GET /agile/1.0/sprint
- Replace the web request action that sends the notification with another action or your own webhook URL. I used the free webhook.site for testing, but in production, you might want to send email to yourself for testing.
2) There are more details embedded in the rule's description.
3) For what is worth, the rule has simple examples on usage of the following that can be helpful on writing future rules:
![Alexander Eck [Tempo]](https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/default-avatar-5.png "Alexander Eck [Tempo]"){kind=avatar}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.