On this page
Use case
This use case considers having a dedicated release ticket which tracks the release process. We will use this template to automatically generate a Jira version when creating the release ticket.
Configuration
Add the Execute remote action post function to the desired transition or create a new transition.
Create remote action
Select the action to get started. Choose Create a version.
Based on the external Jira instance you can select either Cloud or On-prem template.
Select connection
Choose an existing connection to the current instance or create a new connection.
Customize your action
Setting the parameters
Name
Set it manually using the expression editor as follows:
%{issue.summary}
Project key
Set it manually using the expression editor as follows:
%{issue.project.key}
From the used template, you can retrieve the Project ID and/or the Version ID and save them in any field. For this use case we will save the Version ID in the description field.
Optionally, you can use the storing results section to save the response body or parts of it into some field.
Storing results
Select the field to be set.
Choose Description.
Set the value.
Choose Version ID.
Related use cases
Use case No content found.
If you still have questions, feel free to refer to our support team.
