Cannot see issue types in backlog

[BenWade]

Hi everyone,

in one project I can see them all

but in another project I can see only these three

Here's the board filter

Which settings responsible fro making all the issutypes visible?

#jirapremium #jiracloud

[Walter Buggenhout · Accepted solution]

Hi @BenWade

That is perfectly logical. The board filter shows your board is getting issues from 1 single project. The issue types available in a project are defined in the issue type scheme linked to that project. In business language: you will only be able to create the types of issues available in the project you select (in this case, the board is telling you you are working in just the OPEX project).

When you hit the create button at the top of your screen, you will always be forced by Jira to select a project, which is where you will be creating an issue. And then, the list of available issue types in that project will be refreshed. Just mentioning to illustrate the link between project and issue type.

So, in short, you will never be able to create other issue types in the board backlog for the OPEX project unless someone adds additional projects to the board or adds more issue types to the project configuration. I don't expect that to happen, as this seems very intentional and also very much best practice.

Hope this helps! 

[BenWade]

I am sorry, I edited the topic. I want to be able to see them. Can you please check the screenshots I uploaded

[Walter Buggenhout]

I have checked the screenshots, @BenWade. I am not sure what I can add: to that. You share screenshots from 2 different projects / boards. As I explained, projects can be configured to use different sets of issue types. And so there is nothing strange about seeing different sets of issue types in different projects. What is not there cannot be displayed. 

[BenWade]

I have stories and epics in the OPEX project but they are not visible in backlog as opposed to another my project. The projects have an identical issue type scheme

[Walter Buggenhout]

Ok @BenWade, ok - that clarifies the issue a bit more. A couple of things in that case. Let me start with Epics, as they have a specific behaviour.

• If this is a scrum board (and you are using sprints, which I cannot see from your screenshots) - Epics are displayed in a separate panel that you can enable/disable from the Epic filter list at the top of your screen. They will never appear in the backlog of a scrum board amongst your other issues.
• If your board is a kanban board, you only have a backlog if you dragged a workflow status in the kanban backlog column in your board settings. When you do so, you can then specify if you want to see epics as cards on the board or in a separate panel, the same way as I mentioned above for a scrum board.

And then about the stories:

• On a kanban board, a specific status is mapped to the kanban backlog. If your stories are not in that status, they won't appear in the backlog.
• In your board settings, make sure that there is no board sub filter specified that accidentally hides your stories from the board.