Can someone tell me if a Federated JIRA will allow one team to create issues and resolve them (Team A) and then another site (Team B) would get the copies. Then Team B would be able to create issues on a different project and refer to the issues (link) on the read-only copy that they have been synced to (Team A issues). This would allow each team to manage their own projects and at the same time to work together. The new issues that Team B created would then sync back to the Team A's server and they would be able to create or update their issues referring to the link in Team B's JIRA question. The same is true of the GIT repo and that each team would have read/write access to their own Repos and would be replicated on the other side, but the other team only has the ability to merge the other team's changes to their own branches.
The goal is to be able to have multiple teams work together, but not interfere in the development and release of each others' packages.
Ex: Cross-Networks
Team A - JIRA 1 Instance | Team B - JIRA 2 Instance
Read Only - Team B Project <--------------------|-------------------- Read/Write - Team B Project
| (link by JIRA ticket number) | /\
V | | (link by JIRA ticket number)
Read/Write - Team A Project --------------------|-------------------> Read Only - Team A Project
hi Seenu
from JIRA point of view, you may be interested to evaluate https://intenso.atlassian.net/wiki/display/SYN/Communication+Models plugin.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.