It means your board configuration is not including the issue for some reason. The board filter is often the culprit (e.g. the board says "all bugs and stories in project X" and you create a request-type in project X), but check also the columns (do you have the "new" or "open" status in a column?) and the quick filters in case you've hidden it with them. Also, if it's a sub-task and you're in planning, they won't show.
You have a big pile of issues in JIRA. Your board is a view of the pile, and it says "only show issues that match these criteria (e.g. it's written on a green note)". There are some further "quick" filters that enable you to toggle more criteria (e.g. only show me notes written in block capitals)
You are creating issues that do not match the criteria, so it's not visible on the board after you create it.
Could you tell us what the issue type is for the new issue (and whether it's a sub-task type), where you are doing this creation and what the board filter is (under Board config)
Thanks for getting back to me. What I did is very basic and was just to try out JIRA. I created a scrum software project called "Test." Then, in the backlog, I created 8 issues titled 1,2,3,4,5,6,7,8. They were all created the exact same way, by typing the number into the "create issue" field and then hitting enter, so I'm not sure how the criteria could be varying. Only 6 of them showed up, the other 2 were hidden.
The issues are all "story" type, none are sub tasks, the creation is being done in the backlog and the board filter under config is "Filter for Test Board."
Ok, great, that rules out some stuff. Next question is what is the definition of the "filter for test board"? Is it really simple, like "project = test"? Do you see all 8 issues if you go to menu -> issues -> search, click "advanced" and paste the query into the search defintion?
And was the "create issue field" the one on the backlog screen?
Ok, that implies you are somehow creating issues that are completely blocked from your sight.
When you run that query, what issue numbers come out? Let's say you created them with summaries as you said, 1, 2, 3, 4, 5, 6, 7, 8. Are the issue keys TEST-1, TEST-2, <missing 3>, TEST-4? Or sequential?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs