Rule action to create a new project version, and optionally link execution related issues to it via the fixVersions field.
Start typing the name of the project where the issue should be created in, and the options matching your text will appear.
Provide the name of the new version.
Optionally provide the description for the new version.
Optionally provide the start date, in format yyyy-MM-dd, for the new version.
Optionally provide the release date, in format yyyy-MM-dd, for the new version.
Optionally select whether the new version should be marked as released.
Select the selection method used to select the issues to add the comment on.
Linked to Build
Select this method to select all the issues that are linked to the build that was synchronized. Refer to the Data Synchronization documentation on how builds are linked to issues.
This method is only available in combination with the Build Synchronized event.
Linked to Job
Select this method to select all the issues that are linked to the job that was synchronized (when using the Job Synchronized event) or the job of the build that was synchronized (when using the Build Synchronized event). Refer to the Data Synchronization documentation on how builds are linked to issues.
Select this method if you want to limit issue selection to specific attributes of the trigger event or even a static value.
When selecting this method you must also specify the expression used to search for issues to transition. For instance, if you only want
to select issues that are mentioned in the job description, then you can use this expression
[[build.job.description]]. You can also combine attributes, e.g.
[[job.displayName]] [[job.description]], or even attributes with static
text, DEV-1, DEV-2,
[[build.description]]. See Expression Values for details on the attributes
that are available.
Select this method if you don’t want to select any issues for the action. Can be useful for instance when using the Create Version action and just want the version without updating any issues.