I'm using JIRA for managing editorial content and I'm concerned about using multiple projects for the different regions in our organisation, each region has a different workflow for editing their issues(articles) but all the regions use the same issuetypes and need to be able to share and view each others issues - are separate projects an appropriate way of doing this.
If the workflows are different for the same issue types you should use different projects with different workflows.
Sharing issues in Jira is a breeze. You can allow browsing of the various projects by averyone (or certain user groups) and moving an issue from one project to another one is as easy as ". move" keyboard shortcut. The original issue key will even continue to work so that issues referencing a moved issue will still work as intended.
Think: One product == One project.
Group results by filters as needed.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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