Next-gen project: How to give existing task a story as a parent?

[vibonacci]

Hi,

We have some existing tasks that are under 'issues without subtask' in our Board. We want these tasks be subtasks of an existing story. How would we give these tasks a new parent story?

Below a screenshot to illustrate the issue.

What we've tried:

1. Click the issue and click: Choose Parent. This does not work as it does not show any results as it expects the parent of a Task to be an Epic.
2. Click the issue and click 'Task' in the top left in an attempt to convert the Task to a Subtask. It only allows issue to be changed to Epic or Story even though Subtask is clearly a defined issue type for our project
3. Click the issue and click Move. Here the UI gives the impression that you can actually change the Task to a Subtask and choose a parent. However, the so called 'bulk' change throws a generic error.

How do we achieve this without adding a new subtask to an existing Story? Thanks in advance.

[Andy Heinzer · Accepted solution]

Hi Igor,

I understand you are wanting to convert an existing issue in a next gen project into a subtask issue type.   Subtasks have only very recently come to next gen projects, prior to this new feature roll out the issue type was not available in these project types.

That said, there does not appear to be any existing way to convert a current issue into a subtask within an next gen project.  You can certainly create new issues of type subtask and IF you were using a classic project type, you could convert stories or tasks into a subtask of another issue. But as of today, this feature does not exist for next gen projects.  But I can certainly understand why you would want to be able to do this, so I created a feature request for this in JSWCLOUD-17980.

I also have never seen the ability to convert an issue into a subtask by drag-n-drop on a board, but I did find another feature request for that in JSWCLOUD-17767.

Complicating your reported problem here, is the term 'add parent'.  In this case it's not setting the parent to be a story, but rather in this specific example, your story/task issue type can only be added to an existing epic.  Which is still a parent issue to that story.  This same kind of parent/child relation exists for both epic/story and again for story/subtask. 

But since next gen projects have not yet had a means to convert existing issues between subtask and story, technically this is not a bug.  Sorry this probably is not the answer you were hoping for here, but subtasks in next gen projects are still a relatively new feature, and perhaps the current implementation will change over time.

I would recommend watching these issues and clicking the 'this affects my team' on those tickets.  This helps our development teams to prioritize new features.

Regards,

Andy

[Igor Willems]

Thank you for the answer.

I would agree with the statement that this is not a bug where it not for the following 'Move' screen. Here it clearly implies to me personally that this should be possible.

[Christine Armiyants]

@vibonacci  this works just fine with the "MOVE" feature.  Just change task type into Subtask and then define the Story. 

[Tarun Sapra]

Hello @vibonacci 

You have described the correct process, but it seems when we move the issue from "Task" type to "sub-task" type we are getting an error. Seems like a Jira cloud bug, I am also able to replicate it. I will share this post with someone from Atlassian.

[vibonacci]

All right, thank you. Keep me updated if possible :)

[Karthik N]

Is this resolved? 

[Christine Armiyants]

@Karthik N   this works just fine with the "MOVE" feature.  Just change task type into Subtask and then define the Story. 

[Günter Zöchbauer]

The "New Issue Type" dropdown does not offer "Subtask" as option

[Günter Zöchbauer]

"Link" works for me (instead of "Move")

[Adrian von Gegerfelt]

Still can't choose "Sub task" in the Move dialog. Link doesn't have anything to do with story or subtask.