fix(bugfix): SendCustomHeaderForAddAttachmentApi as per the jira api … #152
Conversation
This file contains hidden or 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
|
Hi @balaprasanna! Thanks for your PR. Why using const config = {
host: '...',
noCheckAtlassianToken: true,
}; |
|
I looked again at the Jira Cloud API specification for issue attachments and saw that this token is mandatory, so I'm adding this to the master branch. Thanks for the PR! |
|
Thanks @MrRefactoring. |
Merged
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.
Hi @MrRefactoring and Team,
As per the JIRA Api doc,
We need to pass a custom header for Attachment api. (adding a new attachment to an issue)
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-issue-issueidorkey-attachments-post
'X-Atlassian-Token': 'no-check'Issue: Without this header, currently the post request received error like
XSRF check failedSimilar issues reported: https://ecosystem.atlassian.net/browse/ACJIRA-317
Please review the PR.
Thanks