I have one Project set up. In this one project, I have two boards (one board for each team). One team does development work and will use a scrum board and one team does maintenance and that will use a Kanban board. How do I make issues for the maintenance team visible on the Kanban board? Right now, when I create an issue, it shows up in the backlog of scrum board for the development team.
If your issues show up in the issue navigator when using the same filter there are three things that could potentially hide them in the board:
If that is the case and you don't work with the release functionality in JIRA you can leave the sub-filter empty. You can read more about this here: https://confluence.atlassian.com/x/jYRPFw
Yes, do not give it a version when you create it.
You might have an admin who has set the field mandatory though - you will need to get that removed if you can't leave the field blank on creation. Also, if it's getting a version without you setting one, that would be an automation or script your Admins would need to remove or reconfigure.
It is all about the filters you apply to the two boards.
E.g. if the teams are using different issue types you can create the filters to catch the correct issue types for each board.
If they are using the same issue type you will need some other way to distinguish the tickets. maybe a custom field showing if it is a maintenance ticket or a development ticket.
This page describes how filters work: https://confluence.atlassian.com/display/JIRA/Using+FiltersThe filter used by each board is found under the board config.
Also check out this page: https://confluence.atlassian.com/display/AGILE/Configuring+a+BoardIt describes well how to configure your boards.
Hi Ted! Thanks! I checked the case. It matches. Unfortunately, my issues are still hidden on my kanban board. I can see that I have two issues when I configure my board, but when I view my board the issues are hidden. Do you have any other suggestions of what I can check to see why my issues are hidden?
Ted I really appreciate your help. When I run it from the filter page, the filter shows up. My core problem is that I have one project and I need two different boards to represent my dev team and the other board will be for my operations team. My dev team has a scrum board and my operations team has a kanban board. When I add an issue (task) that is intended for my kanban board it shows up on the scrum board once the sprint is active however it stays hidden on the kanban board. If you could offer any suggestions on the proper way to get these two boards set up, that would be a HUGE help. I just want to start over and recreate my boards. Any thoughts?
Hi Bridgette. I have the same set up on my boards, and they work with no issues. Without being able to see the exact set up, I don't know what it wrong, since the Kanban filter returns issues, and they statuses are mapped to columns. I would suggest filing a support ticket and having one of Atlassian's support engineers take a look, they will be able to solve the issue quickly.
Here's a nasty end-case I've recently solved:
I have a Kanban board attached to a filter whose query includes specific labels.
I've set my board's swimlanes to be based on Epic, and wound up with nothing but the default "Issues without epics" swimlane.
As it had turned out, issues having suitable labels didn't show in case their associated Epics didn't have the labels as well. I added the proper label to Epics - expected issues started showing on the board.
I have nothing to add in regards, besides the fact that I find the way you handle submissions unprofessional and inappropriate.
A pro would have asked me for filter details, JIRA version, etc. - and, in the very least, a description of how it does work (response to "that's simply not how it works"); This isn't the case here, just a shallow "you are wrong". Quite disappointed.
I sure hope things improve around here, or this community would be rendered scarce.
I'm not "handling a submission", I'm an end user pointing out that a new answer on an old question is wrong.
I apologise for my initial response seeming terse, it was intended to be short and simple, but I did not make the effort to explain that better. I wanted to quickly and cleanly make the point that what you had written was based on a misunderstanding, and was the wrong answer.
There was no need to follow it up with any questions, because I didn't need any more information to understand that you did not understand how it works. I should also have explicitly pointed out that the previous answers here explain how it works correctly, and that you should have read them, rather than expect me to repeat the explanation.
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
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