FAQs

Make sure you have configured the post function on the issue type associated with the Trigger

This can happen when there are multiple screen schemes. Ensure the custom fields are available on both create and edit schemes. https://support.atlassian.com/jira-cloud-administration/docs/manage-screen-schemes/

The Configure option does not list some fields like Linked issues. To add such fields, click on Configure and then click on the link next to the text “To add more fields, or configure field tabs for this screen, go to <link here>” Here you can add the Linked Issues field to the screen.

This is to prevent a potential “infinite loop” which can happen if you have the same project/issue-type combination for Trigger and one of the Tasks in your Flow.

The app looks for previously created Trigger issues with employee ID. If an issue is found, then it is deemed to be duplicate and new ones are not created. A message is logged in Job Logs. Note that the first line in the Mapping Configuration of Trigger configuration is the field used as the ID.

Add "atlassian-addons-admin" group and “atlassian-addons-project-access” role to Create Issues, Edit Issues and Browse Projects permissions.

Make sure the custom field is available both on Create and Edit screens. To confirm, you can run “Find your field” from your issue and select the custom field. Make sure a green check appears next to “Field Screen”