Adding the bug to test casess automatically

[Mine]

We have two options linking the issues to the test casess or adding the bug to the test cases to their each steps. 

First option;

 Second option ;

I expected after I added the issues to the test cases I can see the issues automatically. Without adding in the second option

I understand that second option is useful because each step has option to adding a bug. 

But I like to add all the issues to the estcases automatically for the execution without test steps. If I like to add every step I can add later. But I want to know how is the progress module by module. Is there any way "

I expected that after I added the issues to the test cases, I could see them automatically in the cycle without adding the second option. I understand that the second option (in the picture) is useful because each step has the option to add a bug.  But I prefer to add all the issues into the test cases automatically for the execution without test steps. Because all issue results are coming from Jira automation. I don't like to add each step bug manually to see execution. Is there any way to make it automatically?

Thank you for your help

[Marc - Devoteam]

Hi @Mine 

Contact the support department of the marketplace app.

But I do expect the to explain to you that this can only be done by adding issues.

Other test managements apps do the same as this is based is this issue required to have testing related or not.

My suspicion is that adding any issue from Jira on every test will impact the backed performance of the app.

Also I don't see the benefit inthis as this will clutter the overview of which issues have been useful to a certain test case.

[Michał Kowalewski_SolDevelo]

Hi @Mine 

This is Michał from SolDevelo, company behind QAlity Plus - Test Management for Jira, app you're using.

The feature works in the way that you should report a bug on the particular step which you can have multiple in the particular test case. Each step might bring another bug, therefore the feature is specially designed for test steps.

By assigning a bug directly to a test case, our app is unable to determine exactly which step has failed and a bug has occurred.

What's more, the way we suggest to retest a test case involves executing the same test case and not a modification, an already executed execution, because for now we do not offer a history of execution changes. What I'm pointing out is that any execution can have its bugs and not just a given test case.

Remember that only bugs that were reported during the execution on the particular step will be visible in the Traceability Report.

If you have any additional questions or suggestions then I encourage you to contact us through the Customer Portal. We respond faster there than on the Atlassian Community.

And if you want to learn more about the app then check out our video onboarding playlist.

Kind regards,
Michał
SolDevelo Team