I have an internal workflow I am building out whereby external customers can submit a ticket through Jira Service Management and have it replicated over to Jira Product Discovery as an idea. One issue I am having is that I capture some information in a custom field on the JSM side that I am unable to copy over to a custom field by the same name within Jira Product Discovery.
I know that they are technically different fields, but I am not sure how to even reference the field on the Jira Product Discovery side, or if that is even possible. Even when I look at the automation options inside of Jira Product Discovery, the issue fields that are accessible seem to be globally set ones.
Any pointers?
Hi @Ylan Muller
To learn if a field is supported by automation rules, please use the how-to article linked below. Essentially you find an example issue (or idea for JPD), call the REST API with a browser, and search for the field. If it is not present, it is not supported by rules. This technique also helps to confirm the correct smart value syntax for a field, as smart values are name, spacing, and case-sensitive.
https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
Once you find your field, you may need to use JSON to edit it. Please look here for information on that technique:
https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
Kind regards,
Bill
This is excellent, thank you for linking these resources! Worked exactly how I needed it to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.