Integration with Jira Standalone server #751
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've prepared the issue for this pull request - #752 |
ehsandeep
added
Status: Review Needed
|
Thank you @gano3s for detailing the issue with the proposed fix / PR, we will review it asap. |
Ice3man543
approved these changes
Jun 4, 2021
ehsandeep
added
Status: Completed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The current implementation does not work very well with non-Cloud version of Jira. See details below:
I am a newbie in golang - please let me know, if there is any need to update the proposed behavior.
Description
We are using the on-premise version of Jira server (v8.13.2#813002) and the Jira reporting feature does not work correctly. The RestAPI for the on-prem version is different then the Jira Cloud instance. Set an example in our release, the jira account does not have any accountId and login via email does not work.
The fix requires to use the username instead of it.
Once the fix UI is correctly authorized, the next issue is with the creation of the new issue. The field
reporteris not recognized by the RestAPI and it requires to useNameinstead of theAccountIDNuclei version
Tested on the latested dev version of the nuclei. The same behavior even on v2.3.7.