Open beaudryj opened 7 years ago
Would it make more sense to call this Set-JiraIssueComment
rather than Update
? This would be more consistent with Set-JiraIssue
, Set-JiraUser
, etc.
I will take this one
Add Get-JiraComment please
@Dejulia489 Are you still working on this issue? I have a Set-JiraIssueComment
implementation in my branch that's almost ready for a PR.
@hmmwhatsthisdo sorry to bother you but did you finish the implementation for Set-JiraIssueComment
?
@hmmwhatsthisdo sorry to bother you but did you finish the implementation for
Set-JiraIssueComment
?
@Zeebiro I ended up leaving that job shortly afterwards so I had no JIRA instance to work on. The branch I created had the bare-minimum functionality that I needed at the time, but IIRC it wasn't fully PR-ready (I don't think I wrote tests for it).
If you'd like to leverage the implementation work I did, you're more then welcome to do so. (Some fiddling with remotes/branch rebases should let you reuse my commits against the current codebase)
api/2/comment
Update-JiraIssueComment
Update-JiraIssueComment
orSet-JiraIssueComment
Updates an existing comment using its JSON representation. PUT /rest/api/2/issue/{issueIdOrKey}/comment/{id}Parameter
-Issue
int / PSJira.Issue mandatory-commentID
int / commentID mandatory-comment
string / comment (must this be mandatory?)-VisibleRole
enumerationRemove-JiraIssueComment
Remove-JiraIssueComment
Updates an existing comment using its JSON representation. DELETE /rest/api/2/issue/{issueIdOrKey}/comment/{id}Parameter
-Issue
int / PSJira.Issue mandatory-commentID
int / commentID mandatoryHelpful links