The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is there a way to create a bug within a subtask? Do not want to go via linking approach

Pooja Kurbetti
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2022

Hi Team

Is there a way to create a bug within a subtask?

I want all my bugs linked under a subtask that qa had picked

Currently its very painful to link every bug one by one, imagine a qa raise 20 bugs and has to link each one of them is there no auto way to handle it?

 

If there could be a create button within subtask would be helpful

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
February 3, 2022

Sub-tasks can not contain further sub-tasks.  You will either need to use links, or raise bug sub-tasks against the parent story (of which the sub-task is already a part)

0 votes
Hannes Obweger - JXL for Jira
Atlassian Partner
February 3, 2022

Hi @Pooja Kurbetti

welcome to the community!

If you really want to create a bug "within" a subtask, I'm afraid that issue linking is the only way to model this.

There are apps in the Atlassian Marketplace that would make the issue creation easier; e.g. if you model your hierarchy in JXL for Jira and use the inline issue creation, it would automatically set the correct issue links for you:

subtask-bug-hierarchy.gif

(There's much more than this to JXL; it's really a full-fledged table/spreadsheet view on your issues. More info @ https://jxl.app. Disclaimer: I work on JXL :))

This being said, it may be worth rethinking your Jira "data model" - if you manage to model something that is more aligned with Jira's native Epic/Issue/Subtask hierarchy, you will typically get better experiences with in Jira. (JXL would still work perfectly fine, of course.)

Hope this helps,

Hannes