Error after creating a new issue "Your issue OOO-3 has been created but not visible on board"

[Gabriel Lai]

Hi guys,

I had tried to look for similar issues like mine. Tried a few ways in setting as well as filter but still unable to get my issue appearing on the board. Currently there is no issue appearing on any of my boards.

- The issues are not more than 2 weeks old.

- The filter is all issues.

What are the other possible reasons?

This first screen shot shows the issues created appearing under "Resolved" board.

The second second shot shows the error after creating the third issue.

Thanks in advance for any help!

Best Regards,

Gabriel

[Max Foerster - K15t · Accepted solution]

Hi @Gabriel Lai ,

could you please tell us the exact JQL board filter you used for this board?

Best, Max

[Gabriel Lai]

Hi @Max Foerster - K15t , I am using the default.

project = OOO ORDER BY Rank ASC

[Max Foerster - K15t]

And that is a Scrum board, correct? And if you add the issue to a sprint and start the sprint, will it be visible on the board? Because Scrum boards only show issues in active sprints.

Best, Max

[Gabriel Lai]

no Max, that's a Kanban board.

[Max Foerster - K15t]

Okay, good to know! The column mapping looks different to me in my instance with the Kanban backlog. Could you please check your Kanban board sub-filter?

[Gabriel Lai]

I am not sure if I am grabbing the right info?

[Max Foerster - K15t]

You can find the Kanban sub-filter at the bottom in the General tab. :)

[Gabriel Lai]

Oh thanks. Managed to grab the value from there.

fixVersion in unreleasedVersions() OR fixVersion is EMPTY

[Max Foerster - K15t]

Okay, this is tricky. We must be missing something. You wrote, "Currently there is no issue appearing on any of my boards." 

So we check the board filter - seems okay. The sub-filter seems fine (default) as well.

Did you map all statuses in your workflow? Is there anything special about OOO-3 that distinguishes it from the other issues?

[Gabriel Lai]

Yes, I did for the statuses to workflow. There is nothing special about the latest issues. The other issues, OOO-1 and OOO-2 encountered the same error as well. I just created the third issue to capture that error.

[Max Foerster - K15t]

And what are the two issues in the Resolved column? You should be able to see them I guess. 

[Gabriel Lai]

Nope. The 2 issues are OOO-1 and OOO-2 which are in the resolved columns but not appearing on the resolved board. 

[Max Foerster - K15t]

Hey Gabriel,

I have to get back to you later. But are you really on a Jira free plan? 

[Gabriel Lai]

Thanks for your help Max. Yup i am on a free plan but I used to be on a paid plan before.

[Max Foerster - K15t]

Hey Gabriel,

I guess you're still struggling with the issue or were you able to find a solution? I'm still very curious about the reason for it. Would you like to have a Zoom call later today to look at the configuration of your board? 😁 What timezone are you in? 

Because if your board filter is correct, access to the issues is given, all statuses are mapped to columns, the workflow itself could be interesting to see.

[Gabriel Lai]

Hey Max,

Thanks for checking. Yeah, I have tried to do a few stuffs on the workflow after reading some of the articles posted here but still the problem exists. 

Thanks for offering your help. I appreciate it. I am in GMT+8 what about you?

[Max Foerster - K15t]

I'm on GMT+2, do you use LinkedIn, let's connect there for being able to chat and find a date. :) https://www.linkedin.com/in/maxfoerster/

[Max Foerster - K15t]

A little update for you all after @Gabriel Lai  and I have been going through all the bits and pieces of the affected project and the board for like 40 minutes. Every setting, filter shares, permissions, we did changes of schemes yadda yadda. 😁

The culprit was the default board sub-filter:

fixVersion in unreleasedVersions() OR fixVersion is EMPTY

Because it did not show any issue with an empty fix version field from that project in the issue navigator. But the query works well for other projects. So it is pretty weird!

So we came to the conclusion that this is a bug we were experiencing. 

[Gabriel Lai]

Thanks for your help once again Max!