Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,603
Community Members
 
Community Events
176
Community Groups

In Progress issues on sprint board showing under To Do column when subtask is added

When a subtask is added to an issue in Jira, the Sprint board shows the In Progress issue under the To Do column.  I thought maybe this was a browser issue but when Shrink my screen to 50% it still displays under the To Do column. I tried different browsers and it is displaying the same way. The subtasks have been closed and the parent issues are in the status of In Progress so it can't be related to the status of the subtask. You can clearly see the issues are in the status of In Progress so how can I fix this?  Sprint Board displaying issues in wrong column.JPG

 

2 answers

1 vote

The sub-tasks are created in a "to do" status, so they go into the "to do" column.  Note that the parent issue does not have any separator columns, it's just there as a container for the sub-tasks.

Nic,

Thanks for the response.  As I stated above the sub-tasks are in "Closed" status, and the parent issues are in an "In Progress" status, so this does not explain why the "In Progress" issue is in the "To Do" column. Everything was fine until the sub-tasks were added to the issues and this is when the sprint board changed. Sub-tasks should be able to be added to issues without it making the sprint board a mess.  I could understand if the sub-tasks were in an "open" status that this issue (parent) could display in the "To Do" Column even if it was in an "In Progress" status, but this is not the case.  If the sub-task is "closed" and the parent issue is "in progress" then the issue should not display in the "to do" column.

I had the same issue, to resolve this use the Swimpalne option under board settings and set it to None

 

Screenshot 2022-12-07 141924.png

0 votes
Jack Brickey Community Leader Feb 14, 2018

@Beth Starr let's do two things:

  1. open Board settings and look at the Columns screen. What statuses are mapped to which columns? Screenshot?
  2. open each issue and verify that the statuses are indeed as you indicate (closed, in progress, to do). 

I opened the board settings and looked at the column mapping and it is as follows:

To Do ->Backlog

In Progress ->In Progress

On Hold -> On Hold

Review ->Pending Review

Done -> Closed

I opened the issues and the Parent issue is in the status of In Progress and the Sub-task is in the status of Closed.  Everything was correct on the board until sub-tasks were created and the view changed.  The board configuration did not change.

Jack Brickey Community Leader Feb 19, 2018

@Beth Starr, sorry for delay in getting back to you. I lost this in my notifications. Any recent findings during my absence?

@Jack Brickey I have just discovered this whilst investigating a similar issue. I have two tasks with sub-tasks that are simultaneously in the To Do and In Progress columns. I am using Jira 8.5.8 at a client site.

Jack Brickey Community Leader Feb 05, 2021

@Mike Wilkins , i suggest opening a new question for this as I suspect your situation is different and a new question will drive new eyes on your specific issue.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events