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 clone and keep sync of issues between projects

Raabe Tatiane Barbosa (DHL Supply Chain)

Hey!

I need to share issues betwwen projects. I could use the automation to clone the issue, but I'm not being able to keep it sync. I'd like that any changes made in one project is also reflected in the other one, like really sharing the same issue

Accepted answers

Mark Segall

Hi @Raabe Tatiane Barbosa (DHL Supply Chain) - It's not the cleanest, but you could do something like this:

TRIGGER: Issue Updated
BRANCH: linked issues (your link type)
- ACTION: Edit Issue
  - Select all of the fields you wish to copy and set to copy from trigger issue

All comments

Mark Segall

Hi @Raabe Tatiane Barbosa (DHL Supply Chain) - It's not the cleanest, but you could do something like this:

TRIGGER: Issue Updated
BRANCH: linked issues (your link type)
- ACTION: Edit Issue
  - Select all of the fields you wish to copy and set to copy from trigger issue

Curt Holley

Hi @Raabe Tatiane Barbosa (DHL Supply Chain)

If sharing, is there any reason not to just use the one issue, but visualise it/them across both projects via a board with an appropriate filter query?

Saves the complexity of duplication and automation, as well as ensuring a single source of truth.

Matthias Gaiser _K15t_

@Raabe Tatiane Barbosa (DHL Supply Chain) I've seen that you've posted the same question here as well.

I kindly ask you to not duplicate content so that the people answering questions here don't waste time when they answer a question which is already answered somewhere else.