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