We can't create subtask from sprint backlog view (board)

Jordi Ariño July 9, 2024

Hello, goord morning

When we try to create a new subtask from sprint backlog view (board) in a Scrum project (team-managed project), we receive the following error message.

We have the board group by subtaks and we are using "Create issue" bottom link at kanban columns. We have used without problems, but suddenly this error appears. In the popup that appears sprint value is disabled and automatically selected by the tool (with same sprint that user story); the difference when we create subtask from inside user story is that sprint value is unassigned.

Have something changes? For us is very comfortable to create subtasks directly from board.

Issue '' is a subtask and subtasks cannot be associated to a sprint. It's associated to the same sprint as its parent.

3 answers

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 9, 2024

Hello @Jordi Ariño 

Welcome to the Atlassian community.

I have not been able to recreate your issue.

In a Team Managed Software project with a Scrum board, looking at the Board/Active Sprints view where the Group By option is set to Subtask, I am able to click the +Create Issue option at the bottom of a column within a swimlane and create a new subtask in the issue denoted for that swimlane.

Can you perhaps provide a video or screen images to illustrate the steps you are executing? Perhaps I'm not following the same path as you.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 9, 2024

Thank you for the additional information. With that I was able to replicate your scenario and get the same error message you get.

The fix is to remove the Sprint field from the Issue Layout for the Subtask issue type. Then you will be able to save the issue without error.

Jordi Ariño July 10, 2024

Thanks.

This fix solves the problem.

Thank you

Like Trudy Claspill likes this
0 votes
Sebastien November 21, 2024

I have exactly the same problem.

This happen so many time using the Plan views. We have to created not in the plan to make it work.  It's a bug or a bad restriction. Don't know how to solve it.

 

 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 21, 2024

Hello @Sebastien 

Did the accepted answer on this Question solve your issue?

If not then I suggest that you start a new Question for a discussion of your scenario, since your scenario is different ( creating from a Plan vs a Scrum board).

Sebastien November 22, 2024

Well it's a solution but we cannot use it for now because we use (and love to use) Sprint field at Subtask level on all our projects.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 22, 2024

Subtasks cannot be in a different sprint from their parents.

What purpose is served by using the Sprint field in the subtasks?

Like Jack Brickey likes this
0 votes
Jordi Ariño July 9, 2024

Hello,

Thanks for your response. Here is a screenshot of the error message after we click on 'Create Issue' option, write the summary of the task, popup is open and we click on create.

capture.png

Also a small animated gif simulatin the scenario.

demo.gif

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events