Issues are not displayed on the board in a default settings project

[Willian Stigliani]

I was testing with custom workflows and having a problem with the items not being displayed on the board (the old "Your issue has been created, but currently isn't visible"). As I couldn't find a way to solve it, I decided to create a new Kanban project, with the default settings and test the creation of an issue. To my surprise, he doesn't appear on the board either!

And this is repeating again and again, for any project created. That is, I create a new project, Scrum or Kanban, with default settings, and yet, when creating a new issue (without changing any project or board settings), it is not displayed on the board.

This made Jira practically useless for me. And I have no idea how to solve it anymore. Has anyone faced something similar? Any suggestion?

[Willian Stigliani · Accepted solution]

Hey guys,

First of all, thank you very much for the replies. All of you were very thoughtful!

After exploring these alternatives (some I had even tried before), I decided to do some more tests, and I ended up finding the solution to the problem, which I'm sharing below so it can help other people.

What I found is that the Kanban board subfilter was preventing items from showing on the board. Removing it made the items reappear on the board.

What I find strange is that this filter is created by default in any new project (I've tested it several times, creating several projects), and I haven't made any changes to it. This causes the problem to happen right away.

I just don't know if this is something that only happens to me, or if it could be a tool bug.

Once again, thanks to all for the help!

[Ruby]

Thank you so much. I had the exact same issue and this has been driving me crazy! 

I've been deleting unneeded fields like Version so I guess that filter couldn't find anything.

[RISHAV KUMAR GUPTA]

Hi @Willian Stigliani  As per your query you might be getting the view like this .

this can be resolved by configuring (board settings::column ):

and map the unmapped statuses to the columns . I hope this might work .

Thanks ,

Rishav.

[Tom Lister]

Hi @Willian Stigliani 

Check your board columns show the status of the new issue.

https://confluence.atlassian.com/jirakb/how-to-resolve-the-error-your-issue-has-been-created-but-currently-isn-t-visible-779160922.html

Is it in the backlog?

Does the permission scheme give you access to the ticket if you open it directly?

[Stefan Salzl]

Hi @Willian Stigliani 

Did you see any issues before? 

As you mentioned in your very first sentence you are using a custom workflow:

If the standard/former used workflows are changed the new statuses need to be mapped to the columns of the board. Any status that is "unmapped" cannot be shown.

Please go to board settings, menu item "Columns" and check if there are any status in the far right column named "unmapped statuses"

If this doesn´t solve the problem please add screenshots of the above mentioned page and your custom workflow.

Best
Stefan