Showing work in Team1's board that is in Team2's sprint?

[Kurt Smith]

I tried adding Team2's project to the Team1 filter query but it still did not bring in the Team2's story assigned to the Team1 resource.

[Mykenna Cepek · Accepted solution]

The sprints are not "linked". The two projects are completely separate. Sprints are in the scope of a project.

A board is just a "view" on a set of issues. A board shows the issues selected by the filter. A board can show issues in just one project, or across multiple projects.

Cross-project boards can get confusing. An example might clarify what you're seeing:

• Let's assume we have two projects: OPSA and OPSB.
• First let's look just at project OPSA:
  • This project has a Sprint board, which is based on a filter which shows OPSA issues.
  • The issue OPSA-123 is a Story set to be in "Sprint 4" in this project, and "Sprint 4" is the active sprint.
  • The OPSA-123 issue will show in the "Active Sprints" view, as expected.
• Now let's look at the OPSB project:
  • This project also has a Sprint board, but the filter is set to show issues in both the OPSA and OPSB projects.
  • Let's assume that the active Sprint in the OPSB project is "Sprint 27".
  • Remember that the Sprints in the OPSB project are independent from the Sprints in the OPSA project.
  • OPSA-123 by default will only show in the Backlog in this OPSB board. But note that it will be there. This is because it is not assigned to any OPSB Sprint.
  • To see OPSA-123 on the OPSB "Active Sprints" view, simply add "Sprint 27" to the "Sprint" field of OPSA-123.
  • Note that the Backlog view for the OPSB board will show (unclosed) Sprints for both the OPSA and OPSB projects. This is because the filter selects issues from both of those projects (and both of those projects have Sprints).

Note the confusion potential with "Sprint 4" and "Sprint 27" being in separate projects. This is why I always coach teams to include the project key as a prefix for Sprint names. Thus:

• use "OPSA Sprint 4" instead of "Sprint 4"
• use "OPSB Sprint 27" instead of "Sprint 27"

Why is Jira like this?

Jira supports cross-project work at several levels. Epics, for example, can have child Stories from multiple projects. While a single Epic can only live in a single project, all the work under that Epic can fan out to multiple projects.

Since each Project has independent Sprints, the team working on that project can customize their work cadence. For example, the OPSA team might have one-week Sprints starting on Monday, and the OPSB team might have two-week Sprints starting every other Wednesday.

It's not intuitive (to those new to Jira) that the Sprint field is project-heterogeneous. Once you understand that OPSA-123 can be in an OPSB Sprint, things will make more sense.

[Kurt Smith]

Very helpful!

[Trudy Claspill · Accepted solution]

Can you provide copies of the board filter, and evidence of an issue that you think should be showing, and evidence of it not showing where you expect to see it?

[Kurt Smith]

project in ("Operations 2", "Operations 1") ORDER BY Rank ASC

The sub-tasks are now showing, but Jira Cloud linked the two sprints and now it's a mess.  How do I unlink the sprints?

[Trudy Claspill]

Sprints will appear in a board based on these conditions:

1. The sprint was created in that board.

2. The sprint contains issues that are within the scope of the filter of that board.

When you modify the filter of the board, that results in all sprints that contain issues that are within that filter to now display in that board. 

I think you are going to need to provide more details about what you are trying to accomplish between these two projects and two boards, to enable us to provide a better answer.

[Kurt Smith]

I have resolved this problem.  Thanks for the help!

[Mykenna Cepek · Accepted solution]

Sorry, not enough info here to help. Consider posting the JQL and/or screenshots, so we can better understand what you're trying to do, and how it is not working.