Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA] - Add different bug ID depending on the ENV / ROBOT / COUNTRY #1946

Closed
Nouxx opened this issue Mar 1, 2019 · 3 comments
Closed

[IDEA] - Add different bug ID depending on the ENV / ROBOT / COUNTRY #1946

Nouxx opened this issue Mar 1, 2019 · 3 comments

Comments

@Nouxx
Copy link
Contributor

Nouxx commented Mar 1, 2019

Currently, a Bug ID can be linked to a test case (one to one)

If we launch the campaign on several countries / env or robots, the bug will still be attached to all the executions. What do you think about implementing a way to have different bug ID for the same testcase.

If there's a need, we could start discussing on it !

@ruirpr
Copy link

ruirpr commented Apr 24, 2019

Agree. Currently we write the country in the bugs comments.

@vertigo17 vertigo17 self-assigned this Dec 21, 2019
vertigo17 added a commit that referenced this issue Dec 29, 2019
added to testcase executor that is copy to execution executor in case the execution is manuel. Also prepared some stats on ReportByStat (only inside servlet).
executor available in mass execution modal.
removed ticket and project from testcase table.
Added tracability tab to execution detail.
vertigo17 added a commit that referenced this issue Jan 2, 2020
Added V0 of bug summary section in reportbytag page.
@vertigo17
Copy link
Member

image

Every bug link can now be desactivated and date of creation and date of closure is saved.

An optional control were also added on empty description thanks to parameter : 'cerberus_testcasepage_controlemptybugdescription'

vertigo17 added a commit that referenced this issue Jan 19, 2020
… closure and creation date). #1926 and #1946.

parameter cerberus_testcasepage_controlemptybugdescription allow to activate a control on empty description
@vertigo17
Copy link
Member

vertigo17 commented Jun 27, 2020

I close this issue as multiple bug is now available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants