Automation to automatically fill fields of issues added in Active Sprints?

[Lucas Ferreira]

Hey everyone!

Something we need to improve here in the project is the tracking of issues Added Mid Sprint, as a way to measure how reactive the teams is being and/or the ammount of 'last minute urgent requests' we've been receiving.

For that, we've been using an 'Added-Mid-Sprint' label on every card that is added to an active sprint however, it's quite risky to do that manually and sometimes mistakes may have happened where someone forgot to add that label.

With all that said, I was wondering if/how an automation can be created for: everytime an issue (task/bug/story, etc) is added to an Active Sprint it gets automatically filled by that label I previously mentioned?

Or even, if anyone has any other better ideas of how to better track this, I'm very open to suggestions, I'm just using labels because they are quite easy to filter and query on.

Thanks in advance!

[Mark Segall · Accepted solution]

Hi @Lucas Ferreira 

You could do this which will trigger the rule when the sprint value changes then validate whether the issue is in the current sprint and then add the label.

• TRIGGER: Field Value Changed (Sprint)
• CONDITION: JQL

  • sprint in openSprints() AND key = {{triggerIssue.key}}

• ACTION: Edit Issues (Labels)
  • Change to Add/Remove
  • Add: added-mid-sprint

[Lucas Ferreira]

@Mark Segall that worked! Thank you very much for your quick response, this community is incredible!

[Bill Sheboy]

Hi @Lucas Ferreira 

Has the team considered reviewing the built-in sprint report, such as during the retrospective, to see this information?  That will show the additions / removals of scope for the sprint, and will not be impacted in the event someone changes the labels before they can be reviewed.

That report is available for company-managed projects: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/

If instead you are using a team-managed project, the sprint burndown report has this information : https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-team-managed-sprint-burndown-chart/

Kind regards,
Bill

[Lucas Ferreira]

@Bill Sheboy yes! We actually use the built-in Jira reports during Retros. However, this is a manual report I personally build every sprint-end to the Organization management and I currently manage 3 teams, so to go and check 3 different Jira built-in reports while I build my own takes much more time if compared to running a query and getting these information out of labels. Do you know what I mean?

[Bill Sheboy]

Thanks for clarifying, Lucas.  And yes, I understand that level of effort for reporting to management on the specifics of team workflow activity :^)

Have you considered building a dashboard (or Confluence page) others can go see and pull when needed, rather than sending a report?

[Lucas Ferreira]

@Bill Sheboy Yes, the report I build is on a Confluence page and I usually export it to a PDF file however, I need to fill/update it constantly (bad thing is that the page formatting usually breaks when exporting as a PDF).
And yeah, I also have some Jira dashboards set as well, but I find them a little bit 'limited' regarding different visuals, and usually the new different gadgets neeed to be purchased :/