Issue Created in All Boards Community Edition

Hi,
I’m running a docker community edition of Gitlab and I have a project in which I have created multiple boards,
If I add an issue in one board it is reflecting in all the boards.
Why this is happening? IF the application allows me to create a board then the scope of the issue should be within the board.

can someone help me on this.
Thanks
Aswin

So, the boards aren’t really scoped like that. All the issues in the issues list can be on any or all boards, and if you want to limit the boards to a subset of your issues, you would do that by defining columns on the boards (with the Add list button) with a particular label, or combination of labels.

Does that help?

1 Like

Hi Snim2,
I created a list/column called “InProgess” in Default Development Board and added an issue to the Inprogress.
I created another board called Release_X.X.X. Now In the Release board, I see the issue from the development board which shouldn’t be part of Release_X.X.X but to be part of the development board.

See the attached image.

Thanks
Aswin

The Open issues column contains all the open issues, regardless of their labels. If TestIssue has a label, and that label has a column associated with it, then TestIssue will appear in that column, otherwise it will appear in the Open column.

I don’t believe that’s configurable, but if you click the > next to Open you can collapse the column.

1 Like

Hi Snim2,

The TestIssue is created in the development board(see first image) and seeing that in OpenIssue of the board is fine and from Open I have moved it do InProgress. However, “Release_X.X>X” Board(see second image). I haven’t created any issue at all, but it is showing the issue from “Development Board” with a label “in_progress”.
See board with Red.

If you actually see the gitlab.com site hosting the GitLab source, each issue is scoped within the board.

I understand what you’re trying to do, but GitLab has no way to scope an issue and restrict it to a board, the only thing you can do is to filter columns on labels. So, an open issue that does not appear in another column will always appear in Open.

Then how come this site is doing it

or is my understanding is wrong.

I see issues are scoped within the boards.

Ah! I did not know about this, but it seems to be a premium feature.

1 Like

No problem. Even I was thinking it might be available in premium. But it defeats the whole point of allowing to create multiple boards but not scoping the issue within a board.

I still find it useful. Usually I want one Kanban style board, and then it’s sometimes useful to have a board for a particular set of labels relating to a feature or release. I don’t mind too much that the Open column is massive, but YMMV of course!

1 Like