-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Comments
Can you provide the error log as seen in #363 ? |
@Prome88 , I remove the automatic added context, actually this is a new request not a bug. |
@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 ? |
yes. @atodorov |
@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 this is possible, refer pycontribs/jira |
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:
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. |
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.
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.
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.
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.
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.
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.
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!
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!
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!
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!
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!
and link the URL of the newly reported issue to the TE
and link the URL of the newly reported issue to the TE
and link the URL of the newly reported issue to the TE
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
The text was updated successfully, but these errors were encountered: