Change "Issue" parameter of "Add-JiraIssueAttachment" to accept pipeline input

[arestarh]

Expected Behavior

"Add-JiraIssueAttachment" cmdlet should accept pipeline input, but for "Issue" parameter, according to 'Get-Help Add-JiraIssueAttachment -Full', "Accept pipeline input? false".

Current Behavior

"Add-JiraIssueAttachment" cmdlet does not accept pipeline input.

Possible Solution

Extend parameter block of "Issue" parameter to accept pipeline input.

Steps to Reproduce (for bugs)

Context

Your Environment

Get-Module JiraPS -ListAvailable | select version
$PSVersionTable

[lipkau]

Please explain the use case.

When do you want to attach the same file (s) to multiple issues?

[arestarh]

I have a .csv file with info for several issues. For each issue I have separate file to attach.
I've just sent issue object to "Add-JiraIssueAttachment" cmdlet via pipeline, because I read about this possibility in examples. No special reason, just it's comfortable for me to use pipeline in this case.

[lipkau]

The file should be accepted in the pipeline. Not the issue.
Maybe the example is wrong.

Well... I need to check if PS can differentiate between to pipeline parameter if one is a PSObject.
If so, I'll add this in the next minor release
If not, it will have to wait for the custom object...

[lipkau]

Tested...

It does work... but the type declaration of the -FilePath would have change to [System.IO.FileInfo] -> which would be a breaking change
Therefore the following are possible:

• Use Get-JiraIssue Foo-1234 | {Add-JiraIssueAttachment -Issue $_ -File "c;\temp\file.ini"} as a workaround
• Change the type of FilePath
  • this would make the parameter to be renamed --> would be good to evaluate other cmdlets and see how they did it
  • which will take a while
• Wait until [JiraPS.Issue] has a class for itself
  • which will take a while
  • would be good to evaluate if it would make sense to change -FilePath to a [System.IO.FileInfo] as well

If anyone can think of another alternative, please share

[arestarh]

Mentioned workaround sounds good to me. Thanks.