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!
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:
Thanks in advance for any details you can provide!
Kind regards,
Bill
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!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for explaining what you are trying to do.
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.
What to put there to make it an automatic assignment? {{status.name}} doesn't work!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think so they're smarter way than this, lets keep this forum open so people can add their solutions
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.