What is the scope of issues in a JIRA Project

[Jose Arteaga]

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.

[Rahul Aich [Nagra] · Accepted solution]

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.

https://confluence.atlassian.com/display/JIRA/Linking+Issues

https://confluence.atlassian.com/display/JIRA/Moving+an+Issue

Rahul