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

Help me, How to automate this?!

Chaitawat Luckanasriwongs_09pu5w

I want to automation this
When I complete the sprint, clone the story issue to other board, where status is done. This part I can solved it as you can see in the picture below.
But the main point is the parent issue or epic is still link to the source board, which is not right, it should create a new epic with the same summary on destination board, if it doesn't existed. So from this pain point, my thinking of this solution is I have to make this automation to check the existing of the parent issue or epic on the destination board before cloning epic, but if it exist, not proceed. Then clone the issue or story issue to destination board.

S
So condition would be like this
When sprint complete, issue with status done must be cloned to other board, by condition if
1. epic of particular story is not existed on destination board, create new one.
2. epic of particular story is existed on destination board, do nothing.
Then clone story issue, and the link to new epic with the same summar

Accepted answers

All comments

Marc -Devoteam-

HI @Chaitawat Luckanasriwongs

This is a request that will still cause mishaps when configured.

My initial question is why, are you doing and what is the requirements for these actions?

Why duplicate information that is in the system and you can simply search for?

Chaitawat Luckanasriwongs_09pu5w

Hi @Marc -Devoteam-
I need this because my organization divided product process into two part and two board, design sprint and development sprint. So I just want the story card from design sprint that is completed and approved, to auto duplicate to other board, so I don't have to double work.

Marc -Devoteam-

Hi @Chaitawat Luckanasriwongs

So for my understanding.

You clone the story for development when the story for design is done, that story is in state done, yes?

You could still clone the issue and link it to the source Epic, why a new Epic as the Epic is completed when Design and Development are done

It would change the setup.

Have an new project where all Epics are made, this can be a kanban project.

Have a project for the development and a project for the design team.

The can still create there own stories, or you clone them via automation , but they are linked to a singe Epic.

Make sure both teams have at least browse permission on the Epic project and adjust the filters on the teams project to be able to see the epics as well.

This will give a more clear view and you don't end up with duplicate Epics

Chaitawat Luckanasriwongs_09pu5w

I want to link to new epic because it's not display on timeline board and I can't plan to roadmap.
The roadmap of this project also separate, design roadmap and development roadmap.
My organization run working process as agile, scrum. but reporting to stakeholders from mother company, they only understand waterfall. So that's why it is mandatory.

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-cloud