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 a ticket and maintain status automatically

wabernathy

I want to clone a ticket such that the original and the copy are identical in every way except the project name, and they remain identical if either is modified. Think of the cloned ticket as a symbolic link to the original. So, if the original ticket is ABC-123 (status: Done), and I clone it to project DEF, the new ticket is also listed as Done. If I change the summary or description for DEF, it changes the same field in ABC (or vice-versa). You might also consider this as simply assigning a new name (DEF-456) to the same underlying data fields.

Is this possible? If so, how?

Accepted answers

Bill Sheboy

Hi @wabernathy

It seems you want to do this to maintain visibility of an issue in one project (e.g. ABC) from the other (e.g. DEF).

Rather than cloning (and synchronizing...) have you considered instead updating the board filter to include such issues in the DEF board(s)? You could add a special label (or other field) such that only those specific issues appear. For example:

project = DEF OR ( project = ABC AND labels IN (highVisibilityIssue) ) ORDER BY Rank ASC

Kind regards,
Bill

All comments

Bill Sheboy

Hi @wabernathy

It seems you want to do this to maintain visibility of an issue in one project (e.g. ABC) from the other (e.g. DEF).

project = DEF OR ( project = ABC AND labels IN (highVisibilityIssue) ) ORDER BY Rank ASC

Kind regards,
Bill

wabernathy

Because my company's Jira system is overburdened with (to my eye) dozens of completely extraneous fields, I am hoping to get away from adding fresh tags or labels if I can. Also, if I propose a new label, it invites PMs to start clamoring for a "the PM says this is a release note ticket" label, which is the approach I'm trying to steer us away from. So, if I can keep it all in the ticket's fundamental structures, it's for the best.

This said, I think your approach has merit as one possible solution for these tickets. I thank you for your response, and will definitely keep it in mind.

wabernathy

On further review, and for the benefit of anyone who comes along after, the verb I was hunting for may not have been "clone" so much as "sync". There are third-party tools that promise this ability: Jira apps | Atlassian Marketplace. I have no insight into their suitability (yet...)

Syed Majid Hassan -Exalate-

Hi @wabernathy

This is Majid @ Exalate.

I would love to hear more about why you need to perform this, but from the looks of it, this seems like a local synchronization use case for Exalate. You can fully synchronize your issues from Project 1 to Project 2, and also control that synchronization at a very granular level (each field can be configured etc.).

If you would like to discuss your particular use case further, please feel free to book a demo and I would be happy to assist you.

Thanks

Majid

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server