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

One project, two boards, issue missing from one board

Martyn Pearson

I have a project, project code "NOT" and it has two boards. We use one epic issue type (Epic), four base issue types (Bug, Story, Task and Support) and four sub-task issue types. Support is of note as it uses a different workflow to the other base types.

One board, we call "story view" has the filter such that it hides the subtasks, thus:

project = "NOT" and issuetype in (story, bug, task, Support) ORDER BY Rank ASC

This board works as expected.

The default board has the filter

Project = "NOT" ORDER BY Rank ASC

When viewing this board (which we have swimlane'd), issues of issue type "Support" do not appear on the board or in the backlog.

To make the Support issue type appear correctly in the story view, we mapped the different states to the columns on the board. There is no option to do this in the default board.

Would be grateful for any suggestions as to why issues of Support issue type are not being shown in the default board.

Thanks in advance!

Accepted answers

All comments

Clark Everson

Hi @Martyn Pearson

Welcome to the community!

With the information you shared it should be showing. However boards are really just views into filters. And within the board settings you can filter inside of filters. So without seeing actual screenshots my best guess is you have either a filter enabled on the board or you have a sub filter in your board.

If you are able to share screenshots of the board and the board settings that could be helpful. Otherwise I would read as much documentation on how boards work:

https://support.atlassian.com/jira-software-cloud/docs/what-is-a-jira-software-board/

Additional links are on the right side

Best,

Clark

Nic Brough -Adaptavist-

Given the two filters you have, you should be seeing "Support" issues on both boards and in the backlog.

So assuming you have no quick-filters or a Kanban sub-filter enabled, then I would have to say your board's column mappings are wrong.

Are your issue status ALL mapped into columns on the board?

Martyn Pearson

Hi @Clark Everson ,

Many thanks for your response and for your welcome!

I created a brand new board to see if there was something amiss with the existing one but that exhibits the same problem.

Here are the board settings...

There's no filter applied to the backlog view...

The workflow for the bug / story / task is...

Whereas the workflow for the Support ticket - the issue type not showing - is as follows. This is the read-only Jira (system) workflow.

Thanks again for your help

Nic Brough -Adaptavist-

Are your issue status ALL mapped into columns on the board?

Martyn Pearson

Hi @Nic Brough -Adaptavist- ,

Thanks for your support.

For the working board, yes, but the in the non-working board the statuses in the Support issue type were not available to map to columns, i.e they did not show in the unmapped statuses column.

We have actually resolved this problem by changing the workflow associated with the Support issue type, suggesting it was the workflow rather than the issue type itself that was the root of the problem.

Would the fact that it was the read only, Jira default workflow rather than one we had created have any bearing on how they work?

Thanks again,

Martyn

Nic Brough -Adaptavist-

The workflows are tied to the issue type - if you select and issue type of X in project Y, all issues of that type in that project will follow the workflow Z

It's not directly the workflow that was the problem, it's the project/issue-type associated to the workflow.

The thing that does not make sense to me in this scenario is that you were not offered the status in the workflow to map into the board. If you change an issetype to use a wildly different workflow to the current one, then the board usually puts all the "new" status into the unmapped section so you can drag them in.

I'd be quite interested to see what the (un)mappings offer you if you were to put your old workflow back!

If you've made more than one change and it gets confused, then it actually puts every status in your system into the unmapped column.

The read-only Jira default workflow doesn't matter really. It's just a workflow, like any other. Nowadays, there's a couple of lines of code that stop us deleting it, but it's actually the workflow that was hard-coded into Jira 1, and it's more of a historical record than anything else to my mind (and a bit of an example of good practices, with the transition screens, clearing resolution on re-open, and the status properties)

Martyn Pearson

Hi Nic,

Thanks again for your continued help.

I tried the experiment you suggested, editing the workflow scheme used by the project to make the Support issue type use the original Jira workflow and it behaved exactly like it should!! After completing the workflow change, going to the board settings showed the statuses associated with the Jira workflow in the unmapped column for both of the boards - and adding them to the columns of the boards made them show correctly.

So in the initial state, the statuses associated with the support issue type were not available to add to the columns on one of the boards but changing the workflow and changing it back again made them available.

The board has been in its initial state for a while (over 6 months) and because the Support issue type was never used until product release, the mapping was probably never set up in the first place for the original board. Could this be something akin to an index that needed refreshing to make the states available to add to the board?

Once again, thanks for your help,

Martyn

Clark Everson

Going off what Nic said, the pages you show are only one tab of about 7 for board configuration

There are columns, quick filters etc to configure. Especially if you created a new board some of the statuses may not be mapped

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud