Create Jira Issues from CSV file and Notify in Slack

 

In this automation, Jira and Slack are integrated to get notifications about the issues raised on Jira for errors that occurred in a CSV file at the FTP server based on the priorities.

 

For more details please visit: Create Jira Issues from CSV file and Notify in Slack Automation Guide

How it works

  • Get the Jira issues from the CSV file

  • Read it and send it to Slack based on the priority by using the conditions.

  • You can put the conditions based on the priority requirements, such as highest, high and medium.

  • Save the configuration and you will get the notification of Jira issues based on the priorities.

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

Steps to configure

  1. Click on the get CSV file, and the below form will appear on the screen. A CSV file is a commonly used file extension when it comes to spreadsheets. Even software programs that don't look and feel like a spreadsheet application will frequently offer a CSV as an output file for downloading a data set, such as a report of results, actions, or contacts.

  2. Add the connection as “Sapper FTP”. For more information please visit https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585

  3. Fill in how do you want to read a file field. You can choose “using the file name” or “using the regular expression”.

  4. By using the file name you can choose a file for reading. On the other hand, using regular expressions is particularly useful for defining filters. Regular expressions contain a series of characters that define a pattern of text to be matched to make a filter more specialized or general.

  5. Now, click on the read CSV file, add “using the file” in the CSV input type. A CSV input type is a simple text file in which information is separated by commas. You can add the file in a formula format.

  6. Add the file in the output meta field, by browsing the file. The output meta is the type resolution for the result of a component. Each component can provide either static or dynamic metadata for the payload and attributes, isolated from each other.

  7. Add a loop. It’s helps the automation to run continuously. It’s like repeating the same things again and again as per the requirements.

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

  9. Click on Jira, and the below form will appear on the screen.

  10. Now provide the connection details, add Jira in the connection field. For more details please visit https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585

  11. In the action field add the “create issues”. Actions are the performer of your automation. They allow you to automate tasks and make changes within your site. By opting for action you can perform many tasks, such as editing an issue, sending a notification, or creating sub-tasks.

  12. Now, click on field. This section involves track attributes surrounding each Jira issue type.

  13. From the field input add a project key. A project key is a unique identifier of your project or automation. It’s become the prefix for tasks created within that project. It can be a combination of text or formulas based on the requirements.

  14. Now, provide a summary from the project key field. A summary is a short description of the core idea of automation.

  15. Add a description from the project key input. A description is a statement that gives details about automation. It can be a combination of text and formulas as per the requirement.

  16. Add an issue name in the issue type field. Issue types distinguish different types of work in a unique way, 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.

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

  18. Now, click on Slack from the loop, and the below form will appear on the screen. This form is used for adding required conditions based on the priorities.

  19. Now, you can add “Slack connection” in the connection section. For more details please visit https://sappersoftware.atlassian.net/wiki/spaces/SD/pages/63602585

  20. Fill the action field with “send message to channel”.

  21. Add the channel name, a channel's name lets people know what it's used for. If the purpose of a channel changes at any point in time, it can be renamed. Now, you can add the condition priority such as, “highest”, “high” and “medium”.

  22. Now add a message as per the requirement. It can be a combination of text and formula.

  23. Now click on the conditions to identify the condition expression. A conditional expression has a general form. Where expr1 is an expression that yields a true or false result. If the result is true, the value of the conditional expression is set to expr2. If the result is false, the value of the conditional expression is set to expr3.

  24. The condition expression can be provided in the below-mentioned format. The format can be viewed by clicking on the conditions.

  25. Now, add the aggregator for completing the automation. An API aggregator is an API on top of several different APIs that provide a single point of implementation and deliver a unique and standardized API regardless of what APIs or services it integrates with.

  26. Now, click on save to save the configuration to complete the automation execution.



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