Create Jira Issues from Salesforce Cases

In this automation, Salesforce and Jira are integrated to create Jira issues from the mentioned Salesforce cases.

For more information visit: Create Jira Issues from Salesforce Cases Automation guide

How it works

  • Get cases from Salesforce

  • Add a loop, and get cases by id from Salesforce.

  • Create a Jira issue, by providing the project key, summary, description, issue type, and priority.

  • Save the configuration for further execution.

Following are the steps that will help to configure the automation:

Steps to configure

  1. Click on Salesforce, and the below form will appear on the screen.

  2. Create an OAuth2.0 Salesforce connection using https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585 template or use the pre-defined connection.

  3. Now, provide the action as a “get cases” and save it for further process. An actions put your app front and center in Slack. Nestled under the ellipsis menu, apps with actions show up on every Slack message in a workspace.

  4. Add a loop, and the below form appears on the screen. Loop helps the automation to runs continuously. It’s like repeating same things again and again as per the requirements.

  5. Provide the input array. An input array is a group (or collection) of same data types. Here the input array will be “response” and status is “recent items”. Now, save it for further process.

  6. Click on Salesforce, and add the connection name and action from the below form.

  7. In the connection section add “Salesforce”, and select action as “get case by Id”.

  8. Now, click on Jira, and the below form will appear. In the connection input add “Jira”, mention action as “create issue”.

  9. Click on the field section. A field section is similar to a zone section in that it is a region of text delimited by start and end tags.

  10. Now, from the field section you need to add the project key. A project key is a unique identifier of your project.

  11. Provide a summary and description. A summary is a short description of the core idea of the automation. On the other hand, description is a statement that gives details about the automation. It can be a combination of text and formula’s as per the requirement.

  12. Now provide the issue type. Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your team's work across your Jira site. From the issue type, you need to add a name based on the specific issue.

  13. Add a priority. A priority field explain about the relative importance of an issue in relation to other issues for the team. The priority can be “high”, “medium”, and “low” based on your requirements. These priority are needed to mention in the name input field from the priority section.

  14. Now save the configuration and execute the automation.

 

For any kind of assistance, kindly get in touch with us at support@sapper.ai