Jira Project Setup - Two organizations, one Backlog, various projects

[Mascha L]

Hello,

Our organization is working towards establishing a centralized JIRA backlog setup.

Currently, our stakeholders, who belong to a different organization, gather their demands and requests in a JIRA project within their own JIRA instance, to which we have access.

In the future, we aim to transfer tickets from their centralized backlog into our own JIRA instance and then distribute them across multiple agile teams. Each team operates independently and maintains its own dedicated JIRA project/backlog.

Having individual backlogs for each team is essential due to various technical and organizational requirements, such as time tracking, invoicing, reporting, capacity planning, and other team-specific processes.

Our questions are:

• How can we move tickets from a project in one organisation to another?
• What’s the best way to set up a central backlog that integrates with multiple team backlogs in JIRA?
• Are there specific JIRA features, configurations, or add-ons that you would recommend for this use case?
• How can we automate the flow of work items from the central backlog to team backlogs while maintaining transparency and accountability?

Thank you in advance for your suggestions and support!

[Alexey Pavlenko _App Developer_]

Hello @Mascha L ,

You mentioned 'time tracking, reporting' for several teams/boards. After the migration to your JIRA instance, if you need to track several teams in a single view and construct various reports, you can use the app I developed - Multi-team Scrum Metrics & Retrospective:

 

With it you will be able to get the view above for any time periods - sprints, months, quarters, half-years, or years, measure any custom JQL metric and much more.

Best regards,
Alexey

[Pedram Mireftekhari]

• How can we move tickets from a project in one organisation to another?

You can do that with using Atlassian marketplace apps - I do not suggest it as this increase the complexity of work

https://support.atlassian.com/organization-administration/docs/should-i-merge-my-atlassian-organizations/

https://marketplace.atlassian.com/apps/1229958/issue-sync-lite?hosting=cloud&tab=overview&utm_medium=asnwer&utm_source=community

• What’s the best way to set up a central backlog that integrates with multiple team backlogs in JIRA?

The best option is using Jira premium so you can use Plans. If not apps such as bigpicture or structure can do that. Or you can use the automation to duplicate issues in a consolidated jira project (again not suggested)

• How can we automate the flow of work items from the central backlog to team backlogs while maintaining transparency and accountability?

If you use the Plans, issues are synced instantly