Sub-Tasks can't be pushed in to Current Sprint

[Mehedi Hassan]

Main task is moveable in to the Current Sprint but it's not allowing to push Sub-Task of that Main task in to the Current Sprint. It always remains in the Backlog.

Does anyone know the reason?

[Trudy Claspill]

Hello @Mehedi Hassan 

Welcome to the Atlassian community.

Normally a subtask should move with its parent issue into and out of sprints. If you are seeing something different, we need more information to try to help you debug that.

Can you please provide a screen image of what you are seeing?

After moving the parent issue to the sprint have you refreshed your screen?

What type of project are you using? You can get that information from the Type column on the View All Projects page under the Projects menu.

[Mehedi Hassan]

Hello @Trudy Claspill 

Thanks for your response.

In a few Projects, ST's are not behaving as expected.

It is a company-managed project. Main task & ST are visible in Backlog. While I am trying to send both in the Current Sprint, Main task is being added without ST. And they are visible in Current Sprint & Backlog respectively. While dragging by selecting both, both are being visible in the Current Sprint but after refreshing, I see that the Main task is in the Current Sprint and ST is still in Backlog.

I am sharing a few pictures for a better understanding...

[Trudy Claspill]

Thank you for those images. 

What is the project type you're using? You can get that information from the View All Projects page under the Projects menu.

What browser application are you using? Have you tried this in another browser application?

Do other users have the same experience?

[Mehedi Hassan]

team-managed projects are giving this issue.

Normally I use Chrome browser. Just now I tried on Microsoft edge and the ST is not visible anywhere, I can only see the Main Task.

Everyone in my team having the same issue, we are all using Google Chrome as browser.

[Mehedi Hassan]

Hello @Trudy Claspill 
Is there any update for me?

[Trudy Claspill]

I have not been able to recreate your issue.

I recommend that you ask your Jira Administrator to open a support case directly with Atlassian about this.

It would be great if you would report back here what you learn.