Automation actions
This page describes all Automation actions provided by this plugin.
If you have an idea or need for some other action, be sure to contact us here and we will make it happen at no additional cost to you!
Create new Jira Space
User who creates the connection must have Administer Jira global permission.
This action allows you to automate creating new Jira Spaces. This is an excellent automation to combine with JSM portal where users can order a new Space for their tasks. Automation can be set up to use configuration from existing Space (Space can be specified by the automation configuration or by the user from the request), combine specific configuration schemes (again, specified by the automation configuration or selected by the user) or create new configuration.
Following information can be set:
Field type | Pre-defined value | Smart value | Copy from Space |
|---|---|---|---|
Space name | Specified value | Allowed | N/A |
Space key | Specified value | Allowed | N/A |
Space type | Select from:
| Allowed Value must be one of:
| Allowed |
Default assignee | Select from:
| Allowed Value must be one of:
| Allowed |
Space lead | Select specific User | Allowed Value must be specific accountId. | Allowed |
Work type scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Workflow scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Field Configuration scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Work type screen scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Permission scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Work security scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Priority scheme | Select from:
| Allowed Value must be specific scheme ID. | Allowed |
Space category | Select from:
| Allowed Value must be specific category ID. | Allowed |
Space description | Specified value | Allowed | N/A |
Space URL | Specified value | Allowed | N/A |
Add Jira Space Role Actors
User who creates the connection must have Administer Jira global permission or Administer Spaces space permission.
Useful for automating adding users/groups to specific role in specific Jira Space. Combine with JSM requests and approval workflows.
Space Key or ID is provided via smart value.
Role is specified in automation configuration.
Comma-separated list of account IDs, group IDs and/or group names can be provided via smart values. These will be added to specified role.
Change Jira Space Configuration
Administer Jira global permission is only needed when changing the schemes or space key. Otherwise you will only need Administer Spaces space permission.
Useful for updating some Space configuration, such as Space Lead. Combine with JSM requests and approval workflows to allow automating space management.
Space Key or ID must be provided via smart value.
Following fields can be updated:
Space name
Space key
Space lead
Default assignee (space lead or unassigned)
Space description
Space URL
Space category
Notification scheme (ID must be provided)
Permission scheme (ID must be provided)
Work security scheme (ID must be provided)
Archive Jira Space
User who creates the connection must have Administer Jira global permission.
Simple automation that allows archiving Jira Space. Space Key or ID must be provided via smart value.
Delete Jira Space
User who creates the connection must have Administer Jira global permission.
Simple automation that allows deleting Jira Space. Space Key or ID must be provided via smart value.
When configuring the automation, it is possible to select to skip moving space to trash before permanently deleting it. This is disabled by default, meaning that by default the space is first moved to trash where it will be automatically deleted by Jira after 60 days.
Archive Jira work item(s)
User who creates the connection must have Administer Jira global permission.
Simple automation that allows archiving Jira work items. Work items must be provided by comma-separated list of IDs or Keys. Smart values such as {{#lookupIssues}}{{key}},{{/}} are supported. Good idea to combine this action with scheduled trigger and “Lookup work items” action to archive work items that match specific condition.