How to test automation with sprint trigger?

Laura van _t Wout
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 22, 2024

I want to send a tiny sprint report to Slack when a sprint is closed.

This report should contain the burned points (sum of all DONE tickets) and a list of done tickets.

Questions:

  1. will this work?
  2. how can I test automations with sprint triggers in the future? (all manual triggers are on issue level and I cannot go from there to sprint level...)

Screenshot 2024-02-22 at 11.55.40.png

 

1 answer

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 22, 2024

Hi @Laura van _t Wout and welcome to the Community!

I am just a bit unsure about one part related to your 1st question (will this work). The basics are there, but I am not sure if Sprint = {{Sprint.name}} will work. I haven't tested, to be honest, but I would not be surprised if you would rather need to use the sprint.Id instead.

If you want to test this, you can always replace the sprint completed trigger with a manual or scheduled trigger, so it can fire at any time and hardcoding the JQL you use in your lookup issues action. That way you don't need to wait for the next sprint to complete before you can see the result.

Hope this helps!

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 22, 2024

Hi @Laura van _t Wout -- Welcome to the Atlassian Community!

Adding to Walter's answer...

 

Regarding "will this work", are you using a Company-managed or a Team-managed project?  You may find this information at the lower-left side of the page's expanding area.

This is relevant as Company-managed projects use the {{lookupIssues.Story points}} smart value and Team-managed use the {{lookupIssues.Story point estimate}} one.  Please update your rule accordingly.

 

One good technique for testing rules like this is to create a test project, specifically for rule testing.  You can experiment as needed without impacting your team.

And then when your rule is working as expected, you may either recreate it manually or ask your Jira site admin to copy it from the test project to your team's project.  When done, remember to disable the rule in your test project so it does not unnecessarily use your company's automation allocation.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer