New-JiraIssue - Service Desk Get-Member issue

[JoeJe1993]

When using New-JiraIssue on a Service Desk, an error about an incomplete Get-Member cmdlet comes up in ConvertTo-JiraCreateMetaField.ps1.

This doesn't happen on other types of Jira boards

[JoeJe1993]

[JoeJe1993]

[JoeJe1993]

I can't find the API you're referencing to in the API browser, the closest I came to was this:

[lipkau]

that's the same thing. /rest/api/latest will use /rest/api/2, as long as 2 is the latest.

@JoeJe1993 I need the full result of that url

[JoeJe1993]

@lipkau That is the full result. Here it is in plain-text:

{"expand":"projects","projects":[{"expand":"issuetypes","self":"https://[DOMAIN]/jira/rest/api/2/project/10100","id":"10100","key":"DOC","name":"[NAME]","avatarUrls":{"48x48":"https://[DOMAIN]/jira/secure/projectavatar?pid=10100&avatarId=10201","24x24":"https://[DOMAIN]/jira/secure/projectavatar?size=small&pid=10100&avatarId=10201","16x16":"https://[DOMAIN]/jira/secure/projectavatar?size=xsmall&pid=10100&avatarId=10201","32x32":"https://[DOMAIN]/jira/secure/projectavatar?size=medium&pid=10100&avatarId=10201"},"issuetypes":[]}]}

[JoeJe1993]

Hi @lipkau, any updates?

[lipkau]

Either Service Desk works differently... or this is a jira bug.

According to your screenshot, you have 5 issue types used by the Project. However, the API designed to give you the metadata of what fields are required, which are optional, what are the AllowedValues , etc is saying the project has no issuetypes.

I think I can get a trial version of Service Desk for my test server. If I do, I will install it and try it out. I might have time tomorrow or Sunday.

If you want to speed things up, you could use this information and ask in the atlassian community site if anyone knows anything about this. Or you could report a bug.

If anyone else has a server with Service Desk, I would appreciate some help with this, as I have 0 experience with this product

[brianbunke]

I just created my first JIRA Service Desk ticket via the API yesterday.

I was not able to get JiraPS 2.1.0.90 to create a ticket in a Service Desk project. I consider myself pretty up-to-speed on the code base, and I spent about 15 minutes debugging. Here's the bad news: Nothing was obviously wrong.

Instead of spending hours making sure, I explored JIRA Service Desk's REST API endpoints instead, and successfully created a test ticket before the weekend.

JIRA SD REST API reference: Cloud: developer.atlassian.com Server: docs.atlassian.com

The most important thing I learned: JIRA ID #s are not the same as JIRA SD ID #s. Here are some rough examples from memory:

Name	Type	JIRA ID	JIRA SD ID
TEST	Project	10110	2
Get IT Help	Request Type	10222	25

This raises messy questions.

• Is anyone going to spend hours trying to make SD accept a normal JIRA API request?
  • My answer is definitely no
• So, should JiraPS be extended to detect and accommodate for this?
• Or should JIRA SD be deemed "unsupported," with recommendations to start a standalone repo?

[lipkau]

I have create 3 different kinds of Service Desk projects in my jira:

All 3 have these Issue Types:

With this setup I was able to:

• get all the metadata of that project (incl. the issuetypes):
  
• create a new issue:
  

I did find an issue for the CLI of jira with the same behavior. It appear to be a matter of permissions: https://bobswift.atlassian.net/browse/JCLI-768?focusedCommentId=32437&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-32437 As I am no expert on Service Desk, I don't know how to help with that.

As I was able to use JiraPS for Service Desk, I will remove the label Bug; at least for now

[brianbunke]

Ok, you made me curious, and I'd like to try replicating on my end.

Cloud or server? What versions of JIRA & SD?

[lipkau]

PS Projects:\jiraps> Get-JiraServerInfo
baseUrl        : https://powershell.atlassian.net
version        : 1000.1323.0
versionNumbers : {1000, 1323, 0}
deploymentType : Cloud
buildNumber    : 100062
buildDate      : 2017-09-26T00:00:00.000+0200
serverTime     : 2017-09-27T08:39:04.861+0200
scmInfo        : f3c60100df073e3576f9741fb7a3dc759b416fde
serverTitle    : JIRA

[brianbunke]

Just got back to testing this, conveniently with v2.4:

I can confirm that the most basic form of New-JiraIssue works against vanilla Service Desk projects in both JIRA Server (7.5.1) and Cloud. My problem previously was with an overcomplicated SD project that had some involved field requirements.

[lipkau]

@JoeJe1993 and @JohnTheDon01 Please test again with latest module version. If it doesn't work, let me know the jira version you are running. Ideally you would also test this with a fresh SD project.

I will close this issue in 2 weeks if I don't get feedback