How to write two different issues in Two different Kanban Boards in one project?
Right now, When I have created two different Kanban boards (in 1 project), and
I describe the issue in one board, it shows automatically in the second board as well.
I want to have written separated issues in first Kanban board and separated issues in second Kanban board.
How to do it?
Hi Guys, I think i over-complicated it.
I have 3 guys in one team:
1 guy working for project A
1 guy working for project B
1 guy working for project C
and I want to have that each of them has a separated Kanbanboard and can create separated issue on own Kanban board.
Righ now I have 3 separated Kanban board, but issue are common ( the same issues on every bord) and want issues from project A on first Kanbanboard. Issues from project B on second Kanbanboard and issues
from project C on a third Kanban baord.
I hope it looks clearer now. Can you please help me with it?
Back to my and Steven's answer. Kanbanboard 1 filter includes AND labels = xxx and Kanbanboard 2 filter includes AND labels = yyy. Then each issue that you want to show on Kanbanboard 1, set it's label to xxx and each issue that you want to show on Kanbanboard 2, set it's label to yyy.
The same method can be used with Component if you prefer.
Replace xxx and yyy with meaningful names.
I hope this helps
Thanks, we are moving forward.
I have labelled issues differently but where can I setup these
board filters. I have viewed board settings but I could not find filters to set up. There is : qucik filters, but how to place there
filters that filter based on labels.? Any ideas.
Marcin, if you share the filters from your boards I'm sure we can assist. Basically if you have three projects and three guys and you want them to have their own kanban the filter should simply be Project = A, Project = B, Project = C. Of course you can add more details to get precisely what you want. If we see the current filter we can point out why you are getting the undesirable results.
Hi Guys, thanks a lot for help. We did it. Labels solved my problems.
Now I can differentiate it, so I can have 3 different kanban boards and each kanban bord has own issues ( thanks to label filter).
Thanks a lot for your support and for the great teamwork.
I really appreciate it.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs