-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
-
all
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
This API works, but does not allow you to specify the comment author. It ignores the "author" field and instead uses the logged-in user. Naturally, in an integration scenario, you dont want to use the logged-in user but rather be able to specify who has made the comment.
Please not that not all SOAP APIs work in that manner: the createIssue API (which is very similar in nature to addComment) takes in a "reporter" field and uses it to capture the user who reported the issue, this gives the external application the ability to correctly create an issue on behalf of a user, while such ability does not exist when you try to create a comment, thus, making the createComment API somewhat pointless. I think this can be easily fixed by adding a new "reporter" attribute to the RemoteComment object or using the existing "author" or "updateAuthor" attributes.
This is a major issue for our company as our service depends on integration with Jira over SOAP. Thank you for your attention.
- is cloned from
-
JRASERVER-19392 addComment SOAP API
- Closed
- is duplicated by
-
JRASERVER-24824 When using the Jira RPC SOAP Plugin for Jira 4.2.3 and trying to add a comment. The author of the comment can only be set to the user who is authenticated to the SOAP service.
- Closed
- relates to
-
JRACLOUD-19416 addComment SOAP API
- Closed