Jira Cloud - Unable to set standard fields

[Gareth Cantrell]

How can we set standard Jira fields (not customfields) when creating a Jira request from a workflow?

I am trying to create a Jira ticket from a workflow and I need to be able to set some standard Jira fields; in this case:

• Due Date (field id: duedate)
• Parent (field id: parent)

However, it seems that we are only able to set custom fields with whose format is "customfield_12345" as the Hornbill automation automatically prepends the "customfield_" to the field id.

I tried to use the field ids above in the the custom fields properties (see attached screenshot) of the Atlassian/Jira Cloud/Create Issue cloud automation with the following error:

Jira Error: customfield_parent: Field 'customfield_parent' cannot be set. It is not on the appropriate screen, or unknown.

[Joshua Howitt]

Hi @Gareth Cantrell, I am looking in to this now and will let you know as soon as I have an update.

[Joshua Howitt]

Hi @Gareth Cantrell, looking at the documentation provided by Atassian when referencing any Custom Field via the api it needs to be appended with 'customfield_FIELDNAME'.

[Gareth Cantrell]

That is true for custom fields, although I've always used the full format in integration (customfield_<id>) rather than just supplying the ID and letting the code fill in the customfield_ bit.

Also, if you look at the JSON request format for Jira, all fields, custom and otherwise are sent in a single "fields":{} object, so within that object I can send a field named "customfield_10000" or "parent". There is no distinction, other than the naming convention.

The main thing for me right now though, is being able to supply some of the standard fields, eg. Parent and Due Date.

[Joshua Howitt]

Hi @Gareth Cantrell, I understand apologies for the confusion, I will look in to adding these standard fields as options for you and update you as this develops. 

[Joshua Howitt]

Hi @Gareth Cantrell,

The changes to the Jira Cloud have been pushed live 'Due Date' and 'Parent' should now be available for use in both issue Creation and Updating as standard fields.