Not able to see the user stories and tasks for a created board of type Sprint?

[Arturo Jimenez]

Hi,

We have a Jira project where we have different projects handled by a team, and I wanted to create a board of type Sprint using filters and the labels for my project as I was told to not create a new project, 

I assigned a label for my project that I added to all the epics and user stories, but when I go to my board only the Epics are displayed.

What can I do?

Filter 

View of my board

This is my board and I only see the epics and cannot plan a sprint 

You see that it reads that there are more items, but even when clicking on clear all filters nothing happens. 

Thank you 

[Trudy Claspill]

Hello @Arturo Jimenez 

Welcome to the community.

Is the source project a Company Managed project or a Team Managed project? It should say at the bottom of the navigation pane on the left.

Based on the screen image of the board that you provided I am guessing that the source project is a Team Managed project.

If that is the case, be advised that the boards you can create manually based on a saved filter are designed to work with the architecture of Company Managed projects, not Team Managed projects. The architecture of the two types of projects is different in how they track the relationship between Epics and their child issues, and between issues and their child sub-tasks. Because of this, how the data is displayed in a manually created board is different.

Once you can confirm that type of project, I can provide additional information.

[Arturo Jimenez]

Hi @Trudy Claspill 

Yhank you for your quick response and detailed responses. Sure, the project reads  "You're in a team-managed project".

Looking forward to hearing from you :) 

[Trudy Claspill]

For Team Managed projects one board is created by default when the project is created. That board functions based on the architecture of a Team Managed project.

Currently the way Team Managed projects track the parent Epic of an issues is to record the Epic issue key in the Parent field of the child issue. In Team Managed projects the same field is used in Sub-task issues to record the issue key for the sub-task's parent issue.

In Company Managed projects the Parent field is used only in Sub-task type issues to records the issue key for their parent issue. To record the issue key for a parent Epic, the issue key is stored in the Epic Link field of the child issue.

When you use a manually created board, it functions based on the architecture of a Company Managed projects. Considering that your manually created board is referencing issues in a Team Managed project, it is considering the child issues of the Epic to be similar to Sub-tasks. So, it will not show the child issues in the Backlog screen just as it would not generally show Sub-tasks in the backlog screen. Issues that have no parent Epic will show up in the Backlog screen.

You will not be able to have multiple boards created for your Team Managed project where those boards all function "correctly" and like the board that was automatically created for your Team Managed project. There is a change request for that here:

https://jira.atlassian.com/browse/JSWCLOUD-17371

Your options are

1. use multiple Jira projects for the "projects" on which the team works, or

2. create a Company Managed project and move all your Team Managed issues to that Company Managed project, and then you can create additional boards as you desire. However there are limitations to moving issues between Company and Team Managed projects (see this article), and also then the customizations for the project can be managed only by Jira Administrators rather than project administrators.