Smart Value for Total Issues with multiple Sprint Values

Question

I'm trying to create a Smart Value that totals the number of issues that contain multiple Sprint Values from a JQL query.

Purpose is to calculate number of rollover tickets from the previous month for a report.

I don't have the option of installing or using addons so limited to a solution of base Jira.

Been working on this and best I could think of is the below template..

Any suggestions would be appreciated.

Bill Sheboy · Answer

Some things are the same and some are different for Jira Cloud versus Server versions of automation rules.  I am using Jira Cloud and so cannot experiment directly with the expressions.

Let's try breaking this down into pieces.  To go faster, I recommend creating a separate, scheduled-trigger rule, with only the lookup and a write to the audit log.  That can be called manually for testing.

First, let's confirm what is in the sprint field when there are multiple sprints.  Please try writing these to the log:

{{#lookupIssues}}{{key}}:{{sprint}}; {{/}}

What we expect to see is a list of keys and sprints, for example such as this:

ABC-123:sprint 1, sprint 2; ABC-456:sprint 3; ABC-789:sprint 2; sprint 4; ABC-222:;

Then try checking the counts:

{{#lookupIssues}}{{key}}:{{sprint.size}}; {{/}}

What we expect to see for that one is:

ABC-123:2; ABC-456:1; ABC-789:2; ABC-222:;

The last example as no sprints, and so the size will be null.

Aaron D · Answer

I'm on the Server version and unfortunately unable to share a screenshot.

When running the rule it is returning the value "0" but the true return value should be "2". Audit log is returning success with no error messages for me to see.

Testing the greater than value using .gt(0) still will return a "0" value.

Will the value code change using a Jira Server version?

Bill Sheboy · Answer

Are you using Jira Cloud, Server, or Data Center version?

Would you please post an image of your complete rule, and audit log details, for some context?

The example I provided definitely works in a rule with any trigger for Jira Cloud, as it uses the result of a lookup issues action, not for a sprint from a sprint-related trigger.

And...context is key for smart values:

* when the trigger is for a sprint-related one, {{sprint}} refers to that trigger sprint...
* however if once inside a rule, if there is an issue in scope at a particular point in the rule, {{issue.sprint}} and {{sprint}} are the same thing; it is no longer the sprint which triggered the rule