How to ensure interoperability between projects?

[Michel SE]

Our organization includes several streams in charge of delivery and maintenance of several solutions constituting our IS Lanscape.

Teams need to work separately but need to be able to share and exchange issues like bugs and change requests for example. Root cause analysis of a bug initially sent to Application1 may conclude that bug is in reality in Application 2.

How should be create Projects in Jira to allow such possibility of collaboration?

Do we need to create a kind of Master Project with a specific configuration (or scheme) and have all our projects using this configuration? Would this Master Project be the unique place to maintain the configuration where any change (addition of a new field in an object) would be automatically propagateds to all projects?

[Ryan Fish · Accepted solution]

@Michel SE

There are lots of options for you, here is some stuff to think about:

• Each board is only a view of whatever its specific JQL query returns.
  • If each team has its own board, then they can view their specific teams work.
    • But, they may have some transparency issues because they can get in the habit of only looking at their team board.
  • A master board with subordinate team boards may require defining the workflow as issues move from master to subordinate and (assuming) back to master.
    
    • board configuration, column configuration, and status assignments make this work fairly well once the workflow is defined
  • A single board can be used too, with swimlanes and quickviews to delineate between teams, developers, etc. 
    • Large quantities of teams and/ or developers make for a lot/ too much of viewable information.
• Dashboards supplement the above approaches. Gadgets display queries and views for teams and individuals.
  • Requires some amount of maintenance if team membership changes

Hope this helps 

Ryan