Support Service Desk fields

[katherinepatrice]

Service desk fields (listed as custom fields) are not supported currently.
I see that Type: "array|sd-customerorganization" and many other "sd-" types are grayed out and not supported. Would it be possible to make these available?

[ljay79]

Hi @katherinepatrice
thanks for using my Add_on and for taking the time to request an enhancement.

As i am not a heavy user and i do not have access to an Jira instance with Service Desk, i can only give it a "blind" shot on trying to add support for such fields.

If you could kindly assist me with getting more details on such fields, i like to ask you to follow below procedure. This should give me quite good information on such fields and how to possibly add support for them into my add-on.

1. Add-ons -> Project Aid for Jira -> About

• Turn "on" debugging and provide me with the shown "Temp. User Key"

2. Add-ons -> Project Aid for Jira -> Configure Custom Fields

• Simply open that menu once after enabling debugging
• no further action needed

3. Perform a search using the Add-ons custom function "JST_search()"
   =JST_search(JQL; Fields; Limit; StartAt)

This will try to perform a query to your Jira instance with the given jira fields.
Even it will not properly return results to you, as the fields are not supported, it will certainly log the Jira issues response data to my StackDriver Logging account.
This way, i can analyze the fields response format and try to (blindly) implement support for such fields.

Please perform a search like this example:
=JST_search("status = Done"; "key,sd-servicelevelagreement"; 10)

Note: This will request Jira issue data and make them visible to me (me only) as long as the
"Debugging" option is enabled. So please choose a JQL query which does not return sensitive information :)

In case you have more of such custom fields, i believe the Jira field map (Add-ons -> Project Aid for Jira -> Jira field map) will list you all these custom fields and there names.
Important for my development is the name in column "ID".
You can perform above custom JST_search() adding these ID names into the second parameter and it will as well, give me some more detailed information in my logs on how to maybe implement support for same.

[ljay79]

Hi @katherinepatrice , any update on this? Do you maybe need further assistance for providing requested details?

[katherinepatrice]

Hello! Sorry for the late reply! OK so I did steps 1-3. My Temp User key: AANBUuXj7RZGH9VYxxeHVTMSWNuGPRzTinTFIqGIaxDV1Z7bt+ycuQquilebwPLdBVdU+zCDatFJ I tried a couple of different jql queries to bring up data - the = JST_search("project = RD", "key,sd-customerorganization", 2) one is a search for tickets that include these fields. I was not able to search successfully with the IDs pulled from the field map list (e.g. ID: customfield_14911), only with the name shown under "configure custom fields" - like "sd-customerorganization". We have a few more of these custom fields - the ones that are interesting to me at the moment are the service level agreement ones, as well as satisfaction and organization. ID: customfield_14911 array|sd-customerorganization ID: customfield_14921 sd-servicelevelagreement ID: customfield_10400 sd-servicelevelagreement ID: customfield_14902 Satisfaction (Type: "any" - not supported) Please let me know if you need any other information. Thank you, Kate

…

On Tue, Apr 2, 2019 at 12:46 PM Jens ***@***.***> wrote: Hi @katherinepatrice <https://github.com/katherinepatrice> , any update on this? Do you maybe need further assistance for providing requested details? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#191 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AugqVHyPm348AF3Sig3YMM2FL6Eabnaeks5vc7OGgaJpZM4cRWQL> .

[ljay79]

Thx, i will check what i got and how/if it can help.

[ljay79]

Hi @katherinepatrice , sadly this didnt helped that much as i was hoping. I dont have deep level debug active for these relevant parts.

Maybe the following will give me more input.
When you are logged in into your jira, open a second tab and access following URL:
https://ji.mfmnow.com/rest/api/2/field

It should return a JSON response with all your jira field types and mapping, if you could pass me this data her or by email to github [at] jens79 [dot] de that should hopefully give me more insights on how to add support to service desk fields.
Couldnt find detailed info on atlassian doc's itself yet.