how do I create an automation that notifies me when a sprint starts with a score above the average t

[Luan Castro]

how do I create an automation that notifies me when a sprint starts with a score above the average that the team delivers. Example my team delivers 40 points based on the last sprints, if you start a sprint with 41 points or more let me know. Has as?

[Luan Castro]

and for me to put the average manually would it be like this?

[Mark Segall]

Yes, but you'll need the lookup Issues action before that condition. 

[Luan Castro]

can you give me an example?

[Mark Segall]

See my first response for full context, but you'll want this:

• ACTION: Lookup Issues

  • sprint IN ({{sprint}})

[Mark Segall]

Hi @Luan Castro - You would need a mechanism for capturing average velocity somewhere.  The only way that comes to my mind without some type of marketplace app or custom development would be manual:

Then use automation like this:

• TRIGGER: Sprint Started
• ACTION: Lookup Issues

  • sprint IN ({{sprint}})

• CONDITION (Advanced)

  • {{lookupIssues.Story Points.sum}}
    Greater Than
    <Team Velocity>

• ACTION: Send Email/Send Slack Message/Send Teams Message

Any time the average velocity changes, you'd need to update the advanced condition in the rule. 

[Luan Castro]

I have a gadgets application that shows the average speed, will I be able to use this data?

[Mark Segall]

Unfortunately no - This is calculated in real time.  Since there is currently no capability to look back at last n sprints dynamically in Jira, you'd need to capture this.  Here's a way you could do that which is not the cleanest approach, but an option:

Leverage automation to create a "Sprint Story" at the end of each sprint.  The purpose of this story would be to capture the velocity.  In my example, I'm using a component as a way of labeling these for future use. The rule would look like this:

• TRIGGER: Sprint Completed
• ACTION: Lookup Issues
  • sprint in {{sprint}} and resolved IS NOT EMPTY
• ACTION: Create Issue
  • Summary: Sprint Name: {{sprint.name}}
  • Story Points: {{lookupIssues.Story Points.sum}}
  • Component: Sprint Veloicty

Then you'd tweak the rule I shared above like this:

• TRIGGER: Sprint Started
• ACTION: Lookup Issues

  • Component IN ("Sprint Velocity")

• ACTION: Create Variable
  • varAvgVelocity
  • {{lookupIssues.Story Point.average}}
• ACTION: Lookup Issues

  • sprint IN ({{sprint}})

• CONDITION (Advanced)

  • {{lookupIssues.Story Points.sum}}
    Greater Than
    {{varAvgVelocity}}

• ACTION: Send Email/Send Slack Message/Send Teams Message