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,998
Community Members
 
Community Events
176
Community Groups

How to rapidly switch an issue to a subtask?

I am fairly new to SCRUM concept, and here is how I understood it could/should work:

 

I am currently having my dev team create their issues into Jira directly, whether it's a bug, story, task, etc. Enssentially, whenever they find something, they can create an issue about it in Jira backlog.

 

However, very often, the issue they create will actually be a sub-task of another story or task. And I cannot ask them to create the issue as a sub-task because they don't know if it's a subtask or not (and it makes no sense to ask them to find out through the whole backlog).

 

In my mind, I thought I could just link child issues based on the current backlog issues I had, but from what I understand, you can only link sub-task issues as a child. 

 

Then, if I click on an issue, and hover above its type, it will allow me to change it only to another issue (not a subtask), so I actually have to go through "Move" action to move the issue as a subtask.

 

Can anyone please shed some lights for me here, or any better best practice you would recommend? (For context, we're a startup of 20 employees, but with a team of 6 devs only in total, I'm the product owner). 

 

Thanks!

2 answers

2 accepted

0 votes
Answer accepted
Kevin Bui Atlassian Team Jan 21, 2020

Hi @Kevin Sauvageau - As far as I know, the method you've suggested is the only way to change a Story/Bug/Task to a subtask.

But if you don't want to go through that hassle, depending on the nature of the tasks you might find it more appropriate to link the two issues, to indicate a relationship between them. For instance, you can mark it so that one issue relates to another.

Not sure if it's appropriate for the tasks that you're tracking, but it's an alternative you can consider.

To learn more about issue links, check out the Atlassian documentation.

0 votes
Answer accepted
Lenin Raj Atlassian Team Jan 21, 2020

Hi @Kevin Sauvageau 

I actually have to go through "Move" action to move the issue as a subtask.

What you have already mentioned is the quickest way to convert an issue into a subtask.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events