Attachment upload issue - Internal error

[Sandro Leone]

Hi

We have been having the following problem on our jira installation:

When uploading attachments to some issues, an internal error shows up.

Following some of the questions I found online, I created a HAR of the issue and was able to reveal that the POST data was incomplete and the server response code was "0". The size of the body also was 0 bytes.

Further than that, I don't know how to find out more about this issue or how to even attempt to solve it.

[Sascha Krieg]

An easy way to do this is using the Collective Issue View for Service Desk Plugin. 
This plugin adds automatically groups of users as Participants. 

[Bartek Zukowski]

Thanks a lot, Kristian! That looks exactly like what I was looking for.

[Kristian Walker _Adaptavist_]

You may also find the article at https://confluence.atlassian.com/jirakb/how-to-automatically-add-request-participants-when-creating-an-issue-777026955.html here which shows how you can set users in the request participants field using a Post function which you may be able to convert into a behaviour.

Thanks

Kristian

[Kristian Walker _Adaptavist_]

Hi Bartek,

Sorry about the link it should of pointed to https://docs.atlassian.com/jira-servicedesk/REST/cloud/#servicedeskapi/request/{issueIdOrKey}/participant-addRequestParticipants

I hope this helps.

Kristian

[Bartek Zukowski]

Thanks Kristian,

but the link doesn't work

[Kristian Walker _Adaptavist_]

Hi Bartek,

Service desk uses system fields which cannot be set by the normal JIRA API.

However the latest versions of JIRA Service Desk contain a rest API which will allow you to use a Post Request to set Request participants. 

An example of the Add Participants method in the API can be viewed here.

I hope this helps

Kristian

[Bartek Zukowski]

'Request participants' is of type 'Request participants'  - it is a locked system custom field that is added by JIRA Service Desk. It works somewhat like multi user picker but not exactly, because you can add also an e-mail address there if a user doesn't have a JIRA account.

It stores people involved in an issue - so it's like a field to store watchers but in a different way. Our 'watcher field' (that is added by installing Watcher Custom Field for JIRA add-on) is easily populated by placing user names like:

watcherField.setFormValue("user1,user2,user3")

[JamieA]

What type of field is Request Participants? You can see that in Admin -> Custom Fields. May be a multi user picker?