I'm just getting started with JIRA and trying to figure out what is the scope an issue within a JIRA project. So far what I have seen in 101 reading and playing with it is that the scope of the issues are only for that project and each project has their own issue workflows, components, versions, etc to define those issues.
Usecase: If I have product A, and that product will have a set of versions, components, etc. and requirement is track issues accross the lifetime of the product, thru various versions/releases, etc. Each version/release is managed and sort of like it own project and in each one new components added or the assignees can be changed.
This looks like it will work if we have a single project in JIRA for product A. The question is can and how could we setup if we wanted to have this broken into multiple JIRA projects (one per release/version)? Some way of linking issues accross JIRA projects?
Hope question is clear and usecase makes sense.
Firstly, why would you want to have multiple projects for very version/release. You can tag each issue with the affect and target versions and that way they are all traceable in future.
If however you do want to break down a project into multiple projects you can move issues over to projects.
Linking of issues is again a feature in Jira. have a look at these URLS.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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