nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Labeling tickets based on epics

Mara Julin

Im trying to set up a series of automations to label tickets based off their epic. In order to not have to create 1 automation for every epic, I was planning on setting up the automation to look for just an ending like "(A)" that we would just start adding to the epic names we'd want to categorize.

I'm testing this out and while the automation is working for the 4 categories I want (Bugs, interruptions, new features, maintenance) - it is applying all 4 labels for all the epics instead of just the ones I want - anyone know why or how I can set this up so it doesn't need to be updated?

This is the current setup for 2 of the automations and then an example of how for one of the epics all 4 labels still show up.

Screen Shot 2022-05-19 at 5.42.12 PM.png Screen Shot 2022-05-19 at 5.46.20 PM.png Screen Shot 2022-05-19 at 5.47.03 PM.png

Accepted answers

All comments

Mark Segall

Hi @Mara Julin - Can you please share the steps of the rule(s) so we can have more clarity on your end goal? This would help in our ability to assist.

Bill Sheboy

Hi @Mara Julin

Are you currently using the Labels in the epics for anything else? If not...

As you are setting the Labels in the child issues of the epic, I wonder if you could simplify and just set the desired Label in the epic, and then copy to any child issues, with no need to parse the Epic Name.

Kind regards,
Bill

Mara Julin

Yeah I was initially thinking of this approach, but I wasn't sure if it would update any tickets that come in.

In this way I can see sprint per sprint, what types of work are we completing. Based off this would you still suggest that way?

Mara Julin

Yep! I'll attach below, also including more context if it helps:

My goal is to create higher level categories for groups of epics. So for example the label "roadmap" would include epics: project epic 1, project epic 2, project epic 3. Or "tech debt" would include epics related to infrastructure changes. In this way I can see sprint per sprint, what types of work are we completing.

My hope though is that I only have to set up 1 automation for each of these things, and don't have to add a new automation whenever we add a new epic. Which is why I was trying to do the "(M)" at the end of the epic name for "Maintenance", etc.

Screen Shot 2022-05-20 at 4.05.49 PM.png Screen Shot 2022-05-20 at 4.06.02 PM.png

Mark Segall

Thanks for the screenshot... It looks like it's just a matter of swapping the condition and the label action. As it stands right now, it applies the label and then looks for whether the epic ends in (M). So it will have applied the Maintenance label to all issues in that sprint, regardless of the Epic.

Bill Sheboy

No, I would not. It seems you are trying to use Labels to represent groupings for hierarchy (e.g. roadmap) and classification (e.g. maintenance).

However you choose to do this, the key will be consistency as you are storing more than one type of information in the Labels field. Other approaches to solve this would be to use Components for one of those classifications, or custom fields with selection lists. The latter would make your automation rules (and reporting) easier to do.

Mara Julin

Thank you!

I am trying your custom field approach with a selection list, I just added it to my project screens and see it on my tickets, however when I go to edit the automation to edit that field it isn't coming up as an option, even when i search.

Any idea why?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud