To add a step to an newly created single issue operation, click Add Step next to the operation in the "Operations" dialog.

The "Add Step" dialog is displayed.

The following actions are available for single issue operations:

and:

• Iterate over issues or other items

Confluence actions

Create new page

Creates a Confluence page for the current issue from a template.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Template Selection: Select how the template is selected. 
  The following options are available:

  • Predefined template: Select the template that should be used from the "Template" drop-down menu. You can create new templates on the "Manage Templates" page.

  • Let the user select the template: The user will be prompted to select the template. You can select an existing user input or let the Issue Publisher create a new user input.

• Parent Selection: Select how the parent page/content is selected.
  The following options are available:

  • Let the user select the content: The user will be prompted to select the parent page/content. You can select an existing user input or let the Issue Publisher create a new user input.

  • Content of previous step: The page/content of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined content: Select the target server from the "Server" drop-down menu and enter the page/content ID in the "Parent Content" text box. Variables will be replaced.

  • No parent content: Select the target server from the "Server" drop-down menu and enter the space key in the "Space" text box.

• Existing Page: Select what to do when a page with the same title exists already in the space. Possible options are throwing an error (Fail), skipping creating the page (Skip), updating the existing page in-place (Update in-place) or updating the page and moving it under the selected parent page (Update and move).

• Create Link: Select if a link to the new page should be added to the Jira issue. If there is already a page with the same title and you selected an option other than "Fail" under "Existing Page", the link will point to the existing page.

• Save ID: Select weather the ID of the new page should be saved in a custom field.
  If you select "Yes", a drop-down menu "Field to Save ID" is displayed. If there is already a page with the same title and you selected an option other than "Fail" under "Existing Page", the ID of the existing page is saved.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Create new blog post

Creates a Confluence blog post for the current issue from a template.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Template Selection: Select how the template is selected. 
  The following options are available:

  • Predefined template: Select the template that should be used from the "Template" drop-down menu. You can create new templates on the "Manage Templates" page.

  • Let the user select the template: The user will be prompted to select the template. You can select an existing user input or let the Issue Publisher create a new user input.

• Server: Select the target server.

• Space: Enter the space key. Variables will be replaced.

• Create Link: Select if a link to the new blog post should be added to the Jira issue.

• Save ID: Select weather the ID of the new blog post should be saved in a custom field.
  If you select "Yes", a drop-down menu "Field to Save ID" is displayed.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one. 

Create new folder

Creates a new Confluence folder in the page tree for the current issue.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Title: Enter the title of the folder. Variables will be replaced.

• Parent Selection: Select how the parent page/content is selected.
  The following options are available:

  • Let the user select the content: The user will be prompted to select the parent page/content. You can select an existing user input or let the Issue Publisher create a new user input.

  • Content of previous step: The page/content of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined content: Select the target server from the "Server" drop-down menu and enter the page/content ID in the "Parent Content" text box. Variables will be replaced.

• Create Link: Select if a link to the new folder should be added to the Jira issue.

• Save ID: Select weather the ID of the new folder should be saved in a custom field. If you select "Yes", a drop-down menu "Field to Save ID" is displayed.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one. 

Update (overwrite) existing page

Updates respectively overwrites a Confluence page for the current issue from a template.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Template Selection: Select how the template is selected. 
  The following options are available:

  • Predefined template: Select the template that should be used from the "Template" drop-down menu. You can create new templates on the "Manage Templates" page.

  • Let the user select the template: The user will be prompted to select the template. You can select an existing user input or let the Issue Publisher create a new user input.

• Page Owner: Optionally enter the account ID of a new page owner. Variables will be replaced.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one. 

Update field value macros on page

Updates the values of the Jira Field Value macros on the current issue's Confluence page.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Page Title: Enter a new page title. Variables will be replaced. If this is left empty the current page title will be kept.

• Page Owner: Optionally enter the account ID of a new page owner. Variables will be replaced.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one. 

Update labels on page

Sets labels on a Confluence page. Existing labels are removed.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Labels: Enter the labels that should be set. Multiple labels can be separated by blank spaces. Variables will be replaced.

  To keep existing labels, add $currentPage.labels.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Move Page

Moves a Confluence page under another parent page/content.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Parent Selection: Select how the parent page/content is selected.
  The following options are available:

  • Let the user select the content: The user will be prompted to select the parent page/content. You can select an existing user input or let the Issue Publisher create a new user input.

  • Content of previous step: The page/content of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined content: Select the target server from the "Server" drop-down menu and enter the page/content ID in the "Parent Content" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Create link to page

Creates a link from the Jira issue to an existing Confluence page.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Copy attachments to page

Copies the attachments of the current Jira issue and/or the files from the operation store to a Confluence page.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Attachments: Select this option to copy the attachments from the current issue

• Exclude Old Attachments: Select if want to exclude older versions of attachments with the same name from copying.

• Name Filter: Optionally enter a regular expression to filter the attachments by their name. 

• Size Filter: Optionally enter minimum and/or maximum values (in byte) to filter the attachments by their size. Values smaller than 1 are ignored. 

