Add parameter for non-set operations in Set-JiraIssue about jiraps

[replicaJunction]

Hi! Sorry for the delayed response to this; I've had a lot of RL changes recently that have kept me busy.

I hadn't initially designed Set-JiraIssue to accept comments, as that was sort of the purpose of Add-JiraIssueComment, but your use case does make sense.

Are there a lot of fields that trigger this behavior, or is the comment field the primary one you've noticed? If that's the biggest offender, we may be able to add a handler specific to comments in the Fields hashtable.

Your idea for a FieldOperation parameter is a good one, but we'd have to have a way of associating a specific operation with a specific field - or just assume that all fields will use the same operation in a single call. That might take a bit more thought...perhaps a nested hashtable?

$fields = @{
    comment = @{
        add = 'Another insightful comment'
    }
}

Get-JiraIssue -Key "Test01" | Set-JiraIssue -Fields $fields

[replicaJunction]

I still see the use in this feature, but I haven't figured out a good way to do so. I'm adding the "help wanted" tag to see if anyone else wants to chime in with some ideas.

[jjhayter]

No worries. I was thinking of a child object something along the lines of PSJiraField that would be a hashtable containing the FieldName and ApiMethodType (Add, Edit, Update, etc). What I am debating is whether or not this becomes too brittle in the long term.

[lipkau]

@replicaJunction
I see it as to cumbersome to handle comments in this command.
Making the fields has contain the operation add a new layer of complexity only for the comments to benefit from it.
Also, this only usecase this works well is adding a new comment. But that is not was Set- is supposed to do. It is supposed to be able to change the comment (edit).

I recommend adding a line to remove the comment element from the hash, if present and only allow for comments to be managed by dedicated functions.