Jira Connector custom fields

Question

I am trying to create a JIRA issue using an Azure logic app and the JIRA connector.

There are a number of mandatory custom fields in the project I am trying to create the issue in.

I have no problems assigning the values for some of the custom fields. However, I am receiving the following error when trying to set the value for customfield_10119:
"customfield_10011": "Field 'customfield_10011' cannot be set. It is not on the appropriate screen, or unknown."

This makes no sense because the input JSON contains the following:
"fields": {
"customfield_10119": {
"value": "My Custom Field Value"
},
"description": "This is a test issue created by an Azure Logic App execution.",
"issuetype": {
"id": "10009"
},
"priority": {
"id": "1"
},
"summary": "Azure DF JIRA integration Test"
}

Nowhere in the input JSON is there a reference to customfield_10011. In fact, there is no field in our JIRA database with this ID (10011).

I did notice from the JIRA connector documentation (https://learn.microsoft.com/en-us/connectors/jira/) that customfield_10119 is associated with "Epic Name". In our JIRA Server setup, Epic Name is customfield_10104.

My questions, thus, are:

1. Is there a particular reason why the JIRA connector has the Epic Name hardcoded to customfield_10119, when this particular code can be associated with a completely different custom field and is dependent on each individual JIRA setup?
2. How does the connector error output reference customfield_10011 when setting the value for customfield_10119 in the input JSON? Is this a hardcoded association or is it random?

Answer 1

Hi @Marcell Abrahams

I agree with you that the Jira connector should leverage dynamic schema to work with custom fields. The exact field for ‘Epic Name’ is currently hardcoded in the code and the product group is checking the feasibility if this can be dynamic.

The error code that you are seeing is not random when you are setting customfield_10119. The product group is working on this to reflect the correct error message.

I will update my answer once I have further updates from my team.