In the board the option to create an issue only shows story type instead of all available Work types

[sergio_gonzalez]

I checked filters, columns, status, workflow all looks good, I have 2 other boards and those show all available Work types.

[James Gamble]

Hola Sergio,

I’d check this in two places.

First, I’d confirm what Marc mentioned: make sure the space actually has more than Story in its work type scheme. Go to Jira settings, then Work items, then Work type schemes, and compare the scheme used by this space against the schemes used by the two boards that work. If this space only has Story in its scheme, the board won’t offer the other work types from the inline create option.

Atlassian’s work type documentation is here: https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/

If the work type scheme looks correct, then I’d look at the workflow setup next. Jason may be onto something with the different workflows point. There have been Community reports of the board creating options that behaved differently when work types in the same project used different workflows. It isn’t the same, but it’s close enough that I’d compare the workflow scheme in this board’s space with the boards that show all work types.

Related Community thread: https://community.atlassian.com/forums/Jira-questions/Create-issue-button-only-in-one-column/qaq-p/1831670

I’d test it this way: create one issue of each missing work type from the normal global Create button first. If Story, Task, Bug, and the other work types can all be created there, then permissions and the work type scheme are probably fine, and the problem is specific to the board’s inline create behavior.

After that, compare the board filter and workflow mapping with one of the working boards. Make sure the board filter doesn’t limit the issue type, for example, with something like issuetype = Story, and make sure the statuses for the missing work types are mapped to board columns.

There’s also an Atlassian Cloud KB about the board Create button being unavailable when board columns/statuses don’t line up correctly, so I’d check the column/status mapping too: https://support.atlassian.com/jira/kb/the-create-issue-button-is-greyed-out-when-attempting-to-create-from-the-board-view/

So my order would be: compare the work type scheme, test the normal Create button, check whether the board filter limits work types, then compare workflows and board column mappings against the boards that work.

Thanks,

James

[sergio_gonzalez]

Yes, I believe I've done the do diligence on this, I also found that in the problem boards, when I switch to "List" or "all work" views/tabs Im able to select all the other Work types to create Work items, and I also recognize that for both of the views the default Work type is different, like for one is task and the other is test. is this behavior wierd or is it me.

[James Gamble]

Hola Sergio,

That does sound a little weird, but I don’t think it’s just you.

Since you can create the other work types from List and All work, the work type scheme and basic create permissions are probably fine. That points more toward the board’s inline create behavior.

The part I’d focus on is the workflow/status mapping. The board creates an option to create the new work item in a specific board column. If the missing work types use different workflows, and their starting status isn’t mapped cleanly to the column where you’re trying to create the item, Jira may only show the work types it can create in that board context.

I found a related Community answer where the same general issue happened because the issue type didn’t have a status mapped to the first board column: https://community.atlassian.com/forums/Jira-questions/All-issue-types-aren-t-showing-when-creating-in-backlog/qaq-p/2230425

I’d compare the working board and the problem board side by side, especially the first column. Check which statuses are mapped there, then check the starting status for Story, Task, Bug, Test, and the other work types. If the work type starts in a status that isn’t mapped to the column, that may explain why it doesn’t show in the inline create menu.

Your test with another board/filter also helps, because it makes the filter less likely to be the cause. I’d next test one missing work type by temporarily giving it the same workflow and starting status as the work type that does appear. If it starts showing in the board create menu after that, then the issue is almost certainly workflow/status mapping rather than permissions or the work type scheme.

Thanks,

James

[Jason Krewson]

This is pretty interesting, from my understanding you should see all work item types when you click create there.

In testing I found that one project I see all, another project I only see bug, but in the project I only see the bug work item type the space does have access to create story, task, bug, and defect.

When looking into this I found that it's possibly a known issue when different work items share different workflows.

Not sure if this is the answer but I hope it helps, I will keep an eye on this post as well to see what others say. 

Here is another post I found that was good, I know its not this exact issue but its related to the create button in columns and testing someone did: https://community.atlassian.com/forums/Jira-questions/Create-issue-button-only-in-one-column/qaq-p/1831670 

[sergio_gonzalez]

Yes most of the Work types have different Worflows, most of them are in one, I have a different Workflow for Task, Story and Bug one for each, but after analysing I can't find any rules or settings that might be limiting the work types I can use to create tickets in that specific option.

[Marc -Devoteam-]

Hi @sergio_gonzalez 

Are there more issue types listed in the issue type scheme, used by the space then Story?

[sergio_gonzalez]

Yes, here is an example of another board in the same project.

[sergio_gonzalez]

I tested creating another board using a different filter and is the same result.