Would one not want to create a "Bugs" subtask type?

I was debating creating a subtask type called "Bugs" or even migrating "Bug" into a subtask type. I just find this interface easier when associating all bugs related to a story, as opposed to creating bugs manually and having to link one by one to the parent story. Are there any cons to this?

2 answers

1 accepted

2 votes
Accepted answer
May be define it like this. Those bugs which are find during the development of the story goes as sub tasks. There will always be bugs coming after the story was developed, may be even months later, they should just be created as normal bugs. Also keep the normal level bugs open for anyone to raise an issue they find, including customers

I like this approach. I saw in the documentation that they had possible options for Sub-Type as "Sub-Bugs"which would be mini sub-tasks for Bugs. This allows us to classify our bug types to a main bug issue (e.g. like registration is broken) and then sub-bugs (e.g. 1) verification email not being sent 2) user can log in without verifying, etc)

1 vote

No cost, other than the effort needed to migrate your data.

If you find bugs work well as sub-tasks of stories, then that's the way you should do it!

Sorry, I was assuming you had already got some bugs in a project that you wanted to convert to sub-tasks of stories. You'll need to migrate them to sub-tasks of their parents.

If you're starting with a new project, that's fine, there's no migration to worry about.

As Renjith points out, it might also be worth having an "issue type scheme" that has "Big Bug" at the top level, and then "Little bug" as a subtask type.

Thanks Nic for your help. I'm pretty new to this so could you give me an example of how it would make it harder to migrate data?

Would it affect any type of reporting or anything?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,716 views 17 21
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you