Handling Scrum Sprints

[Zuhair Thabit]

I have a question about managing a project in Jira that involves multiple smaller projects, such as 'X Development Project in Jira Software' and  'X Marketing Project in Jira Work Management', etc. My question is about handling tasks across these projects, especially when one task is completed in one project and then starts in another. Additionally, if the sprint changes in the process, how can I ensure that the completed task from one project remains available in the other project for reporting purposes? What settings or configurations should I use in Jira to manage this situation effectively?

[Dave Mathijs]

Hi @Zuhair Thabit welcome to the Atlassian Community!

A task is an issue in Jira. An issue in Jira can only belong to one project. The issue key uses the project key as prefix with a number as suffix.

In order to ensure the relationship of tasks between projects, create a task in each of the projects and link them together via a valid issue link type.

Please note that there is no project nesting available in Jira.

You need to agree on What is a project first.

[Bill Sheboy]

Hi @Zuhair Thabit -- Welcome to the Atlassian Community!

Adding to Dave's suggestions...

When you want to manage work across multiple teams, Jira has several things to help with that.  For example, you could:

• create a filter and board which spans all the Jira projects, treat that board as "read only" and use it for visibility of the work
• use Jira Product Discovery to manage the full life cycle of work spanning different teams, as described here: https://www.atlassian.com/software/jira/product-discovery
• etc.

Kind regards,
Bill