child issues not visible on agile sprint board

[Abhinav Singh]

Let me discuss the prob with u.

I faced this prob in the regular standup I take on JIRA .

Suppose I have a parent user story A, it has two child issues B and C.

A is assigned to ram.

Now ram has assigned B to Shyam and C to Ghanshyam. 

Now when I click on the Shyam icon to see all the tickets, B is not visible (as B is a child issue ).

This becomes really cumbersome for everyone during the standup

[Niranjan]

Hi @Abhinav Singh ,

Board is just a placeholder of issues returned by your board's JQL filter. Could you check your board's filter query? Just run the query in the issue search and check if it returns the child issues.

[Abhinav Singh]

how to check it? 

[Abhinav Singh]

@Niranjan No it does not return the child issues. How can I make it return child issues, basically everything (tasks, user stories, child issues, and bugs ) 

[Niranjan]

@Abhinav Singh What is your board's filter query? You can check it by

1. Navigating to your team-managed Jira Software project.
2. From your project’s sidebar, select Board.
3. In the top, far right select More (···) > Configure board.
4. General  - you will see the query

[Abhinav Singh]

@Niranjan I cannot follow ur 4th point. see the attached image. after following top 3 steps I am here 

[Niranjan]

@Abhinav Singh ,

https://support.atlassian.com/jira-software-cloud/docs/configure-filters/

Can you click on Boards above the column and statuses?

[Abhinav Singh]

no

[Abhinav Singh]

I am using a team-managed project for my product. Does that make a difference 

[Abhinav Singh]

@Niranjan Why I am not getting general and filter (your 4th point) in team-managed software? 

[Niranjan]

Hi @Abhinav Singh - I got to see this open feature request - https://jira.atlassian.com/browse/JSWCLOUD-17444

NextGen projects does not have all features of classic projects and we do not have options to customise the board/change the filter query. Next-Gen is customized for teams looking for a simpler solution. They may not be suited for typical classic projects users.

[Abhinav Singh]

@Niranjan why cannot I see general and filter in team-managed software in Jira? 

I CANNOT see what u are seeing in the attached image in a team managed software 

why so? 

[Niranjan]

@Abhinav Singh - Team Managed project is a different proeject standard template and does not have what a classic or company managed project has. They use only standard filters.

https://support.atlassian.com/jira-software-cloud/docs/what-are-team-managed-and-company-managed-projects/

[Abhinav Singh]

@Niranjan Can I change from the team-managed software to company-managed software? Can everything remain the same (all my tickets , basically all record of team managed software ) 

[Niranjan]

@Abhinav Singh You can migrate the projects from one type to another type.

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

Things to keep in mind if you migrate from team-managed to company-managed:

1. Team-managed projects and company-managed projects are technically quite different. Here's a few things to consider when you migrate from a team-managed software project to a company-managed software project:
2. Board statuses: If you customized your team-managed board, you'll need to set up the same statuses in your company-managed project's workflow. Only Jira admins can create and modify statuses and workflows. Learn more.
3. Custom fields: If you customized the fields that appear on your team-managed issue types, you'll need to have a Jira admin recreate these fields in your new company-managed project's screen schemes and field configuration schemes as the data stored in these fields will be lost.
4. Issue types: If you added your own issue types to your team-managed project, you'll need to have a Jira admin recreate these using an issue type scheme that they associate to your new company-managed project. Learn more.
5. Project access: Access to company-managed projects is controlled by a permissions scheme. Only your Jira admin can update your company-managed project's permission scheme. Learn more.
6. Project and issue keys: Project keys are unique and can never be reused in Jira. If you migrate your issues to another project, they will get new keys and the new project must have a different key of its own. If you migrate your issues using the process above, Jira will automatically redirect any links to your old issue keys.
7. Reports: Reports data won't be saved. Even though your issues will be retained, data for your project's Velocity and Burnup reports won't transfer over, and will be lost.
8. Story points estimation: This data will be lost. This is because the custom field that Jira uses to store estimates in company-managed projects (Story points) is different to the custom field used in team-managed projects (Story point estimate).

[Michael Areola]

Thank you