In Jira automation, how to clone and move epic to another board when its child issues are Done

[Nan Da]

Hi, I have a situation where I have to clone and move epic to another board when its child issues are Done.

When an issue is transitioned to Done status, I need to check if it is a child issue of an epic. If yes, I need to check whether all child issues under that Epic are Done. If its child issues are all Done, I want to clone and move epic to another board. I don't really care if Epic's child issues are also cloned and moved, it doesn't matter to me. As long as the epic is cloned and moved to another board, that would be good enough for me.

How can i achieve this in Jira automation?

[Nic Brough -Adaptavist-]

You don't, at least not by "moving to another board".

Boards are not containers for issues, they are a view of a selection.

I can't think of a good reason for cloning an epic and sticking it on another board, it sounds like you have a clunky or broken process, but if you insist on doing it, then yes, you can do it.

It's actually a lot more simple than you might think.

1.  Create an automation that clones the new issue, and puts a label on it.

2.  Create your board from a filter that says "Label = X"

[Nan Da]

I also think we have a clunky or broken process. May be I will just say in a simplest way about our current process and you can give a suggestion to improve it.

We now have Dev Board (DB) (Scrum board- managed by dev team) and Product Board (PB) (Kanban board - managed by product team).

• Let's say we have project-A as an epic on DB which has many stories.
• After development, QA and PR review are done for a story, we move it to Done (right most column of DB).
• On Done Column, for each issue, we set environment as EPIC_MAIN or STAGING or PRODUCTION depending on which branch a story is merged to.
  • EPIC_MAIN: master branch of a particular project waiting to be merged to staging or production. No more development, QA, PR review needed.
  • STAGING: our testing server where codes are pushed to test first before pushing up to production
  • PRODUCTION: our production server that clients are using
• Depending on environment, the issues are cloned and moved to PB by Jira automation. Product team will manage these cloned issues from there onwards.
• But it's quite overwhelming for product team to manage if all the issues are being cloned and moved to PB. So, the product team is wondering if it's possible to clone and move only Epic (not the stories) if the stories' environments are set as specific one, for example EPIC_MAIN. So, on the PB board, they will see by Epic only, which means by project, without flooding the board with all the stories.

[Nic Brough -Adaptavist-]

Well, clunkiness aside (I'd recommend changing your process so that there's no cloning happening at all), you can still do it with the method I described.

[Nan Da]

For your method, I get the first point. but what do you mean by create your board from a filter that says "Label=X"?