Jira connector custom field issue

[Anonymous]

I am using the Jira connector for Flow that creates a Jira card from a Forms response.
I am recieveing the following error when submitting a form, "customfield_10119": "Field 'customfield_10119' cannot be set. It is not on the appropriate screen, or unknown."

According to the documentation (https://docs.microsoft.com/en-us/connectors/jira), customfield_10119 is assigned to the 'Epic Name' field. However, in Jira the 'Epic Name' field is really customfield_10005.

Is there a way to change the set field on the connectors side or some other way to correct this issue?

[ghollingsworth]

Having the exact same issue, cause by this piece of the JIRA Create Issue Action:

"customfield_10119": "@{body('Get_response_details')?['rbfc321c212754c899a4544b659ca5218']} - Launch"

Can we get a fix on this? It completely prevents the flow from being used to create Epics

[Anonymous]

I am having this issue as well when using a flow to create jira issues from a SP list. Specifiying no text works for other issue types, but Epics require a name in Jira by default and this appears to be pointing at the wrong custom field ID. 

Edit: It appears that the field assigned for Epic Name is different across various instances. One of the above users mentioned their was an id containing 10005. The ID for one of the instances I am working with for Epic name is instead CustomFieldId_10007. 

This would be easilly rectified if I could change the custom field ID that is obviously wrong when viewed in the code peak: 

"customfield_10119": ...

[PriyankaB]

The issue still exist. Anyone has any update on this one?

[Hosko]

This issue still exists - May 2020 when reported quite a while ago It is looking for "customfield_10119": "@triggerBody()?['subject']" for the epic name but it's erroring out. EPIC name custom setting for mine is 10361 so I think what we need is an option to specify the correct custom field ID for multiple custom fields. Every install it looks like might be different. Would certainly assist

[JPMontoya]

Just jumping in to mention that I have the same issue (customfield_10008 would be needed in my case). I have also tried circumventing the predefined connector for the creation of epics by trying to set up a custom connector action to create an epic.

There however I keep running into CORS / XSRF check fails, which I can't seem to resolve, no matter which "fix" I try. Have any of you been able to work around this or attempted a custom connector for Jira yourselves?

[smak]

Adding yet another bump to this...as of Feb 2021 there is still not a way to change the customfield name to the Instance's Epic field name...mine is 10008 - not the default Microsoft is forcing on us. Please fix or at least respond to our messages on what you're doing with it.

[cstair]

Hi I wanted to add to this thread that I am seeing the same issue on my connector. 

{

  "errorMessages": [],

  "errors": {

    "customfield_10011": "Field 'customfield_10011' cannot be set. It is not on the appropriate screen, or unknown."

  }

[ghollingsworth]

That would indicate that the custom field is not present on the "Create" screen for the issue. Any value that you want to pass in via the Create Item API (which is what the connector is using), it must be present on the "Create" screen for the project in JIRA.

[jordine]

Limitations are explained here:

https://learn.microsoft.com/en-us/connectors/jira/

Perhaps this will help you because it helped me!