Hey all!
I have an automation set for add the label 'Added-Mid-Sprint' to any issue that gets included in an active sprint.
However, sometimes those 'added mid sprint issues' roll over to the next sprint, what makes the label 'Added-Mid-Sprint' to loose its sense fo those issues.
With that said, I'd like to also have an automation for the opposite way, meaning, an automation to remove that 'Added-Mid-Sprint' label to whenever a issue gets removed from an active sprint AND/OR for issues that roll over to the next.
Is that feasible?
Note: Current automation I have to add the label \/
I suggest ignoring the label for issues removed from the active sprint...until a new sprint starts.
That will enable the team to review what happened during the sprint in your retrospective, and more easily see potential improvement opportunities.
Then create a new automation rule, triggered on Sprint Started, and branch over the issues in the sprint to remove the label, using the Edit Issue action with the ADD / REMOVE option.
Kind regards,
Bill
Hey @Bill Sheboy that sounds interesting. Can you help me configuring that automation triggered by the Sprint Started you mentioned?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Certainly; it is essentially what I described:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Lucas Ferreira ,
It's possible, using automation rules you can Automate the label management process .
Try out Colored Label Manager , Learn how to use labels the right way using simple functions like reorder, edit, rename, merge and delete, report on labels and more.
Atlassway Team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Create a New Rule: Click on "Create rule" to start creating a new automation rule.
Trigger: Choose the trigger "Issue transitioned" or "Sprint field changed". If you choose "Issue transitioned", specify the transition that moves the issue out of the active sprint. If you choose "Sprint field changed", specify the condition that the issue is moved out of the active sprint.
Conditions (Optional): You may set additional conditions if needed, for example, to ensure that the issue has a specific label before removing it.
Action: Define the action to remove the specific label from the issue. Here's how you can do it:
remove
function. For example, if the label you want to remove is "OldLabel", you can use something like {{issue.Labels.remove("OldLabel")}}
.You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.