< Back

Add-JiraIssueComment

Thu Jan 16, 2020 7:43 am

NAME Add-JiraIssueComment



SYNOPSIS

Adds a comment to an existing JIRA issue





SYNTAX

Add-JiraIssueComment [-Comment] <String> [-Issue] <Object> [[-VisibleRole] <String>] [[-Credential]

<PSCredential>] [-WhatIf] [-Confirm] [<CommonParameters>]





DESCRIPTION

This function adds a comment to an existing issue in JIRA. You can optionally set the visibility of the comment

(All Users, Developers, or Administrators).





PARAMETERS

-Comment <String>

Comment that should be added to JIRA.



Required? true

Position? 1

Default value None

Accept pipeline input? False

Accept wildcard characters? false



-Issue <Object>

Issue that should be commented upon.



Can be a `JiraPS.Issue` object, issue key, or internal issue ID.



Required? true

Position? 2

Default value None

Accept pipeline input? True (ByPropertyName, ByValue)

Accept wildcard characters? false



-VisibleRole <String>

Visibility of the comment.

Defines if the comment should be publicly visible, viewable to only developers, or only administrators.



Allowed values are:



- `All Users`



- `Developers`



- `Administrators`



Required? false

Position? 3

Default value All Users

Accept pipeline input? False

Accept wildcard characters? false



-Credential <PSCredential>

Credentials to use to connect to JIRA.

If not specified, this function will use anonymous access.



Required? false

Position? 4

Default value None

Accept pipeline input? False

Accept wildcard characters? false



-WhatIf [<SwitchParameter>]

Shows what would happen if the cmdlet runs. The cmdlet is not run.



Required? false

Position? named

Default value False

Accept pipeline input? False

Accept wildcard characters? false



-Confirm [<SwitchParameter>]

Prompts you for confirmation before running the cmdlet.



Required? false

Position? named

Default value False

Accept pipeline input? False

Accept wildcard characters? false



<CommonParameters>

This cmdlet supports the common parameters: Verbose, Debug,

ErrorAction, ErrorVariable, WarningAction, WarningVariable,

OutBuffer, PipelineVariable, and OutVariable. For more information, see

about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).



INPUTS

This function can accept JiraPS.Issue objects via pipeline.







OUTPUTS

[JiraPS.Comment]







NOTES





This function requires either the `-Credential` parameter to be passed or a persistent JIRA session. See

`New-JiraSession` for more details. If neither are supplied, this function will run with anonymous access to

JIRA.



-------------------------- EXAMPLE 1 --------------------------



Add-JiraIssueComment -Comment "Test comment" -Issue "TEST-001"



This example adds a simple comment to the issue TEST-001.

-------------------------- EXAMPLE 2 --------------------------



Get-JiraIssue "TEST-002" | Add-JiraIssueComment "Test comment from PowerShell"



This example illustrates pipeline use from `Get-JiraIssue` to `Add-JiraIssueComment`.

-------------------------- EXAMPLE 3 --------------------------



Get-JiraIssue -Query 'project = "TEST" AND created >= -5d' |

Add-JiraIssueComment "This issue has been cancelled per Vice President's orders."



This example illustrates commenting on all projects which match a given JQL query. It would be best to validate

the query first to make sure the query returns the expected issues!

-------------------------- EXAMPLE 4 --------------------------



$comment = Get-Process | Format-Jira

Add-JiraIssueComment $comment -Issue TEST-003



This example illustrates adding a comment based on other logic to a JIRA issue. Note the use of `Format-Jira` to

convert the output of `Get-Process` into a format that is easily read by users.



RELATED LINKS

Online Version: https://atlassianps.org/docs/JiraPS/com ... ueComment/

Get-JiraIssue

Get-JiraIssueComment

Format-Jira