Issue with create issue REST API after Jira Upgrade

[Erik Buchholz]

We are upgraded our test instance of Jira (data center) from 8.13.6 to 8.20.7 with Project Specific Select Fields from 3.0.0 to 3.0.2.

We have an Confluence page where we use ConfiForms Plugin to create an Jira issue over Jira REST API. Confluence and ConfiForms are not upgraded.

Currently we are using a JSON like

{
  "fields": {
    "project": { "key": "TEST" },
    "issuetype": { "name": "object" },
    "summary": "summary of 1234",
    "customfield_10100": [{"name":"Value A"}],
    "customfield_10103": "1234",
  }
}

Customfield 10100 is a sproject specific multi select field while customfield 10103 is a label like custom field.

This works in Jira 8.13.6 and PSSF 3.0.0 but in 8.20.7 only project, issuetype, summary and customfield 10103 are set correct. The value for customfield 10100 is ignored.

Did you mention something similar?

To check the behavior I created a Automation for Jira with manual trigger and issue modification with the two customfields in the JSON. It’s the same here. While customfield 10103 is updated. The value for customfield 10100 is ignored.

[Holger Schimanski]

There is no change in PSSF REST API between 3.0.0 and 3.0.2.

It could be that in Jira 8.20 you are no longer able to update non-standard custom field types. PSSF is actually subclassing the Jira standard custom field type, but this likely interpreted as custom field type.

Could you check that with your support for ConfiForms?

Did you try to call the same REST API call directly eg from curl to Jira REST API?

[Erik Buchholz]

Thanks for your reply. I will get in touch with Jira Support as the behavior is the same with Automation for Jira and should be independent of ConfiForms. I’ll keep you updated.

Regards

[Erik Buchholz]

Hi Holger,

I found the mistake. The correct JSON is

{
  "fields": {
    "customfield_10100": [{"value":"Value A"}]
  }
}

so with value instead of name.

Kindly excuse any inconvenience.

Regards,
Erik

[Holger Schimanski]

Oh that‘s good. Thanks for the update and closing the issue.