Automate cloning ideas between two JPD projects?

[Hugo Maarten Fehmers]

Hi everyone,

I’m working on an automation rule in JPD to automatically clone an issue from our intake project to another JPD project immediately after submission. Specifically, I need to ensure that a short text field and a people field (@) is cloned exactly as entered.

To achieve this, I’m using the Clone issue action in Jira Automation and then configuring the Choose fields to set… option. In this configuration, I plan to map the value from the original field to the corresponding field in the cloned issue using a smart value, both fields have the same name but I can't find the field ID in JPD. My questions are:

1.How do I set the smart value so that it clones the corresponding field into the correct field of the other JPD project?

2.Are there any best practices or pitfalls I should be aware of when mapping fields between different projects, especially if the field names or IDs differ?

Any detailed guidance or examples would be greatly appreciated!

Thanks in advance for your help.

[Bill Sheboy]

Hi @Hugo Maarten Fehmers -- Welcome to the Atlassian Community!

From my observations, Jira Product Discovery (JPD) is based upon team-managed project (TMP) features.  And so the project-specific fields are distinct for each.  While there may be common, global scope fields used, you may need to copy the fields using JSON and their custom field IDs to get the correct source / destination values in the Ideas.  Here are some suggestions to help.

• To learn the correct custom field ID (and if your field is even supported by automation rules), find some example Ideas in the project with your fields, and then use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ The basic approach is using a browser tab to call the REST API, and then search for your field on the page.
• For the JSON format needed by field type, please see this documentation: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/
• Some JPD fields can be dynamically calculated, and thus those will not be copied: only their source fields for the calculation will copy.  Others cannot be set at all by rules, due to limitations in the REST API endpoints.  The earlier how-to article I noted will identify such fields, if any impact your Ideas.
• What do you want to do with the "intake" Idea after it is copied / cloned to the other project: close it, etc.?  Deciding that early may help prevent confusion if people find two open Ideas for the same request.

Finally, experimentation and testing are key!  If you run into challenges, please post images of your complete rule, the audit log details, and explain what is not working as expected.

Kind regards,
Bill