nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

After I convert a sub-bug into a bug, why the link between the story and the bug is lost?

SOFIANE BENMILA

On our regular workflow, when I test a stroy I enter my finding as sub-bugs.
Sometimes decision is taken to close the story and convert the sub-bugs into bugs for the backlog.
Is there a reason why the link between the story and the converted bug is lost?
Is there a way to change this default behavior?

Accepted answers

Alexey Matveev

Hello,

What kind of links do you use between story and sub-bugs? If you use subtasks for sub-bugs and bugs are usual tasks, then the link will be lost. If you want the link to be untouched, you should link Story and Sub-bugs with a custom link not with task -> sub-task link .

All comments

Alexey Matveev

Hello,

SOFIANE BENMILA

Hello Alexey,
Thanks for your prompt answer, you are right we use subtasks for sub-bugs.

Is it possible to set this custom link at the moment when we convert the sub-bug into a bug automatically or we can do it only manually (moments before converting)?

Thanks!

Alexey Matveev

You can do automatically if you have an add-on like ScriptRunner, Power Scripts, Automation for Jira. And even having these add-ons, it would be easier not to create a sub-task but a task and link it to the main task with a custom link. If you do not have such add-ons, then you can do it only manually.

SOFIANE BENMILA

Thanks for answers Alexey!
I understand. Solution for me will be to go manually.

Just to keep you in the context...
We made a choice by adding sub-bugs as sub-tasks for an "external dependency" reason:
We moved recently from TFS to Jira and we still automatically generating tasks and branches in TFS for each task created in Jira and not for sub-tasks (our code and build system is still being managed in TFS for now and for sometime ahead).

So, as a QA and in order to not pollute TFS with false items and branches, we choice to go with sub-bugs during story development phase.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud