custom field with variable

inlikefletch commented 7 years ago

Curious how one can create an issue with declaring a fields argument when the component name is a variable. i.e.: -Fields @{'components'= @(@{name = $categoryName})}

Current Behavior

I get an error stating: Get-Member : You must specify an object for the Get-Member cmdlet.

Context

I assume there is some issue of how to declare an object in an array in an object with a variable.

Your Environment

Get-Module PSJira -ListAvailable select version Version

1.2.5.251 $PSVersionTable Name Value

PSVersion 5.0.10586.117
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.10586.117
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Thanks, Jason

P.S. awesome model!

lipkau commented 7 years ago

Can you describe how you would like it to work?

inlikefletch commented 7 years ago

Yes, so in the following example, I supply a New-JiraIssue command with variables

i.e. New-JiraIssue -Project $project -IssueType $issueType -Reporter $reporter -Summary $summary -Description $description -Fields @{'components'= @(@{name = $categoryName})}

But it does not like the format of the fields attribute. If I eliminate the variable in the fields attribute, and just have a string, it works. But I would like to determine how to use a variable in the field.

i.e. New-JiraIssue -Project $project -IssueType $issueType -Reporter $reporter -Summary $summary -Description $description -Fields @{'components'= @(@{name = 'MyCategoryName'})}

inlikefletch commented 7 years ago

Okay, so I come to learn its not an issue of my code, but rather where I am running the code. The following works on my desktop, but not the server.

New-JiraIssue -Project $project -IssueType $issueType -Reporter $reporter -Summary $summary -Description $description -Fields @{'components'= @(@{name = "$components"})}

I need to do some more troubleshooting.

Thanks, Jason

inlikefletch commented 7 years ago

On my server, I see the following error. Command works fine on my desktop. Updated server to match PSVersion 5.1, still have the issue. Get-JiraIssue commands work fine on the server. Not sure why PS on my server is handling object differently or if some other module is require for PSJira.

PS C:\Users\user> New-JiraIssue -Project $project -IssueType $issueType -Reporter $reporter -Summary $summary -Description $description -Fields @{'components'= @(@{name = "$components"})} -Verbose VERBOSE: Using saved Web session with username jirauser VERBOSE: GET https://jira.xxx.xxx/rest/api/latest/project/SVCS?expand=projectKeys with 0-byte payload VERBOSE: received -1-byte response of content type application/json;charset=UTF-8 VERBOSE: Using saved Web session with username jirauser VERBOSE: GET https://jira.xxx.xxx/rest/api/latest/issuetype with 0-byte payload VERBOSE: received -1-byte response of content type application/json;charset=UTF-8 VERBOSE: Using saved Web session with username jirauser VERBOSE: GET https://jira.xxx.xxx/rest/api/latest/issue/createmeta?projectIds=11632&issuetypeIds=16&expand=projects.issuetypes.fields with 0-byte payload VERBOSE: received -1-byte response of content type application/json;charset=UTF-8 Get-Member : You must specify an object for the Get-Member cmdlet. At C:\Program Files\WindowsPowerShell\Modules\PSJira\1.2.5.251\Internal\ConvertTo-JiraCreateMetaField.ps1:37 char:32

... eldNames = (Get-Member -InputObject $fields -MemberType '*Property'). ...


+ CategoryInfo          : CloseError: (:) [Get-Member], InvalidOperationException
+ FullyQualifiedErrorId : NoObjectInGetMember,Microsoft.PowerShell.Commands.GetMemberCommand

lipkau commented 7 years ago

@inlikefletch please open the following URL in a browser in which you are already authenticated with your jira server and send me the json that is displayed:

https://jira.XXX.XXX/rest/api/latest/project/11632

inlikefletch commented 7 years ago

Hi @lipkau Thanks for the response. What are you looking to gain from that url? I am cautious to post any internal data. I understand which fields are required for my post commands. And like I mentioned, this exact command works on my desktop.

lipkau commented 7 years ago

The error you posted is due to the input to the ConvertTo-JiraCreateMetaField to be empty. Which means that the Get-JiraIssueCreatMetadata is getting no response for the issue types in the project.

The url I sent you gives the config of the project. Except for the url of your server, it contains no sensitive information

inlikefletch commented 7 years ago

@lipkau copied below:

lipkau commented 7 years ago

ok. json looks fine. there must be an other reason for the problem... what is different between the desktop and the server? http proxy maybe? sure the credentials are ok?

inlikefletch commented 7 years ago

Issue resolved. Ended up being a permissions issue within jira permissions.

Thanks for helping!

AtlassianPS / JiraPS