Better support for using Automation in Next Gen / team-managed Jira projects: bugfixes, support for custom issue types, show what project custom fields are for, display User Picker fields from Team Managed projects

Bugs

• Next-gen parent smart values are not reliable on issue creation - There appears to be some timing issue with accessing parent values on issue creation in next-gen projects. Adding a re-fetch action seems to work but in general accessing parent next-gen fields on issue creation appears unreliable.
• Copy from parent and Epic does not work in the Next gen Project - GSAC Case - https://getsupport.atlassian.com/browse/PCS-23859?focusedCommentId=24712146&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24712146
• Transition the linked issues across two next gen projects using a smart value fails - In next gen cases status ids don't match(across projects) even for same status name.
• In Next gen project , Using "Send Email" action and set the "To" as "Approver" or "Pending Approver" doesn't work
• Next-gen | "Issue fields condition" values for select list are displayed incorrectly when the name of the filed is the same - Next-gen | "Issue fields condition" values for the select list are displayed incorrectly when the name of the filed is the same in two or more next-gen projects
• NextGen | Updating parent links does not triggers "Issue Updated"
• Create & edit issue shows custom fields from other project contexts always - Jira next gen fields should list what project the are for in our dropdowns - Next gen removes field sharing across projects. This means that multiple projects that have the same field name across them will actually create two unique fields which have the same name. This is confusing to use in dropdowns across our app because there is no additional contextual information besides the field name. This requires users to guess at the correct field and often people result to trial and error when building automations.
• Support the Jira Next-Gen People field - This feature request is to add people field into Automation for Jira. Currently, we don't support the people field. This field is from Next-Gen project. We should also support sending emails to users in people fields as well.

Multiple issue types support for next gen - support for custom issue types - Area of effect:

• Condition: Issue fields condition
• Action: Create issue
• Action: Edit issue
• Action: Clone issue
• Action: Create sub-tasks
• Action: Transition issue
• More component?

Issue type ids won't be updated when we switch the scope between next gen and classic project

Reproduce:

1. create a rule for a classic project
2. select the condition with different issue types
3. change the rule to a next-gen project
4. publish the rule

Expect result:
The issue type ids are updated to next-gen project's issue type ids or an error indicates customer the current issue types are in different project types

Actual result:
The issue type ids are not updated. No message indicates the inconsistent issue type ids. And the rule is failed which not enough message to let the customer know the ids are not right.

Issue Summary

If a Team Managed project has a User Picker field available for an issue type in the respective layout, Automation for Jira doesn't display it as an option when selecting an action for Edit issue fields.

Steps to Reproduce

1. Access a Team Managed project
2. Create a custom field of the user picker (People) type
3. Make it available for an issue type
4. Head to Automation for Jira rules
5. Create a single project rule selecting the respective Team Managed project
6. Use any trigger
7. Select the action Edit issue fields
8. Look for the newly created custom field

Expected Results

Custom field should be displayed as an option to be used

Actual Results

Custom field is not displayed

Workaround

Depending on the complexity of the rule you are trying to make, the following workaround might not be an option, but you can change the workflow of your Team Managed project associated with the issue type. You can read more about it through this link.

Alternatively, you can use the JSON below:

{
    "update": {
        "<fieldName>": [
            {
                "add": { "accountId": "<accountID of the user to be selected>"}
            }
        ]
    }
}

If you need to copy from another field, you can use the one below instead:

{
    "update": {
        "<fieldName>": [
            {
                "add": { "accountId" : "{{issue.<fieldNameToCopyFrom>.accountId}}"}
            }
        ]
    }
}

To Update the Assignee field with a user from a custom people field replace "add" with "set":

{
    "update": {
        "Assignee": [
            {
                "set": { "accountId" : "{{issue.<fieldNameToCopyFrom>.accountId}}"}
            }
        ]
    }
}

Please have in mind that anything in between <> is a value to be replaced in the examples above.