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; } } }

only show one issue type on board - filter?

Mo Omar

Hi Guys,

I'm sure many of you pro's have been asked this question before;

Back drop story:

Current project has your usual issue types: Story, Bug, Epic, Task etc

Recently I've been tasked with creating a new board "Change Management" which is now live. Of course this new board inherits all the existing JIRA ticket/issues types of the current project.

Problem:

I want to be able to show all users of this board only one issue type, which is one that I have specifically created for this board. I have appropriately called it 'Change request'

Hope to hear from you guys, many thanks in advance

Accepted answers

All comments

unknown

Hi @Mo Omar,

You will need to add to the board's JQL filter within the Board Settings:

AND type = "Change Request"

I assume the issue type is called Change Request.

Added a link to documentation on the subject. Select the link in the Board Settings > General > Edit Filter Query

Hope this helps

Mo Omar

@[deleted]Thanks for the quick response I think that has worked in theory, but I've messed up my work flow earlier in the process, and as a result no tickets/issues are actually showing up atm on the board.

Appreciate your help, even though you can't see what my project looks like, is there a way to show you ?

many thanks once more

unknown

Hi @Mo Omar,

why not add a screenshot of your board settings and your board’s filter query?

thanks

Mo Omar

@[deleted]good idea, just noticed the picture icon ...shows you how many times I've used this ... earned my first badge (Merry May badge) :-)

if you can't make any sense of why those "cahnge management" tickets are not showing up not to worry.

in fact its change some of our board issues to a different workflow (Change Management) one. those ticket have some how changed to the new work flow, i must of have clicked on the wrong things.

if you can steer me in the right direction Danny.

Thanks and have a good weekend! Change Issue type.png Filter area.png general board page.png workflow print screen.png

Jack Brickey

@Mo Omar,

what statuses are mapped to your columns for the board? Your board filter looks correct. Could you paste that filter into the advanced search issues screen and see what appears?

Mo Omar

@[deleted]@Jack Brickey Thank you both for your replies, that has worked beautifully!

The board is currently showing all my change management issues...however

The only slight problem I have is that I have logged two 'Change Request" test tickets/issues, as well as these two test tickets a further 15 have been inherited into the "Change Request" issue type. I can't edit these either to their original ticket type... have I accidentally applied the workflow to the entire project rather than isolating it to just the Change Management board I wonder...

I have not selected these tickets to be turned into the Change Request issue type neither at any stage. whats more these 15 tickets are now also showing as Change Request tickets which are Open in all our other boards within our current project.

I've supplied some screen shots where I have highlighted the two test tickets [SNSA-490/SNSA-501] as part of the list of filtered Change Request issue types along with other tickets that have also inherited the issue type which were previously another issue type.

Final plea for help, your responsiveness has not gone without appreciation.

inherited issues.png no edit of issue type available.png

Jack Brickey

If you want to keep the test tickets then you need to use the “move” function since they use a different workflow. You find the move via the ellipses in the upper right when viewing the individual issue. But if you just want them to disappear you can delete them assuming you have delete permissions. Again use ellipses.

Mo Omar

Hi @Jack Brickey thanks for your response.

With the 2 [SNSA-490/SNSA-501] 'test' Change Request tickets the aim was to test out how the new board and issue type behaved. So those will stay on the board, its the other 15 that I will have to do the above for i.e sit down with 'Service Manager' and move those tickets to their original state.

Any idea what has caused that change of issue type? is it a conflict of workflows, not exactly sure how these tickets have inherited the new issue type. I'm just a little scared not knowing whats caused those to change, and that this might happen again with future tickets.

Thanks,

Jack Brickey

@Mo Omar, sorry i misread your response. Can you provide a screen shot of your assigned workflows for this project? Not the workflows themselves but the first screen that shows which workflows are assigned to which issue types.

Mo Omar

Hi @Jack Brickey thanks for getting back to me.

Not entirely sure if I got the right screen shots below, but there seems to be some un-published changes. I'm also not sure if these settings apply to only the "Change Management" board or the entire "SNSA" project.

On the 3rd screen shot it shows that if i do want to publish the new changes it does highlight 17 tickets of the "Change request" issue (2 test tickets) and (15) inherited.

Thanks!

Draft workflow-issue type.png workflow and assigned -issue types.png publish work flows.png issue type scheme.png

Jack Brickey

@Mo Omar, thanks for the screenshots. I started typing up a response and then paused coming back to your original question while considering your recent response and I think you may be confused and possibly off track. I want to step back and secure some fundamental Jira concepts.

First and foremost Boards are simply visual filters that allow you to view what you want to and how you want to for a project or group of issues. These boards are unrelated to workflows except in the fact that they use the Statuses of workflows to map issues to columns.

Your original question was simply to display only one issuetype on the board. To do that it is a simple matter of only including the one issuetype (Change Request) in the board filter, e.g. project = SNSA AND issuetype = "Change Request". That exact filter would achieve you original goal as stated.

So now i'm wondering why you have pulled in the whole workflow change into the discussion? If you want to treat Change Request differently that is find and certainly can be done but it has nothing to do with having a board that displays only that issuetype.

Now I do wonder if you may have some workflow cleanup to do but really that should be a different thread/question. Regardless, if you want a different workflow for Change Request then you want something like what is shown in screenshot #2. If you want all issue types to have a single workflow then you want screenshot #1. Of course you need to ensure the underlying workflow is as you desire and for sure PUBLISH the workflow as nothing changes until that happens.

Mo Omar

@Jack Brickey Thanks for getting back to me once more.

Thanks for setting me straight, I'm still a young Jedi at this JIRA stuff. Everything you have said above makes complete sense. I will look at my workflows in more details and see if I can sure up that side of my knowledge.

Is till not sure how to stop other tickets inheriting the 'Change Request' issue type, I've gone into the history section in couple of those tickets (out of 15) and they revealed the following two screen shots. SNSA 437.png SNSA 231.png