In the Target configuration tab, you can find the settings that let you define the context of the issues that will be created by your recipe.
Target issue context
This section lets you configure where and how your copied issues will be created.
These options restrict the target projects and issues types that will be available to a user triggering the recipe from the Jira issue view.
Use this setting to restrict the projects where the issues can be copied to. Only these projects will be available as a target when the recipe is triggered.
If only one project is selected, this project will be preselected as the recipe target.
If you leave the field empty, all projects will be available as a possible target when the recipe is triggered.
You can also select the "Same as source issue" option here, which means than the copied issue will be created in the same project as the source issue.
Use this setting to restrict the types of issues that the issue created by your recipe can have. Only these issue types will be available to the end-user when the recipe is triggered.
If only one issue type is selected, it will be preselected automatically.
If you leave the field empty, all issue type will be available to the end-user when the recipe is triggered.
You can also select the "Same as source issue" option here, which means than the copied issue will have the same issue type as the source issue.
If only one project and one issue type are selected in this section, the execution of the recipe will be shorter. Indeed, the end-user will not have to decide manually which project and issue type to target when triggering the recipe, and the issue creation dialog will be opened immediately.
Recipes can be used in a workflow post-function only if one project and one issue type have been selected here.
This section lets you configure how the created issue can be monitored by the user who triggers the recipe.
Create link to source issue
Use this setting to select the type of link that will be created between the original issue and its copy.
All the link types available in the "Issue linking" configuration of your Jira instance are listed here.
As its name indicated, the link type "is Epic of" will only work if the source issue of the recipe is an Epic. If the source has any other issue type, no link will be created.
In the same way, the link type "has parent" will only work if the Cloud instance has the add-on Advanced Roadmaps (this add-on is available on Jira Premium instances). If this is not the case, no link will be created.
Here you can select which users to add as Watchers of the new issue created by the recipe among:
- the Reporter of the original issue
- the Assignee of the original issue
- all the Watchers of the original issue
- the Current user who triggers the recipe
Display in customer portal
If this option is enabled, issues created with this recipe from a Jira Service Management ticket will be displayed in the "request view" of the Customer portal, along with their issue type and status.
Only users with the "Browse project" permission on the related issues will be able to see them in the Customer portal panel.