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

Clone verus Link - when to use which?

Lynn Gariepy

Please explain when to clone an issue and when to link issues?

Thanks,

Lynn

Accepted answers

Rahul Aich [Nagra]

Have a look at the URLS, Both concepts are explained in detail

https://confluence.atlassian.com/display/JIRA/Cloning+an+Issue

https://confluence.atlassian.com/display/JIRA/Linking+Issues

All comments

Rahul Aich [Nagra]

Have a look at the URLS, Both concepts are explained in detail

https://confluence.atlassian.com/display/JIRA/Cloning+an+Issue

https://confluence.atlassian.com/display/JIRA/Linking+Issues

Lynn Gariepy

So I did read those pages, but what is the business logic? If an issue is reported in ProjectA, but ProjectB in a different team will do the dev, but the issue will come back to Project A for testing, I think the issue should be linked to a new issue in ProjectB and then when dev is done, the ProjectA ticket will be moved to testing. Is that right?

Rahul Aich [Nagra]

My recommendation would be that you do not manage the issue in different projects then. Give the necessary permissions to every member involved in the issue lifecycle to one project and manage the life cycle at one project using workflow states - Development, testing, release etc. This way you only have one copy of the issue , there is no confusion which issue relates to which. Imagine the confusion if you have 500 issues all duplicated into multiple projects and linked together

Lynn Gariepy

Thanks for the feedback, but we setup Jira project per deparment that manages its own workflow.

Lynn Gariepy

Thank you.

Welcome!

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

Quick Links

Find more posts tagged with

jira

link

clone