I'm new to Atlassian and am running the free trial. Loving it so far.
I've set up a few projects which are all the various component parts of my company and created issues within each project.
I've also created Epics for future versions of the web-based projects with each issue assigned to an Epic (or version).
What I'd like to know is whether it's possible to create Epics across more than one project so that I can assign issues to their specific project (and therefore team of people), but also assign those issues to a global Epic (or version) so that issues in different projects which are related can be viewed under the same Epic (or version name).
Perhaps this is not intended usage and there's a "proper" way to do this?
While it is possible to assign any story to any epic in any project (as long as it is visible in the board), it may look a bit confusing for stories to cross refer Epics from other projects. I would suggest that you have an umbrella project which contains the Epics and then the stories from other projects refer to these epics.
Also also this should be done, only if you are unable to manage the epic-story relationship within one project itself.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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