You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

On this page

Use case

For this use case we will consider having a bunch of tickets under an epic in one project and we want to organize them applying components. We will use this template for creating a component to group UI related issues. Then we will use the Update issue post function for setting the component to the issues under the epic.

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 component.

Based on the 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


The values used below are created for the example only. Please provide real input from your instance for making the use case realistic.

Name

Set it manually using the expression editor as follows:

UI design

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 Component id and save them in any field.

Optionally, you can use the storing results section to save the response body or parts of it into some field.

Configure Update issue postfunction

This post function runs syncronisly in Jira on-prem, but not in Jira Cloud. Therefore, in Cloud this step could run before the configured Execute remote action post function!

Setting the parameters


The values used below are created for the example only. Please provide real input from your instance for making the use case realistic.

Target issue

Choose Issues under epic.

Fields

Choose Component.

Set it manually using the expression editor as follows:

UI design




Related use cases


If you still have questions, feel free to refer to our support team.