How to add labels

Ri A February 23, 2024

Hi

Can someone guide me please. I am trying to structure a JIRA project using this structure Inititaltive> Label>Epic> Story> Task. 

As this is a new idea I am bring to the team, I want to create a No label epic where tickets that do not follow this structure when created will be saved in. Anyone encountered this before?

Please help.

Thanks

2 answers

2 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 23, 2024

Hi @Ri A and welcome to the Community!

If you are on a free plan (as you indicated when creating this thread), your hierarchy is limited to Epic > Story > Sub-task. You would need a premium plan to extend your hierarchy above epics or look at the Atlassian marketplace for apps that help you go beyond the built-in levels.

A few additional complications I see is that Story and Task are at the same hierarchy level in Jira's fixed hierarchy - right now making tasks a child issue of stories is not possible. Adding label as a hierarchy level is also something I would not recommend, as this is also a system field in Jira. As Jira terminology is already challenging in certain areas, that would create more confusion than clarity with your users, I'm afraid.

Lastly, It is definitely possible to create a placeholder Epic for work that does not fit entirely in your structure. But it is definitely worth thinking about why this work doesn't fit in the structure and if you really need to include it in your portfolio of planned work in that case and look at the way you can adequately manage that type of work.

Hope this helps!

Ri A February 23, 2024

Thanks Walter. I have a premium access for work purposes, I ask question using my personal account here due to restrictions that come with work email. Please can you explain the place holder again?. My thought process here is as I am looking to help the team improve ways of working I expect some errors when they will attempt the first few times. The idea is for those tickets that were created to go into a the "placeholder" epic where I can go through and sort it. Thanks again.

1 vote
Kristian Walker _Adaptavist_
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 23, 2024

Hi Ri,

I can confirm that this requirement could be achieved using ScriptRunner for Jira Cloud and the Script Listeners feature that it provides.

The way this would work would be to configure a script listener mapped to your project.

You would then add a condition in the conditions box to check if the issue type of the created issue matches the issue types you need to run the script for, and we have an example condition to show how to do this here.

The script would be configured to run on the Issue Created event, and in your script, you would check if the issue had the structure of the label required on it, and if it did not, then you would set its Epic link field to be the key of the No Label Epic to add it to the No Label Epic. 

I can confirm the example script here shows a guide on how to set the Epic Link field to add an issue to a specific epic.

I hope this information helps.

Regards,

Kristian

Ri A February 23, 2024

Yes Walter, I understand the logic, I will try to implement it and let you know. Thanks

Suggest an answer

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

Atlassian Community Events