I've created a story and linked it to an epic. I can open the Epic and see the story as a child issue but it doesn't appear in backlog. It is a company managed Jira software project in case that information is needed.
Hello @Dorothy Callahan
This issues that will display in a board are based on
1. The Filter Query associated with the board. You can find that under Board Settings > General. If the issue is not within the scope of the filter, it will not be displayed.
2. If the board is a Kanban board, then it can also have a Sub-filter. You can find that under Board Settings > General also.
3. Mapping of Statuses to Columns. If the issue is in a Status that is not mapped to a column, the issue will not display in the board/backlog. This if sound under Board Settings > Columns.
4. Quick Filters - an active Quick Filter can hide issues from display that are otherwise within the scope of the board.
There are other factors that can affect the visibility of issues on boards, but we'll start with those. Check each of those. If you are unsure what how to troubleshoot, then post copies of the information for the above and a copy of the issue that is not being displayed.
Thank you! Issue was in status not mapped to column.
Hi @Trudy P ClaspillWhat are the other factors that can affect the visibility of issues on boards?
I did not filter our stories as all issues and issue types from the project are visible in the filter. There is nothing unmapped in the columns, no constraints set, no active quick filter.
Can the screens or fields settings for the issue type prevent a certain issue type (story in this case) to be shown in the backlog and/or timeline?
Hello @N. S.
Welcome to the Atlassian community.
To get the best visibility to the wider community on your question please click the Ask the community (or Ask a question) option at the top of the screen and begin a new post of your own.
Updates to existing posts are seen only by the original author, people who responded, and people who are watching the post, so your question is not getting wide visibility. Also, adding to an old post (this one is over 2 years old) is considered bad forum etiquette. Lastly, this post has an accepted answer already. If the accepted answer doesn't address your issues then you should start a new post.
If this current Question is relevant, you can include a link to it in your new Question.
It looks like you're new here. Sign in or register to get started.
