Remove label when the sprint has been completed

Kateřina Blahová October 9, 2024

 

Hello,

please can you help me with another of automations?

We add label sprintGoal for the identification of issues that are needed for achieving the sprintGoal.

Sometimes hapend that we don't finish all issues and the Goal for the next sprint needs to be different. So we have to add label to the different issues then in previous sprint. 

We would like to automatically remove the label sprintGoal from all issues in the moment when the sprint has been completed. 

My current automation looks like this

 

Remove sprintGoal label.png

Thank you 

1 answer

3 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.
October 9, 2024

Hello @Kateřina Blahová 

In the Edit action, after selecting the Labels field click the ... button to the right of the Type to find value... field and select ADDREMOVE

Screenshot 2024-10-09 at 2.03.51 AM.png

You can then specify the Labels value(s) you want to remove in the Values to remove field.

Screenshot 2024-10-09 at 2.05.31 AM.png

 

Kateřina Blahová October 9, 2024

Hello @Trudy Claspill ,

I have it, but it is not working. In the audit log there is an information about some errors.Remove sprintGoal label error audit log.png

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.
October 9, 2024

The root of the problem, as mentioned in the error message, seems to be that in your instance there are multiple custom fields named "sprint" so the branch portion of the rule is unable to zero in on using the native, Jira-provided Sprint field to find the issues in the sprint that was closed.

The one that you need is the one that is Locked and of type Jira Sprint Field

Screenshot 2024-10-09 at 9.30.55 AM.png

I recommend that you look into that to determine why there are multiple custom fields with that name. Note that Jira doesn't require custom field names to be unique.  It is possible that a such fields have been created by Product Admins at the global level under Settings / Issues / Custom fields, or created by Project Admins in Team Managed projects.

I advise that you work to get any other custom fields also named Sprint renamed, and then your rule should work.

Alternately you may need to use a JQL related issues condition for your branch so that you can search for issues in the sprint using the custom field identifier for the native Sprint field. You can find that identifier using the View All Issues screen and starting to type in the field name Sprint

Screenshot 2024-10-09 at 9.28.54 AM.png

This should also show you if there are multiple fields named Sprint. In the above, the custom field identifier is cf[10020]. The number may be different in your instance.

You can then use that in a JQL for the For: Related Issues: JQL branch thus:

"cf[10020]"={{sprint.id}}

Suggest an answer

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

Atlassian Community Events