Converted subtask to task/story and the ticket is not showing in the Sprint Report
Asked by Sari Kachorovsky:

The ticket was converted from subtask to task/story and the ticket is not showing in the Sprint Report list or the Burndown chart of the active sprint (Jira reports). The ticket does exist in the Active Sprint board. It has the correct team and sprint. Any idea why?


Answers:
author: shiva kumar Gosul
body: Where are those converted Story/Task?

Cross verify the below checklist

Check is there Sprint name for those converted Story/Task.

If those converted Story/Task closed before the Start sprint then it will not display in Active sprint.

Also, check those status of converted Story/Task and verify the same status in Column under Board configuration. Sometimes, unmapped status will hide.

Verify the Board level query in "General" under board configuration.

comments: author: Sari Kachorovsky
body: [@shiva kumar Gosul](/t5/user/viewprofilepage/user-id/4674204) Thanks for your answer, All the details looks correct, correct team , status and active sprint (46), as I said I do see it in the Active sprint board but in the Jira reports they are not shown, One thing I've noticed in the History of the ticket, is that it was removed from S46 in some point, but as you can see the field Sprint is filled with S46, but there is no mention of this in the History. Maybe this explain why it is not in the reports, but how can it be?![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/347492iEEDEFBB45717AEE9/image-size/large?v=v2&px=999 "image.png")


author: shiva kumar Gosul
body: Thanks, [@Sari Kachorovsky](/t5/user/viewprofilepage/user-id/5188527) let us dig more

* Open the converted task/story
* Check if it's still associated with the correct sprint
* If not, add it to the sprint manually
* Try to clear the cache or login into Incognito
* Check are there any filters.
* There is also option called "Issues" check even there


author: Sari Kachorovsky
body: [@shiva kumar Gosul](/t5/user/viewprofilepage/user-id/4674204) - thanks.

* Check if it's still associated with the correct sprint - it is, I can see it in the active board
* Try to clear the cache or login into Incognito - how to do that?
* Check are there any filters. - where?
* There is also option called "Issues" check even there - where exactly? not sure I understand what do you mean.


author: Bill Sheboy
body: Hi [@Sari Kachorovsky](/t5/user/viewprofilepage/user-id/5188527)

Are you using a company-managed or a team-managed project?

Does the converted issue appear on the Sprint Report as removed from the sprint?

If using a company-managed project, this is a known defect: <https://jira.atlassian.com/browse/JSWCLOUD-23342>

Kind regards,  
Bill

comments: author: Sari Kachorovsky
body: Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) Thank you for your answer. Yes I'm in a company-managed project. The issue not appears at all at the sprint report although the sprint field is correct (assign to active sprint). The ticket was converted from subtask before the sprint become active. And wired there is no mention in the History when the ticket added to the active sprint (see my screen shot above)


author: Bill Sheboy
body: Unfortunately, there are cases when changes to issues are not recorded (or displayed) in the issue history. That normally happens for changes made by addons or combined operations by Jira...

In this case, where the subtask "inherits" the parent's Sprint value, when the subtask is converted to an issue (e.g., Task) the Sprint value is set and that does not appear in the history. Yet once the Sprint starts, I do see such converted issues on the Sprint Report.

Please show an image of your Sprint Report, with the noted sprint active, and this specific issue *not displayed on the report*.


author: Sari Kachorovsky
body: [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) the ticket is BP-24704, the active sprint is 46.![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/347815i8CBBDAF196CB210F/image-size/large?v=v2&px=999 "image.png")![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/347816iA8C4C7BA2694ABC3/image-size/large?v=v2&px=999 "image.png")![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/347818i43C591E7AF971C8A/image-size/large?v=v2&px=999 "image.png")


author: Bill Sheboy
body: Based on the prior history you showed...

How was this "subtask" added to an Epic as its parent: BP-22309? Or was that issue later converted from a Story / Task to an Epic.

According to the history, several of those changes were made in under a minute, so something does not add up.


author: Sari Kachorovsky
body: when it was converted to from subtask to a story a parent (epic) was added. I guess that the massive changes to this ticket caused a glitch and something was not caught in the Jira.


author: pinky_reddy
body: Hi [@Sari Kachorovsky](/t5/user/viewprofilepage/user-id/5188527)

Ideally It will appear as a scope change in burndown. Can you check share more details to help further.

comments: author: Sari Kachorovsky
body: [@pinky_reddy](/t5/user/viewprofilepage/user-id/2679900) Thanks for your answer, that is what I expected, to see it in the burndown list but it is not, see my answer above to Shiva.


Tags: cloud

jira-cloud