You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be IMHO better to ignore the current check i.e. verify that the entered project matches the project configured for the JiraTestResultReporter.
This way we could link tests to issues are opened for another project in our JIRA.
Currently this is not possible and results in a failure
If the entered issue ID does not exists in JIRA, then the response from JIRA would trigger the "Not a valid issue key" error
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
What feature do you want to see added?
When manually linking a JIRA issue i.e.

It would be IMHO better to ignore the current check i.e. verify that the entered project matches the project configured for the JiraTestResultReporter.

This way we could link tests to issues are opened for another project in our JIRA.
Currently this is not possible and results in a failure
If the entered issue ID does not exists in JIRA, then the response from JIRA would trigger the "Not a valid issue key" error
Upstream changes
No response
The text was updated successfully, but these errors were encountered: