Pointers on why the Completed Sprint trigger does not run
Asked by Dipen:

Team

The **problem I am trying to solve** is 2 fold

a.Get a count of Story points for a completed Sprint.

b.Get a count of Story points for issues that are in Done status, for that Completed Sprint.

**Previous completed Sprint** ( the one that i would like to run this rule against) is listed in the JQL query as shown below by the custom field name cf\[10113\].

I have Tested the output of JQL using the Validate query button.

I have limited the scope of the output of JQL to 2 rows to test this functionality before expanding the scope.

Have the following **Automation rule** in place

![Screenshot 2024-06-28 094951.png](https://community.atlassian.com/t5/image/serverpage/image-id/332400i8654B467779DAF96/image-size/large?v=v2&px=999 "Screenshot 2024-06-28 094951.png")

**Issue**: The rule does not run. it appears that the trigger - Sprint completed for the previous Sprint is not getting picked up.

Audit log shows just the Configuration changes I made but there is nothing else that indicates whether the Rule is failing or why it is not executing.

![Screenshot 2024-06-28 100350.png](https://community.atlassian.com/t5/image/serverpage/image-id/332407iD56CEEE2D8312B5E/image-size/large?v=v2&px=999 "Screenshot 2024-06-28 100350.png")

Any pointers on what I could be doing wrong would be super helpful.

**Final expected result** is that the Edit issue fields will aggregate the story point values for each issue in the JQL and send an email with the final count.

Hope this information helps

Please let me know if there is any additional information required to figure out the root cause.

Thanks

KD


Answers:
author: Joseph Chung Yin
body: [@Dipen](/t5/user/viewprofilepage/user-id/5462529) -

Need some additional information from you -

In JSM, by default that issue management is done via "Queue" process and not managed by "Sprint" via Scrum board process. Sprint management is typically used for Jira Software application projects and not for JSM.

Can you provide your reasoning behind the usage of Sprints? Also, when you executed your JQL, did the JQL returned the issues that you wanted? (not just simply validating the JQL in the automation rule.

Here is a link on how one can troubleshoot automation rule by using the action of "log action" and one can review the audit log of the rule's steps -

<https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/>

Please advise, so we can assist you further.

Best, Joseph Chung Yin

comments: author: Dipen
body: Joseph

Thank you for your response.

Responding to the questions you posted above

1."when you executed your JQL, did the JQL returned the issues that you wanted? (not just simply validating the JQL in the automation rule." - Yes, it returned exactly 2 rows, which was the scope of my testing.

2. For the time being I am running the automation on a schedule every so often to see what else is broken.

I agree with your comment: " In JSM, by default that issue management is done via "Queue" process and not managed by "Sprint" via Scrum board process. Sprint management is typically used for Jira Software application projects and not for JSM."

This is a team managed software project hence the use of Sprint.

I also want to thank you for sharing the link that shows how to use debug. That should help me find out why the Sprint story point estimate values are not adding up and showing in the Aggregated Story points.

The one additional challenge that I am running into is with the syntax of this statement:

{{lookupIssues.Story point estimate.sum\|0}} - It is not recording any errors, however the Story point values are not adding up.

I am trying to add the Story points estimate for both the issues returned by JQL and show the aggregated value under a new custom field of type Numeric.

Please let me know if I can be of any additional help.

Thanks

KD


Tags: jira-service-desk-cloud

jira-service-management

jira-service-management-cloud