Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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). 



2 answers

2 accepted

0 votes
Answer accepted

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.

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,184 views 10 14
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you