nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adding a project to a board filter

Axel von Arnim

I changed the default project filter of my kanban board from the board settings (General and Filter settings) to be:
project in (A, ORDER BY Rank ASC

to be able to see issues from A and B in my kanban backlog. The issues from A and B are shown in the query result, though I can see only the original issues from A and nothing from B in the Backlog. Project Browse permissions in B are set to application-access and even to Anyone. So I don't get why issues from B are not shown in A's backlog.

Best regards

Accepted answers

Axel von Arnim

Thanks to both of you, @[deleted] and @Andy Heinzer!

The permission scheme for project B was ok, since all was accessible to Jira application level. But the problem was that statuses and workflows were different in both projects.

The fix was to use A's workflow in B in order to share the statuses. Thus A's backlog would show A and B's issues base on the same statuses.

Also sharing the workflow was not enough to be able to transition B's issues. I had to replicate the project roles in B ("People" settings) since I had conditions based on project roles in the workflow.

This was quite a fight, but worked out finally.

Cheers!

All comments

unknown

Hi @Axel von Arnim,

Has a sub-filter been applied to the board? You can find out by navigating to Board Settings > General > (on that page) Kanban Board sub filter?

Thanks

Axel von Arnim

Actually yes: "fixVersion in unreleasedVersions() OR fixVersion is EMPTY"

But removing it does not help.

I also changed my project filter to display only project B:
project in (B) ORDER BY Rank ASC

and again I get issues in the search, but void in in the backlog or board...

unknown

Hi @Axel von Arnim,

Could you provide a screenshot of your board configuration as well as the JQL query if possible?

Thanks

Andy Heinzer

You need more than just the Browse permission in project B to be able to see and manage issues on an agile board (scrum/kanban). You also need to have the Manage sprints, Edit issues, Transition issues, and Schedule issues permissions in project B to be able to see them on the board and then be able to drag them into an active work-board or sprint. I'd recommend reviewing the permission scheme for project B and check these permissions against the documentation in Managing project permissions.

Axel von Arnim

Thanks to both of you, @[deleted] and @Andy Heinzer!

The permission scheme for project B was ok, since all was accessible to Jira application level. But the problem was that statuses and workflows were different in both projects.

The fix was to use A's workflow in B in order to share the statuses. Thus A's backlog would show A and B's issues base on the same statuses.

This was quite a fight, but worked out finally.

Cheers!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud