Custom issue type not showing

[Simon Jackson]

I have created a custom issue type called spike and linked  to the project i am working on. The issue type does not show on the backlog or the sprint but when you export the data the issue type is in the data 

[Marc - Devoteam]

Hi @Simon Jackson 

What workflow is used for the Spike a separate WF or one already on the project?

Can you create Spike work items on the project?

Check the WF scheme which WF is used for type spike.

Also still check the filter used on the board, as you the Spike work item is in the Work item scheme used on the project, so it's usable on the project.

[Marc - Devoteam]

Hi @Simon Jackson 

So you issue type is in a issue type schema, this issue type schema is used on the porject.

On the workflow scheme, is spike defined to use a specific workflow, or is it using the default workflow, so screenshot.

On the board configuration, in board details a filter is defined that is used for that board, what is the JQL of this filter?

[Howard Nedd]

Hi @Simon Jackson ,

If you've created a custom issue type called "Spike" in Jira and it's not appearing in the backlog or sprint view, but it does show up in exports, there are a few potential reasons to consider.

First thing that I would checkis if the "Spike" issue type is included in the issue type scheme associated with your project. If it’s not included, it won’t show up in the backlog or sprints.

Also make sure to check your board config. Under Columns, check if the "Spike" issue type is mapped to any of the columns. If it’s not mapped, it won’t appear on the board.

Regards

Howard

[Marc - Devoteam]

Hi @Simon Jackson 

Or check the filter of the board, as the backlog is in essence still a board, is the board filter including the work item type Spike?

[Simon Jackson]

The issue type of SPIKE shows on the issue types screen for the project . on the board config I can only map statuses and not ticket types 

[Simon Jackson]

do i need to ad the workflow to the project

[Simon Jackson]

A workflow was not linked to the project. due to it being inactive