Get started

Use case library

JWT expression editor

JWT expression parser functions

JWT workflow functions

JWT remote actions

JWT automation rules

JWT calculated fields

JWT calendars

JWT properties

JWT JQL functions

Cloud migration hub

Additional product info

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

Compare with Current View Page History

« Previous Version 6 Next »

JWT offers the Execute remote action post function to execute predefined or custom actions not only locally on the current Jira environment, but also on any other web services.

Configuration

The post function offers two types of configuration. In the default view you can choose between predefined and directly usable action templates. In the expert mode, actions can be freely defined and configured.

The wizard is the default configuration view of the Execute remote post function. It was built to enable an easy and efficient configuration of common use cases. For those use cases, action templates are shipped with the app, which can be configured in a three-step approach.

Select action

At the very beginning, you need to choose an action template that suits your purpose. You can filter those templates by the target service and search across all provided ones. After selecting one, click next to get to the next step. 

Select connection

After selecting an action template, you need to choose the remote service, the action shall get executed against. If you have selected an action template that fits to your current plattform, you can select next to your custom connection, the current instance additionally.

If you cannot find a connection that fit for you can easily configure a new one.

//EXCERPT?

After selecting one, click next to get to the next step. 

Customize your action

In the last step, you can finish your configuration by setting all the required action template parameters using the set value link next to the parameter name. Some templates have optional parameters that can be chosen using the "Add parameter" action.

Each parameter can be set either by selecting a Jira field that contains an according value or by setting a custom value using the "set value manually option" and passing a parser expression.

Besides setting the actions parameter, you can also configure fields to be updated after the action has been executed. If provided in the action template, you can set a field using a dedicated part of the remote service's response. In every case, you can store the complete response and the status code of the remote service after executing the action.

After setting the actions parameter and optionally storing the service response, you can click "Add" to store the post function in your transistion.

You can switch at any time to the Expert mode, where the configuration so far is taken over, using the Expert mode button on the top. Be aware that once you change anything in the expert mode, you cannot switch back again.


Action

The mode parameter defines how many issues you want to create. The following modes are available:

OptionDescription




Connection

The mode parameter defines how many issues you want to create. The following modes are available:

OptionDescription




Parameter

The mode parameter defines how many issues you want to create. The following modes are available:

OptionDescription




Fields
OptionDescription
AutomaticThis option is only available for the field Assignee.
Selected valueSelect a specific value from the dropdown list.
Copy field value from current issueCopy the value from a field in the current issue. Select the field you want to copy the value from.
Copy field value from epic issueCopy the value from the related Epic issue. Select the field you want to copy the value from.
Copy field value from seed issue

Copy the value from a seed issue. This option is only available if multiple issues were selected and JQL mode or Issue list mode was used to set the value).

Copy field value from parent of new issueThis option is only available if you create a sub-task under a new parent. Only available if the issue to be created is a sub-task.
Set field value manually (parser expression)

Select the field to copy from using an expression. 

Learn more about the possibilities of the JWT expression editor.

Additional options

The only available additional option is Store issue keys.

If this option is checked, all issue keys from the issue(s) to be created will be stored in the field temporary text 3 as a comma separated list. 

Conditional execution

You can optionally specify a logical expression to define the circumstances (or conditions) under which the post function should be executed.

The result of the logical expression must return a boolean value of either:

  • true → the post function will be executed
  • false → the post function will not be executed

Using the conditional operator, even complex or multi-layered conditions can be constructed.

Make sure to learn more about defining logical expressions and browse through the various examples here: Logical mode

Run as

Select which user will be used to execute this post function. By default this parameter is set to the current user. You can also use field codes to run the function as a dynamic user (e.g. current assignee).

Make sure that the user running the post function has all the relevant permissions to perform the actions defined in the configuration (e.g. "Update Issues")!

If you want to keep track the actions being performed automatically, we suggest to create a dedicated JWT account, granted all relevant permissions, and use it in the Run as parameter to identify which changes have been made with JWT.


Use cases and examples

Use case
No content found.

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