• Date Filter: Optionally enter minimum and/or maximum dates to filter the attachments by their date. You can use any format that works in a JQL (but no functions), e.g. "-2w" or "2020-03-31 18:00". Invalid values are ignored.

• Files From Operation Store: Select this option to copy files from the operation storage to a Confluence page.

• Remove Files From Operation Storage: Select if the files should be removed from the operation storage afterwards (only available if "Files From Operation Store" is selected)

• Labels: Optionally enter labels that should be set on the attachments. Multiple labels can be separated by blank spaces. Variables will be replaced.

• File Name: Optionally enter a new name for the file(s). Variables will be replaced. Use $fileName to access the current file name.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Move attachments to page

Moves the attachments of the current Jira issue and/or the files from the operation store to a Confluence page.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Attachments: Select this option to move the attachments from the current issue

• Exclude Old Attachments: Select if want to exclude older versions of attachments with the same name from moving

• Name Filter: Optionally enter a regular expression to filter the attachments by their name. 

• Size Filter: Optionally enter minimum and/or maximum values (in byte) to filter the attachments by their size. Values smaller than 1 are ignored. 

• Date Filter: Optionally enter minimum and/or maximum dates to filter the attachments by their date. You can use any format that works in a JQL (but no functions), e.g. "-2w" or "2020-03-31 18:00". Invalid values are ignored.

• Files From Operation Store: Select this option to move files from the operation storage to a Confluence page. The files are removed from the operation store.

• Remove Files From Operation Storage: Select if the files should be removed from the operation storage afterwards (only available if "Files From Operation Store" is selected)

• Labels: Optionally enter labels that should be set on the attachments. Multiple labels can be separated by blank spaces. Variables will be replaced.

• File Name: Optionally enter a new name for the file(s). Variables will be replaced. Use $fileName to access the current file name.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Preview Links: Select if a link from the Jira issue to the preview in Confluence should be created for each moved attachment.
  

  Preview links are supported for files with the extensions jpeg, jpg, png, tiff, psd, wmf, emf, ico, icns, doc, docx, ppt, pptx, xls, xlsx, pdf, mp3, mp4.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Copy attachments from page

Copies the attachments of a Confluence page to the current Jira issue or the operation store.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Labels Filter: Enter labels to filter the attachments. Multiple labels can be separated by blank spaces. An attachment needs to have all entered labels to be transferred. Variables will be replaced.

• File Name: Optionally enter a new name for the file(s). Variables will be replaced. Use $fileName to access the current file name.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Store File: Select whether:

  • to add the file(s) as an attachment to the issue (Save as attachment) or

  • to keep it in the operation storage (Keep in operation storage).

  • In manual synchronous operations you can also let the user download the file(s). 

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Delete attachments from page

Deletes all attachments (or all attachments that contain certain labels) from a Confluence page.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Delete Attachments Permanently: Select to p

  ermanently delete the attachments instead of just putting them in the trash 

• Labels Filter: Enter labels to filter the attachments. Multiple labels can be separated by blank spaces. An attachment needs to have all entered labels to be transferred. Variables will be replaced.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Set page restrictions

Set page restrictions on a Confluence page. Any existing restrictions will be replaced.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• View Users: Enter the users that should be able to view the page.

• View Groups: Enter the groups that should be able to view the page.

• Edit Users: Enter the users that should be able to edit the page. For connections using an application link, the executing user is added automatically. For custom connections, the user who makes the call must be added here.

• Edit Groups: Enter the groups that should be able to edit the page. 

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one. 

Add page restrictions

Add page restrictions to a Confluence page. Any existing restrictions will be kept.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• View Users: Enter the users that should be able to view the page.

• View Groups: Enter the groups that should be able to view the page.

• Edit Users: Enter the users that should be able to edit the page. For connections using an application link, the executing user is added automatically. For custom connections, the user who makes the call must be added here.

• Edit Groups: Enter the groups that should be able to edit the page. 

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one. 

Set page property

Sets the property of a page. To delete an existing page property use an empty JSON value.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Key: Enter the key. Variables will be replaced.

• JSON Value:

  Enter the JSON value. Use double quotes for a string, e.g. "my value". Variables will be replaced.

• Page Selection: Select how the page is selected.
  The following options are available:

  • Let the user select the page: The user will be prompted to select a page. You can select an existing user input or let the Issue Publisher create a new user input.

  • Page of previous step: The page of the previous step in the operation is used. (This option is only available if this is not the first step.)

  • Predefined page: Select the target server from the "Server" drop-down menu and enter the page ID in the "Page" text box. Variables will be replaced.

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.

Jira actions

Set field value

Sets the value of a custom field on the current issue. A template for the field value can be defined.

Enter the following information:

• Name: Enter a name for this step. If left empty, the name of the action will be used as label.

• Template: Enter a template that is used to set the field value. Variables will be replaced.

• Target Field: Select the custom field that should be updated.

• Variable Target Field: Enter the name or ID of the target field you want to update by the step. The chosen field will take precedence over the above selected Target field. Variables will be replaced.

• Send Event: Click the checkbox to activate it and send an issue updated event other apps can react to. 

• Error Handling: Select whether to fail the operation in case of an error within this step (Fail) or to ignore them (Ignore). The default should be Fail, especially if the next step depends on this one.