We 1 project that needs work done from more than 1 team. So in the main project, all the stories will be created and then moved to whatever team will be doing the work.
The PM still needs to see in what state the main project is. Is it all possible in JIRA 5 to have 1 issue cloned to another project in such a way that any changes done on either issue will reflect on both?
Not that I know of.
Most places don't see the point of having duplicates. If they really need a duplicate issue in another project, they tend to create a "stub" and link it to the original with a message saying "go look over there". Problem with trying to keep two issues in sync is that you have to code for every type of change - it gets long and messy quickly.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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