[Jira] document assign_issue() usage for Jira Server #929
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
jira server usage for assign_issue account_id parameter
gtshepard
changed the title
gtshepard
changed the title
gtshepard
changed the title
gonchik
pushed a commit
that referenced
this pull request
Sep 3, 2022
jira server usage for assign_issue account_id parameter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Context
Documentation for
account_idparameter forassign_issue()is misleading for usage with Jira Server.Fix: Update Method Documentation
When using Jira Server;
assign_issue()'saccount_idparameter must take a valid Jirausername.The parameter does NOT take a Jira Cloud
account_idor Jira Serveruser_idas current docs for this project suggest when using Jira Server.Reference materials for endpoint
assign_issue()calls for Jira Server can be found here.Example
Method documentation has been updated to avoid future confusion.