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

Feature: "Report Issue" to automatically add the bug number/URL to TestExecution #479

Closed
hakehuang opened this issue Aug 17, 2018 · 7 comments
Closed

Comments

@hakehuang
Copy link

@hakehuang hakehuang commented Aug 17, 2018

in bug report for test case, we can report a bug with existing ticket ID for jira, but if we want to report a new bug(we can not provide the jira ID for a new bug), this seems not applicable.

@Prome88
Copy link
Contributor

@Prome88 Prome88 commented Aug 28, 2018

Can you provide the error log as seen in #363 ?

@hakehuang
Copy link
Author

@hakehuang hakehuang commented Aug 29, 2018

@Prome88 , I remove the automatic added context, actually this is a new request not a bug.

@atodorov
Copy link
Member

@atodorov atodorov commented Mar 19, 2019

@hakehuang - do you mean to say that if you click the button "Report Issue" the issue number from Jira is not added back automatically to the test case run ?

@hakehuang
Copy link
Author

@hakehuang hakehuang commented Mar 20, 2019

yes. @atodorov

@atodorov
Copy link
Member

@atodorov atodorov commented Mar 20, 2019

@hakehuang - the current implementation doesn't allow for this and I'm not even sure this is technically possible. At the very best we will be able to report an issue in issue tracker via API and get a link back to it and the user will have to click and edit various fields in the issue tracker itself.

We'll keep this open for now to investigate how and if this will be possible.

@atodorov atodorov changed the title create a new ticket in bug tracking system Feature: "Report Issue" to automatically add the bug number/URL to TestCaseRun Mar 20, 2019
@hakehuang
Copy link
Author

@hakehuang hakehuang commented Mar 28, 2019

@atodorov this is possible, refer pycontribs/jira

@atodorov atodorov added this to the bug-tracker integration milestone Jul 30, 2019
@atodorov atodorov changed the title Feature: "Report Issue" to automatically add the bug number/URL to TestCaseRun Feature: "Report Issue" to automatically add the bug number/URL to TestExecution Sep 15, 2019
@atodorov
Copy link
Member

@atodorov atodorov commented Sep 15, 2019

Something like this is POC'ed in the upcoming KiwiTCMS bug tracker (#699). Once that part of the code is merged the following needs to be done for this functionality to be resolved:

  1. For GitHub, GitLab (maybe some others) - post the bug report directly b/c they really need only title and body.

  2. For Bugzilla, JIRA (where you can have many custom fields and there could be mandatory fields) - try to create a bug, if it the operations fails catch that gracefully.

  3. If the previous step was successful then return the new bug URL so we can open it in another browser window. Also add that URL to the TE as reported bug (solves the current issue)

  4. If previous step wasn't successful fall back to opening a URL where the user can fill-in the missing fields. If this is the case we can't really add anything back to the TE

for 2) maybe figure out how to allow users to override the requests that are sent, or document an easy way to override their IT integration code which will take into account all required fields that may exist. This can be done separately.

atodorov added a commit that referenced this issue Dec 24, 2019
teach Kiwi TCMS how to automatically report issues to GitHub when
user clicks on the Report button. Part of 1-click bug report
functionality!

Falls back to manually creating the issue if something doesn't
work.
atodorov added a commit that referenced this issue Dec 24, 2019
teach Kiwi TCMS how to automatically report issues to GitHub when
user clicks on the Report button. Part of 1-click bug report
functionality!

Falls back to manually creating the issue if something doesn't
work.
atodorov added a commit that referenced this issue May 18, 2020
NOTE: the FE still needs to refresh the UI once the 'Report' button
is clicked which will be implemented together with TR page UI
redesign by @asankov.
atodorov added a commit that referenced this issue May 18, 2020
NOTE: the FE still needs to refresh the UI once the 'Report' button
is clicked which will be implemented together with TR page UI
redesign by @asankov.
atodorov added a commit that referenced this issue May 18, 2020
NOTE: the FE still needs to refresh the UI once the 'Report' button
is clicked which will be implemented together with TR page UI
redesign by @asankov.
atodorov added a commit that referenced this issue May 18, 2020
NOTE: the FE still needs to refresh the UI once the 'Report' button
is clicked which will be implemented together with TR page UI
redesign by @asankov.
atodorov added a commit that referenced this issue May 22, 2020
Gitlab needs only title & description to open a new issue so we
do this automatically and also add the LinkReference to the TE
itself. UI still needs to be refreshed to reflect the new issue!
atodorov added a commit that referenced this issue May 22, 2020
Gitlab needs only title & description to open a new issue so we
do this automatically and also add the LinkReference to the TE
itself. UI still needs to be refreshed to reflect the new issue!
atodorov added a commit that referenced this issue May 22, 2020
Gitlab needs only title & description to open a new issue so we
do this automatically and also add the LinkReference to the TE
itself. UI still needs to be refreshed to reflect the new issue!
atodorov added a commit that referenced this issue May 22, 2020
Gitlab needs only title & description to open a new issue so we
do this automatically and also add the LinkReference to the TE
itself. UI still needs to be refreshed to reflect the new issue!
atodorov added a commit that referenced this issue May 22, 2020
Gitlab needs only title & description to open a new issue so we
do this automatically and also add the LinkReference to the TE
itself. UI still needs to be refreshed to reflect the new issue!
atodorov added a commit that referenced this issue May 30, 2020
atodorov added a commit that referenced this issue May 30, 2020
atodorov added a commit that referenced this issue May 30, 2020
atodorov added a commit that referenced this issue May 30, 2020
atodorov added a commit that referenced this issue Jun 1, 2020
and link the URL of the newly reported issue to the TE
atodorov added a commit that referenced this issue Jun 1, 2020
and link the URL of the newly reported issue to the TE
atodorov added a commit that referenced this issue Jun 1, 2020
and link the URL of the newly reported issue to the TE
asankov added a commit to asankov/Kiwi that referenced this issue Sep 18, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes kiwitcms#479
asankov added a commit to asankov/Kiwi that referenced this issue Sep 20, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes kiwitcms#479
asankov added a commit to asankov/Kiwi that referenced this issue Sep 22, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes kiwitcms#479
asankov added a commit to asankov/Kiwi that referenced this issue Sep 22, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes kiwitcms#479
asankov added a commit to asankov/Kiwi that referenced this issue Sep 22, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes kiwitcms#479
atodorov added a commit that referenced this issue Sep 22, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Oct 2, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Oct 12, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Oct 12, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Oct 14, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Oct 18, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Nov 8, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Nov 20, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
atodorov added a commit that referenced this issue Dec 1, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes #479
@atodorov atodorov closed this in 34b1091 Dec 1, 2020
asankov added a commit to asankov/Kiwi that referenced this issue Dec 2, 2020
Only add classes on `div.list-group-item`

`test-execution-{id}` and `test-execution-case-{id}` classes.

Otherwise this classes got added on an
`li` element in the attachments group and messed up our selecting logic

Closes kiwitcms#479
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants