Automation Help - Sprints, Reporting

[Dylan Lenton]

I'm doing some testing to try to automate some reporting aspects of the organization. Currently using Jira 9.12

Right now we're testing out using some of the plan/program views for C-Suite staff. 

I'm testing out different ideas on automating certain status updates. 

One that I've been thinking about is flagging projects based on risk conditions being met. 

For example: if I were to have a sprint complete and the team missed 25% of their planned story points, would I be able to update a field?

Or another scenario could be based off of time logs, if the estimate is 5 days, the due date is 3 days out and only 1 day of work has been logged, triggering some kind of alert actions? Sprint completion seems to be the more pertinent option as I think the granularity of individual issues would not be helpful at an executive level.

[Dave Liao]

@Dylan Lenton - hi Dylan! 👋 Hopefully you made progress with this? As you might guess, certain signals are easier than to capture than others.

Here's an example you can expand upon.

⚡️We're going to make an Automation rule in your project. This rule will compare the number of resolved sprint issues vs. total sprint issues, and take an action if the resolved number is lower than a desired threshold of the total.

1. Trigger: Sprint Completed

• 💡In a real situation, we might choose the Scheduled trigger. Having this rule run weekly / bi-weekly allows us to proactively manage our sprints.

Pull the issues in our open sprints, and saved the count to a variable: 

2. Action: Lookup Issues

• Use the JQL sprint in opensprints()

3. Action: Create Variable

• Name the variable totalSprintIssues
• Use the Smart Value {{lookupIssues.size}}

Now, pull completed issues from the open sprints. Save the count to a different variable:

4. Action: Lookup Issues

• Use the JQL sprint in opensprints() and resolution IS NOT EMPTY

5. Action: Create Variable

• Name the variable resolvedSprintIssues
• Again, use the Smart Value {{lookupIssues.size}}

Now let us compare the two variables we made:

6. Condition: Advanced compare

• First value = resolvedSprintIssues
• Condition = less than
• Second value = {{#=}}{{totalSprintIssues}} * 0.5{{/}}

For this example's second value, I wrote 0.5. This means that if less than half (50%) of the committed sprint issues are complete, then the next action (below) will execute.

7. Action: Whatever you want.

• Email the PM team or Slack in a shared channel?
• Consider using branches to have more control over what happen when.

Note to anyone else reading this: If you're using a Jira Data Center version prior to 9.x, you might not have the Create Variable action. You will need to record your found answers in another way, like a Custom Field.