Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,337
Community Members
 
Community Events
184
Community Groups

extract start date of a sprint from an array of sprint for an issue using smart values in automation

Background: One of the performance efficiency metrics for a team is “Spill-over rate”

Definition: The average number of story points that have spilled over to future sprints in all the competed sprints in a given time range.

Formula: Total number of spilled over story points in a given time range / total number of completed sprints in a given time range

Requirement: In order to calculate the above metric, can I think of approaching this through an Automation by introducing a custom field (SpillOverStart)? 

Solution Approach:

Trigger: Issue field update (sprint)
Condition: If Issue.statusCategory = "In Progress" and {{issue.sprint.split(“,”).size}} > 1
Action: SpillOverStart = {{issue.sprint.split(“,”).get(1).startDate}} (start date of the 2nd sprint (index 1) in the array)

JQL to be used by the Scrum Master for computing this metric: (export the output to an csv and add up the total story points and divide it by the number of completed sprints)

project = <project_name> and issuetype not in (epic,sub-task) and SpillOverStart is not empty and (SpillOverStart >= "2023-01-01" and SpillOverStart <= "2023-03-31")

I am stuck with the above Action as it is NOT working out. Any leads on where I am going wrong or another way of achieving this will be highly appreciated.

2 answers

1 accepted

1 vote
Answer accepted

Finally it worked. Two learnings:

1. Issue.statusCategory does not work as a JQL. So, I had to replace it with status not in (Done,"To Do")

2. split(“,”) is not working or may not be required. So, my Advanced compare condition looks like: {{issue.sprint.size}} > 1 and Action looks like: SpillOverStart = {{issue.sprint.get(1).startDate}}

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Hello @Deloitte Mohajit 

Welcome to the Atlassian community.

In what way is the automation not working?

What does the Audit Log contain when the rule executes?

Have you used the Log action to print out the smart values that you are using to see if they contain the values you expect?

Thanks, Trudy for reaching out.

Automation audit log says "no action performed"

SS.jpg

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

That indicates that the rule was triggered, but the issue that triggered it did not meet the Conditions. Review the triggering issue, which is noted in the Audit Log, and the Conditions in your rule. If it doesn't meet the Conditions then the rule is working correctly, as per the instructions you gave it.

 

You can use the Log Action to print values into the audit log, like the smart values tou specified in tour conditions, to see the values the rule is getting from rhem

Thank you, Trudy for your guidance! Appreciate it.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events