Show tickets (partly) from another project on my meta/cross-project board

[Ella]

Hi Community,

I would like to know if it's possible to show tickets (partly) from another project on my own project board.

In this case, my team is working in another project together with another team. Otherwise, we just support partly. By our project we create a meta board to have an overview of the whole activities, including our actions in other projects.

When I set a filter, which set up views from tickets of another project, my board will appear in their projects, not our. When I create a new board with more projects, I see all the tickets of other projects. But we just need them partly (our component, our team or our tags).

I hope I can describe my question well.

I am looking forward to your help.

Thank you very much in advance.

Best Regards,

[Nic Brough -Adaptavist- · Accepted solution]

Ok, so a board is a view of a set of issues determined by a filter that you can define.

Usually, this filter is as simple as "project = XYZ", but it sounds like you've already realised you can start to do what you need with "Project in (ABC, XYZ)".

You can make these filters quite complex, although I would recommend that you don't try to be too clever - you should aim for board filters that you can easily explain to the team using the board.  "It's listing all the issues in our projects, plus some from other projects where they need our help (and have somehow indicated that on the issue)".

You say "(our component, our team or our tags)", so I can give you a couple of examples:

• Component: Project = XYZ or (Project = ABC and component = "thingy")
• Tag: Project = XYZ or labels in ("our-team-label", "for-project-xyz")
• Team: This one is a bit more fuzzy, it depends on how you are defining a team and how that is translated into Jira.  I tend to stay away from this one too as I'm gradually moving towards the idea that a Team is defined by the main Board it uses, rather than fixed groups of people (in this case, you wouldn't think about team - it's for the team if it's on their board!)

[Ella]

Dear Nic Brough, thank you very much for your help. I think I did it already, then the new board appeared/sprang in other projects. I want to see it extra in our project, too.

For example:

Our project = project A --> I created here Board 1

Another project = project B

In Board 1 I set the filter:

(project = B AND component = xxx)

Then Board 1 sprung to project B. It disappered in our project A.

I hope I can desribe it well this time...

[Nic Brough -Adaptavist-]

That JQL does not include project A, so the board does not think it has anything to say about project A any more, so A drops it.

You should also consider the component lists - remember that components are project artifacts - the component you have as xxx needs to be a component from project B as you're saying "And project B" in there.

[Ella]

Thank you, so what would be the right code if I want to show (only) component xxx of project B on project A?

I tried: project = A OR project = B AND component = xxx 

The board appears again in my project A, which is great.

But now I see both all tickets project A + project B/componentxxx on this board.

[Ella]

...and can I have 1 board in 2 projects (A,B)?

[Nic Brough -Adaptavist-]

I am sorry, I am a little lost - 

project = A OR (project = B AND component = xxx )

should give you "all tickets project A + project B/componentxxx"

[Ella]

Yes I know it's a bit complex...

I want to see only projectB/componentxxx in one board in project A.

Background is: We want to bundle all activities in other projects to have a better overview. We (team project A) also support project B,C,D, etc.

It should look like that:

In project A.

- Boad B for our activities in project B (component xxx)

- Boad C for our activities in project C (component xxx)

- Boad D for our activities in project D (component xxx)

& Boad META for all activities in project A + project B component xxx + project C component xxx + project D component xxx.

Is it too much in Jira?

[Nic Brough -Adaptavist-]

Ah! I see!

I do not think this can be done - the "belongs to a project" thing is derived from the issue selection in the filter, so if you say "project B and component = x", you're explicitly excluding project A, so the board won't appear as linked to A any more.

What you might want to try (I have not) is forcing that relationship - maybe using a filter that will draw in project A, but only select for issues that would never appear.  So something like

(project B and component = x) OR (project = A and status = Closed)

That assumes "closed" is a status that issues land in after they've been through an ended sprint, or is not mapped on to the board at all.  If it's a Kanban board with a sub-filter, you could do "and fixversion is not empty" as Kanban boards, by default, drop issues with a fixversion set!

[Ella]

Great you got me! It‘s a fantastic idea, I‘ll try it tomorrow and give you a feedback : -)

[Ella]

It works! THANK YOU very much for your help!

[Sebastian.Glaser]

PSA: this breaks the roadmap...

[Nic Brough -Adaptavist-]

No, it makes the roadmap work properly.

Could you explain your thoughts here?

[Warren · Accepted solution]

Hi @Ella 

I think I understand what you're trying to achieve, try using this as the filter for a new board

project = ABC OR (project = XYZ AND component = xxx)

where ABC is your main project and XYZ is the other project. 

That should show all the tickets from your main project (ABC) and only the tickets from the other project (XYZ) that relate to your team

[Ella]

Dear Warren, thank you very much for your help. I think I did it already, then the new board appeared/sprang in other projects. I want to see it extra in our project, too.

For example:

Our project = project A --> I created here Board 1

Another project = project B

In Board 1 I set the filter:

(project = B AND component = xxx)

Then Board 1 sprung to project B. It disappered in our project A.

I hope I can desribe it well this time...