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; } } }

How to assign a created issue to an EPIC with the same name as its status?

Babak Hosseini

On my board, epics have same names as statuses (column names). So, I want to create an automation rules so that when I create a new issue on any column, it'll assign the issue to the epic with the same name. For example, if I create it under column algorithm, it should be assigned to algorithm epic in that project. Is it possible?

I tried the Epic Name in Edit issue, but it brings an error! Screenshot 2023-07-14 121655.jpg

Screenshot 2023-07-14 121451.jpg

Accepted answers

All comments

Mayur Jadhav_30osel

HI @Babak Hosseini ,

Instead of Epic name did you tried Epic link ?

Babak Hosseini

What to put there to make it an automatic assignment? {{status.name}} doesn't work!

Mayur Jadhav_30osel

@Babak Hosseini , You will have to write some conditions. I think you need to create two automations first when you create a ticket and another when you change the status ( transition issue).

1. Trigger: Issue Created.

2. Condition: if status = (you initial status)

3. Action: Edit issue : Epic link ( Search for ticket number where you want to link)

and second automation,

1. Trigger : issue transition

2. Condition: if else ( status = XYZ)

a. Action: edit issue : Epic link

3. Else

( status = ABC)

b. Action: edit issue : Epic link

Babak Hosseini

To apply it to 8 projects with 6 epics each?

Isn't there a smarter way to do it? Or is it the Jira's bottom line?

Bill Sheboy

Hi @Babak Hosseini

I am curious...Would you please explain the purpose of this board?

Jira boards normally reflect a process for a team to delivery something, from start to end. You instead seem to be describing the board as a list of things meeting some criteria. There are other features in Jira which teams often use for that need: labels, components, custom fields, issue type, etc.

And so, I wonder:

Is this a static board, where things are not worked on/delivered?
If things are worked on/delivered, how do you see progress of work?
Are you trying to use any of the built-in reporting with this board, as I suspect it may not work as intended?

Thanks in advance for any details you can provide!

Kind regards,
Bill

Babak Hosseini

Hi @Bill Sheboy

Yes. You are right. I'm not using this board for a scrum-based DevOps purpose. It's more about describing task lists in an organized way, categorizing them and assigning them to the right person, adding subtasks, linking them, putting comments, and descriptions, and updating the project page on confluence. Well, they are data analytic projects and not deliverable the same way as software devop.

However, Epics in this pipeline have a general notion of workflow as they define main phase of the analytical project's roadmap. It's a back-and-forth between these phases, and tasks are added to each Epic based on the progress of the work.

So, there are no immediate features to release every 1-2 weeks like software devop. That's the difficulty in reporting the progress!!

Bill Sheboy

Thank you for explaining what you are trying to do.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

epic

automation