Jira Service Management Actions¶
Actions are the operations (or API operations) that you can perform on Jira Service Management.
You can simply drag and drop attributes from input trigger or derived values using formulas or desired constant that you may wish to map with Jira Service Management.
All the actions that you see below automate the flows you execute manually on Jira Service Management.
Following are the actions for Jira Service Management on Connect iPaaS¶
- Add Existing User to Group
- Create Entity
- Create User
- Delete Entity
- Remove User from Group
- Update Entity
Connect iPaaS supports the following entities for Action on Jira Service Management:
- Request: A request is simply a unit of work within Jira that will be traced through a workflow, from creation to completion.
- Project: A project is a collection of issues that are held in common by purpose or context.
- User: A user is anyone who can log in to the system.
- Comment: It is used to tell what work has been done on an issue or to give any information.
- Worklog: It used to keep track of work that has been done.
- Group: It is a convenient way to manage a collection of users.
- Dashboard: It is the main display we can see while log in to the Jira.
- Issue Link: Issue linking allows you to create an association between two existing issues on either the same or different Jira servers.
Learn here about all the entities on Jira Service Management along with their attributes.
Add Existing User to Group¶
To Set up this action: Select the user and group from the dropdown. You can either type in the values of these attributes or can fill the values using data mapping and transformation or you can use the excel style functions for complex transformations. You can also use the evaluate functionality for deferring selecting from a list to the time when the flow execution is in progress.
In Figure 2 below, whenever a new user is added in Active Directory, the selected User
will be added to the selected Group
of the Jira Service Management account.
Create Entity¶
This action creates a new entity in the Jira Service Management. While setting up this action, you have to select the entity that you want to create in the Jira Service Management account.
After selecting the entity, you will see the attributes that are needed to create that entity. You can either type in the values of these attributes or can fill the values using data mapping and transformation. You can also use the excel style functions for constructing value of attributes using complex transformations. You can also use the evaluate functionality for deferring making a selection from a list to the time when the flow execution is in progress.
In Figure 3 below, whenever a Company is created in Hubspot, a Dashboard
will be created in Jira Service Management. The attributes of the Dashboard are selected based on the attributes from HubSpot. The Dashboard Name
of the dashboard is the same as the Name
attribute and the Description
of the dashboard is equals to the Description
attribute from HubSpot.
Create User¶
This action creates a new user in Jira Service Management.
After selecting the action, you will see the attributes that are needed to create the user. You can either type in the values of these attributes or can fill the values using data mapping and transformation or you can use the excel style functions for complex transformations. You can also use the evaluate functionality for deferring making a selection from a list to the time when the flow execution is in progress.
In Figure 4 below, whenever a new member is added in Active Directory, the specified User
will be created in the Jira Service Management.
Delete Entity¶
This action deletes an entity from Jira Service Management. While setting up this action, you have to select the entities that you want to delete.
After selecting the entity, define the selection criteria for the items that you want to be deleted. You can construct a logic for conditions using AND, OR operators. You can also use the data from incoming trigger application data for creating the selection condition.
In figure 5 below, when a record is updated in Service Now, the issue whose Summary
contains Sys Id
attribute from Service Now will be deleted.
Remove User from Group¶
This action removes a user from an existing group. While setting up this action, you have to select the group and then the user whom you want to remove from the selected group.
You can either type in the values of these attributes or can fill the values using data mapping and transformation or you can use the excel style functions for complex transformations. You can also use the evaluate functionality for deferring making a selection from a list to the time when the flow execution is in progress.
In Figure 6 below, whenever a member is removed from Active Directory, a User
will be removed from the group of Jira Service Management account.
Update Entity¶
This action updates an entity in Jira Service Management. While setting up this action, you can define the criteria to select the entities which will be updated. Further, you can select the attributes which will be updated.
After selecting the entity, define the selection criteria for the items that you want to be updated. You can construct a logic for condition using AND, OR operators. You can also use the data from incoming trigger application data for creating the selection condition.
Next, you can, select the attributes that you want to update. You can either type in the values of these attributes or can fill the values using Built-in Data Mapping or you can use the excel style functions for complex transformations. You can also use the evaluate functionality to make a selection when the flow execution is in progress.
In Figure 7 below, whenever a Deal is updated in HubSpot, Request
whose Description
contains Deal Description
attribute from HubSpot Now will be updated in Jira Service Management. The Priority
and Assignee
of the Request
will be updated. Refer to the screenshot below.