I think you'll need to expand on the question a little. What would a "copy" actually do? If you're expecting the source issues to go away, is this actually a merge? If it is not, I'm not sure what you expect from the copy. If it is a merge, then I can imagine logical paths for the history and comments, but what do you do with fields that conflict?
Currently we have two projects, one is for all of our issues and the other is for our managers. What we need is for certain data from multiple issues in our issue project to copy into one ticket in the managers project automatically. This will allow us to hold our managers accountable for what their teams are doing and better provide communication among the four shifts. We would like a ticket so we will be able to look back at previous shifts.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs