{"id":5874,"date":"2022-12-01T08:00:58","date_gmt":"2022-12-01T08:00:58","guid":{"rendered":"https:\/\/www.process.st\/help\/docs\/jira\/"},"modified":"2025-10-01T08:07:00","modified_gmt":"2025-10-01T08:07:00","slug":"jira","status":"publish","type":"ht_kb","link":"https:\/\/www.process.st\/help\/docs\/jira\/","title":{"rendered":"Jira + Process Street Integration"},"content":{"rendered":"<p><img decoding=\"async\" class=\"alignnone size-full wp-image-9553\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Integrate-Jira-with-Process-Street-04.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Jira helps teams plan, assign, track, report, and manage their work together in teams or in cross-departments. You can integrate <a href=\"https:\/\/www.atlassian.com\/software\/jira\">Jira<\/a> with <a href=\"https:\/\/www.process.st\/\">Process Street<\/a>\u00a0to make your <a href=\"https:\/\/www.process.st\/help\/docs\/what-is-a-workflow\/\">workflows<\/a> super powerful and automate your work via <a href=\"https:\/\/www.process.st\/help\/docs\/webhooks\/\">Webhooks<\/a> or <a href=\"https:\/\/www.process.st\/help\/docs\/jira\/#connect-jira-to-process-street-via-zapier\">Zapier<\/a>.<\/p>\n<p><em><strong>Users<\/strong>: <strong>In Jira<\/strong>, you&#8217;ll need\u00a0<\/em><span style=\"box-sizing: border-box; margin: 0px; padding: 0px;\"><em>a user account with read\/write access to the project you&#8217;d like to automate or be a global admin.<\/em><em><strong> In Process Street,<\/strong><\/em><\/span><em>\u00a0you&#8217;ll need to be an admin to create webhooks.\u00a0<\/em><\/p>\n<h2>Connect Jira with Process Street via Webhook<\/h2>\n<p>A Webhook integration\u00a0can bring information from Jira that would trigger a new <a href=\"https:\/\/www.process.st\/help\/docs\/running-workflows\/\">workflow run<\/a> in your Process Street account.\u00a0<em>Webhooks are\u00a0automated messages or payloads sent from apps as a trigger to cause an action in a receiving app.<\/em><\/p>\n<p>In this example, we will create a Webhook that runs the Customer Support Tickets workflow when a new issue is created in Jira.<\/p>\n<h3>Process overview:<\/h3>\n<ul>\n<li>We will create a Customer Support Tickets workflow in Process Street<\/li>\n<li>We will create a few issues in our\u00a0Jira\u00a0organization. When a new\u00a0issue\u00a0is created, this will act as our trigger<\/li>\n<li>We will create a webhook that listens for our desired trigger in\u00a0Jira\u00a0and runs the Customer\u00a0Support Tickets\u00a0workflow in Process Street<\/li>\n<\/ul>\n<p>Now, let\u2019s jump into the integration.<\/p>\n<h3>1. Preparations in Process Street<\/h3>\n<p>First, create a <a href=\"https:\/\/www.process.st\/help\/docs\/workflows\/\" target=\"_blank\" rel=\"noopener\">Workflow\u00a0<\/a>in Process Street and ensure to add <a href=\"https:\/\/www.process.st\/help\/docs\/form-fields\/\" target=\"_blank\" rel=\"noopener\">form fields<\/a> that are relevant to the data fields in\u00a0Jira. This will help you to map the relevant information from\u00a0Jira\u00a0to Process Street.<\/p>\n<p>This information is stored in\u00a0Jira\u00a0when an\u00a0issue\u00a0is created. So, we need to create relevant form fields in our workflow to push that information through to Process Street.\u00a0For our example, these form fields should include the issue ID (number field), issue\u00a0summary, user who created the issue (short text fields), issue description (long text field), and so on.<\/p>\n<p>This will mean that whoever is working on the support ticket won&#8217;t have to look up information in\u00a0Jira, but can instead see all the details in Process Street.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14437\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-workflow.png\" alt=\"\" width=\"100%\" \/><\/p>\n<h3>2. Preparations in Jira<\/h3>\n<p>Log into your\u00a0Jira\u00a0account or <a href=\"https:\/\/www.zendesk.com\/in\/register\/#step-1\">create a new account<\/a>. Since we want to trigger a new run in Process Street when a new\u00a0issue\u00a0is created, we will be working in our project dashboard in\u00a0Jira. If you don&#8217;t have any project yet, you can start by creating that first.<\/p>\n<p>To create a new\u00a0issue, click<strong>\u00a0Create\u00a0<\/strong>in the top centre of your screen and add the details like\u00a0issue\u00a0summary, description, tags, and other details you may want.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14438\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-create-issue.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Note: You want to ensure that the form fields you have in your workflow match the fields you have in\u00a0Jira. If you&#8217;d like to add more details to your Jira ticket, you can click on any existing issue and configure the issue type.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14439\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-custom-fields.gif\" alt=\"\" width=\"100%\" \/><\/p>\n<h3>3. Create a Webhook trigger to run your workflow in Process Street<\/h3>\n<p>To get the webhook URL from Process Street, when you&#8217;re editing your workflow, click the <strong>+ icon<\/strong> above your task list on the left. Here, you can look for\u00a0<strong>Jira<\/strong>\u00a0as a Trigger to Run this workflow.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14440\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-webhook.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>You can name your webhook as the app name or any phrase that helps you identify the Trigger. Then copy your Webhook URL and select your event as <strong>Default<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14441\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/name-webhook.png\" alt=\"\" width=\"100%\" \/><\/p>\n<h3>4. Set up the Webhook Trigger in Jira<\/h3>\n<p>Click on the <strong>settings Cog<\/strong> in the top left corner and go to the <strong>System<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14442\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/system-setting.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Then click on\u00a0<strong>Webhooks\u00a0<\/strong>under Advanced Settings in the left panel. Then click\u00a0+\u00a0<strong>Create webhook<\/strong> and fill in all the fields as shown below.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14443\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-webhooks.gif\" alt=\"\" width=\"100%\" \/><\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14445\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-create-webhook.gif\" alt=\"\" width=\"100%\" \/><\/p>\n<p><strong>Note:<\/strong>\u00a0Since Process Street needs to receive the JSON body, ensure to leave the &#8220;Exclude body&#8221; box <strong>unchecked<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14444\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/json.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p><em>If you&#8217;re looking for more help on how to set up your webhook in\u00a0Jira, you can refer to their <a href=\"https:\/\/developer.atlassian.com\/server\/jira\/platform\/webhooks\/\">help doc<\/a> here.<\/em><\/p>\n<h3>5. Finish the setup in Process Street<\/h3>\n<p>Now come back to Process Street and test your trigger. Your payload should return as a success but if it doesn&#8217;t, you might want to go back to\u00a0Jira\u00a0and create a new\u00a0issue.<\/p>\n<p>When your test returns successful, you can proceed to map your fields from your issue&#8217;s properties to your Process Street form fields.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14446\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-field-mapping.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Lastly, turn your webhook <strong>On<\/strong> and <strong>Save<\/strong> it. Then <strong>Publish<\/strong> your workflow and you&#8217;re all set!<\/p>\n<p>As an extra step, you can go to\u00a0Jira, create a new\u00a0issue\u00a0then come back to Process Street in the Reports Dashboard to confirm a new workflow is run.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-14447\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/jira-run-via-webhook.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Lastly, turn your webhook <strong>On<\/strong> and <strong>Save<\/strong> it. Then <strong>Publish<\/strong> your workflow and you&#8217;re all set!<\/p>\n<p>As an extra step, you can go to\u00a0Jira, update a deal stage to Closed Won then come back to Process Street in the Reports Dashboard to confirm a new workflow is run.<\/p>\n<h2>Connect Jira to Process Street via Zapier<\/h2>\n<p><a href=\"https:\/\/zapier.com\/\">Zapier<\/a> connects over 1,000 apps together. It&#8217;s an &#8220;if this, then that&#8221; tool, meaning that once a trigger has occurred, an action will then take place. This helps to save you time and effort by <a href=\"https:\/\/www.process.st\/business-process-automation-guide\/\" target=\"_blank\" rel=\"noopener\">automating processes<\/a>.<\/p>\n<p>In this example, we will look at how\u00a0Jira\u00a0can be integrated with Process Street so that when a new company name is added to\u00a0Jira, a new client onboarding workflow is run.<\/p>\n<p>You can integrate Process Street with Jira, using Process Street\u2019s <a href=\"https:\/\/www.process.st\/help\/docs\/automations\/\">Automations<\/a>.<\/p>\n<p>This integration allows you to create an issue in Jira automatically, when a task is checked, or when a workflow run is completed.<\/p>\n<p><em><strong>Users: In order to create or update Automations, you must be an Administrator or a <a href=\"https:\/\/www.process.st\/help\/docs\/what-is-a-full-member\/\">Builder<\/a>\u00a0with &#8220;edit&#8221; permissions.<\/strong><\/em><\/p>\n<p><iframe loading=\"lazy\" title=\"YouTube video player\" src=\"https:\/\/www.youtube.com\/embed\/OKJCLbLiKlg\" width=\"100%\" height=\"406\" frameborder=\"0\" allowfullscreen=\"allowfullscreen\"><span data-mce-type=\"bookmark\" style=\"display: inline-block; width: 0px; overflow: hidden; line-height: 0;\" class=\"mce_SELRES_start\">\ufeff<\/span><\/iframe><\/p>\n<h2>Example use cases<\/h2>\n<ul>\n<li>You collect information about a technical issue from your support desk. When a specific task is completed, a bug ticket is raised for your engineering team to investigate, and a Jira issue number is attached back into your support workflow run<\/li>\n<li>Your support team submit product feedback from customers through a workflow run and once complete, this sends a new issue to your product team to prioritize and then investigate<\/li>\n<\/ul>\n<h2>How to set up an automation with Jira<\/h2>\n<p>Before you get started you\u2019ll need to have a few things set up in <a href=\"https:\/\/www.atlassian.com\/software\/jira\">Jira Software<\/a>, and in your Process Street workflow.<\/p>\n<h3>Preparations in Jira<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-9966\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-set-up-project.png\" alt=\"\" width=\"100%\" \/><\/p>\n<ol>\n<li>Create or <a href=\"https:\/\/id.atlassian.com\/\">login<\/a> to your Jira account<\/li>\n<li>Create a <a href=\"https:\/\/support.atlassian.com\/jira-cloud-administration\/docs\/create-and-edit-a-project\/\">project<\/a> (or use an existing one)<\/li>\n<li>Consider which issue type you&#8217;re going to use (an epic, a task, a subtask etc.) to map details from Process Street into, and remember your choice for when you&#8217;re building your automation later<\/li>\n<\/ol>\n<h3>Preparations in Process Street<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10356\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-form-fields.png\" alt=\"\" width=\"100%\" \/><\/p>\n<ol>\n<li><a href=\"https:\/\/www.process.st\/\">Login<\/a> to your Process Street account<\/li>\n<li>Create or open the workflow you\u2019d like to use for your automation and start <a href=\"https:\/\/www.process.st\/help\/docs\/editing-templates\/\">editing<\/a> it<\/li>\n<li>Required: Add either a short or long text <a href=\"https:\/\/www.process.st\/help\/docs\/form-fields\/\">form field<\/a> into a task that you will use later for mapping your Jira issue <strong>summary<\/strong>. Give it a name label so it is easy to identify when creating your automation later<\/li>\n<li>Optional: Add a <a href=\"https:\/\/www.process.st\/help\/docs\/form-fields\/\">snippet form field<\/a> into a task that you can use later for mapping your Jira issue <strong>description<\/strong> (example shown above). Give it a name label so it is easy to identify when creating your automation later<\/li>\n<li>Optional: Add another short text <a href=\"https:\/\/www.process.st\/help\/docs\/form-fields\/\">form field<\/a> where you can store your Jira <strong>ticket number or ID<\/strong> once it&#8217;s been created. Give it a name label so it is easy to identify when creating your automation later<\/li>\n<li>Save changes to your workflow<\/li>\n<\/ol>\n<p>Now you\u2019re ready to go ahead and start creating your automation!<\/p>\n<h2>Open your Process Street workflow<\/h2>\n<p>Head to your <a href=\"https:\/\/www.process.st\/help\/docs\/template-dashboard\/\">library<\/a> and open up the workflow you\u2019d like to create an automation for. When viewing the workflow you will see the \u201cAutomations\u201d tab next to the workflow tab, as shown below.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10357\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-find-auto-tab.gif\" alt=\"\" width=\"100%\" \/><\/p>\n<h3>Choose your trigger<\/h3>\n<p>Start by selecting the trigger for your automation from the left side of your screen. This will be the event that will cause the automation to start (like a starting pistol being fired to kick off a race).<\/p>\n<p>For Jira you can choose from these two triggers:<\/p>\n<ol>\n<li><strong>When a task is checked then<\/strong><\/li>\n<li><strong>When a workflow run is complete then<\/strong><\/li>\n<\/ol>\n<p>Click the <strong>+<\/strong> button on your chosen trigger to get started.<\/p>\n<p>Let\u2019s walk through examples for each of these triggers and their respective actions.<\/p>\n<h2>1. When a task is checked<\/h2>\n<p>Select &#8220;<strong>When a task is checked then<\/strong>&#8221; from the left side of your screen.<\/p>\n<h3>Choose a task<\/h3>\n<p>Start by selecting the task in your workflow that will act as your trigger.<\/p>\n<h3>Choose an app<\/h3>\n<p>Next, click the <strong>Jira<\/strong> icon and a small tick will appear to confirm your selection.<\/p>\n<h3>Choose an action<\/h3>\n<p>Select the action \u201c<strong>create issue<\/strong>\u201d.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10358\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-task-checked-set-up.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Putting it all together, in this example, completing the task &#8220;Pass to engineering&#8221; in your customer support workflow run creates a Jira issue for the engineering team to investigate. It also adds a note of the Jira issue number back into the workflow run, so that you can refer back to it later.<\/p>\n<h3>Authentication<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10359\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira.-authorize.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>When you select your chosen action, a pop-up window will appear and you will be prompted to choose an Atlassian account to run your automation through.<\/p>\n<p>If it&#8217;s the first time you are connecting to Jira via Process Street, a pop-up window will appear for you to be able to create a new authentication.<\/p>\n<p><strong>Note:<\/strong> You will need to disable pop-ups blockers to allow you to authorize an app.<\/p>\n<p>When prompted for your Jira Site URL, use the full URL including the URL prefix, e.g. &#8220;https:\/\/[yourdomain].atlassian.net&#8221;.<\/p>\n<p>If you already have an account connected, then you can continue with the one shown, or select another account to add.<\/p>\n<h3>Required: Configure Jira project and issue type<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10361\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-choose-project-issue1.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Choose which <strong>Jira project<\/strong> to create the issue in, and the <strong>issue type<\/strong> you would like to create. Remember the issue type you thought of earlier? This is where you&#8217;ll need to add it. Click &#8220;Next&#8221;.<\/p>\n<h3>Map summary and description fields<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10362\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-map-fields-2.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Required: Map the field from your workflow run, that you would like to pull into your Jira issue <strong>summary<\/strong>. This will be either a short text or a long text <a href=\"https:\/\/www.process.st\/help\/docs\/form-fields\/\">form field<\/a> that you added to your workflow earlier.<\/p>\n<p>Optional: Map the snippet form field from your workflow run, that you would like to pull into your Jira issue <strong>description<\/strong>.<\/p>\n<p>Click &#8220;Next&#8221;.<\/p>\n<h3>Optional: Map data to update in Process Street<\/h3>\n<p>This allows you to push data like the Jira ID number or Jira Key, back into your workflow run for future reference.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10363\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-map-optional-field.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Click \u201cAdd new mapping\u201d to map more fields. When you\u2019re done mapping fields, click \u201cFinish\u201d.<\/p>\n<h3>Activate this automation<\/h3>\n<p>Now you\u2019re ready to turn on your automation. Use one of the toggle switches shown below, to switch it on.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10364\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-activate-ex1.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Now every time your task is checked, an issue will be created in Jira, pre-filled with the data you have mapped from your Process Street workflow run. Your Jira ticket or ID number will also be mapped back into the same workflow run.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10366\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Joira-ticket-mapped-to-workflow-run.gif\" alt=\"\" width=\"100%\" \/><\/p>\n<h2>2. When a workflow run is complete<\/h2>\n<h3>Choose your trigger<\/h3>\n<p>Select &#8220;<strong>When a workflow run is complete then<\/strong>&#8221; from the left side of your screen.<\/p>\n<h3>Choose an app<\/h3>\n<p>Next, click the <strong>Jira<\/strong> icon and a small tick will appear to confirm your selection.<\/p>\n<h3>Choose an action<\/h3>\n<p>Select the action \u201c<strong>create issue<\/strong>\u201d<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10367\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-complete-first-steps.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Putting all this together, in this example, completing a workflow run from your &#8220;Product feedback&#8221; process creates a task for the product department, who triage, prioritize and assign it to one of their team.<\/p>\n<h3>Authentication<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10368\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-auth-ex2.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>When you select your chosen action, a pop-up window will appear and you will be prompted to choose an Atlassian account to run your automation through.<\/p>\n<p>If it&#8217;s the first time you are connecting to Jira via Process Street, a pop-up window will appear for you to be able to create a new authentication.<\/p>\n<p><strong>Note:<\/strong> You will need to disable pop-ups blockers to allow you to authorize an app.<\/p>\n<p>When prompted for your Jira Site URL, use the full URL including the URL prefix, e.g. &#8220;https:\/\/[yourdomain].atlassian.net&#8221;.<\/p>\n<p>If you already have an account connected, then you can continue with the one shown, or select another account to add. Click &#8220;Next&#8221;.<\/p>\n<h3>Required: Configure Jira project and issue type<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10369\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-project-issue-ex2.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Choose which <strong>Jira project<\/strong> to create the issue in, and the <strong>issue type<\/strong> you would like to create. Remember the issue type you thought of earlier? This is where you&#8217;ll need to add it. Click &#8220;Next&#8221;.<\/p>\n<h3>Map summary and description fields<\/h3>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10372\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-feedback.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Required: Map the field from your workflow run, that you would like to pull into your Jira issue <strong>summary<\/strong>. This will be either a short text or a long text <a href=\"https:\/\/www.process.st\/help\/docs\/form-fields\/\">form field<\/a> that you added to your workflow earlier.<\/p>\n<p>Optional: Map the snippet form field from your workflow run, that you would like to pull into your Jira issue <strong>description<\/strong>.<\/p>\n<p>Click &#8220;Finish&#8221;.<\/p>\n<h3>Activate this automation<\/h3>\n<p>Now you\u2019re ready to turn on your automation. Use one of the toggle switches shown below, to switch it on.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10371\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-activate-ex2.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>Now every time you complete a workflow run from this workflow, an issue will be created in Jira in your chosen project, including a summary (and optional description) mapped across from your Process Street workflow run.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10373\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-customer-feedback.gif\" alt=\"\" width=\"100%\" \/><\/p>\n<h2>Advanced<\/h2>\n<p>If you\u2019re looking to create a really robust integration with Jira, you can use a <a href=\"https:\/\/www.process.st\/help\/docs\/checklist-run-link\/\">workflow run link<\/a> that you create inside Salesforce\u2019s <a href=\"https:\/\/help.salesforce.com\/articleView?id=sf.customize_enterprise.htm&amp;type=5\">custom links<\/a> for each of your accounts. You run your workflow run, create an issue in Jira and then a <a href=\"https:\/\/www.process.st\/help\/docs\/slack\/\">Slack automation<\/a> notifies your customer success team in their channel that a new issue has been created.<\/p>\n<hr \/>\n<h3>Edit an automation<\/h3>\n<p>To be able to edit the fields you have mapped in your automation, or change the triggers or actions, you first need to turn off your automation using one of the toggle switches.<\/p>\n<h3>Delete an automation<\/h3>\n<p>To remove an automation from a workflow, you can delete it, but first, you will need to ensure that it has been switched off. Turn the toggle switch to the &#8220;off&#8221; position and then click the trashcan icon in the top right of your view to delete the automation.<\/p>\n<h3>Limitations<\/h3>\n<p>There are no filters, delays, or formulas built into automations at the moment. To be able to utilize these types of functions, you might want to consider using a <a href=\"https:\/\/www.process.st\/help\/docs\/zapier\/\">Zapier integration<\/a>\u00a0instead.<\/p>\n<h3>Request another app<\/h3>\n<p>If you would like to request that we add another app to our automations, you can do that from the help button in the bottom right corner of your screen. Click \u201cSuggestions\u201d and send us your request.<\/p>\n<h3>Troubleshooting<\/h3>\n<p>If your automation stopped running, isn&#8217;t working as expected, or is showing errors, there might be a few reasons for this. Please check the following:<\/p>\n<ul>\n<li>Did you turn the automation on once you set it up? Each automation has a separate &#8220;on\/off&#8221; toggle switch<\/li>\n<li>Did you edit your workflow, change or delete a form field that you were mapping in your automation? If you did, then this may cause your automation to stop running<\/li>\n<li>Did you edit your workflow but not save the changes? You need to have saved any edits to your workflow to have the latest version pull through to your automations<\/li>\n<li>Each time your automation runs you will see a record of success or failure, in your run logs<\/li>\n<\/ul>\n<h3>Run logs<\/h3>\n<p>You can check your automation run logs to see how your automations are running, or check for errors. You will find the automation run logs in two places, on your <strong>workflow<\/strong> or on <strong>workflow runs<\/strong>.<\/p>\n<p>In your <strong>workflow<\/strong> on the automations tab, select an existing automation from the left side of your screen (highlighted in blue below). At the bottom of your page, you will see a list of all of the automation runs for that workflow. If your automation hasn&#8217;t run yet, you&#8217;ll see something similar to the below.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10374\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-workflow-success.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>In a <b> workflow run<\/b>, in the upper right-hand corner of your task list, you\u2019ll see the lightning bolt icon<img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-9446\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/lightning-bolt.png\" alt=\"\" width=\"15\" height=\"16\" \/>. Click the icon to see the run logs for that particular workflow run.<\/p>\n<p>If you have any errors, click the word &#8220;Error&#8221; to expand more information on why your automation didn&#8217;t run.<\/p>\n<p><img decoding=\"async\" class=\"alignnone size-full wp-image-10375\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/Jira-workflow-run-success.png\" alt=\"\" width=\"100%\" \/><\/p>\n<p>The lightning bolt icon will only show up on workflow runs that have automations configured on them. This is an automation&#8217;s idle state.<\/p>\n<p>When an automation is running, you\u2019ll see the bolt change to the <img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-9447\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/recycle-icon.png\" alt=\"\" width=\"17\" height=\"17\" \/> icon.<\/p>\n<p>Once the automation finishes running, you\u2019ll see either <img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-9448\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/tick-icon.png\" alt=\"\" width=\"19\" height=\"19\" \/> for success or <img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-9449\" src=\"https:\/\/www.process.st\/help\/wp-content\/uploads\/2024\/02\/x-icon.png\" alt=\"\" width=\"18\" height=\"18\" \/> for failure. If it\u2019s a failure, you can click on the X to see the run logs and then click on the &#8220;Error&#8221; log for more information.<\/p>\n<p>If you have any questions about using Automations, please reach out to our <a href=\"https:\/\/www.process.st\/help\/docs\/support\/\">Process Pros team<\/a>.<\/p>\n<hr \/>\n<p>&nbsp;<\/p>\n<ul>\n<li>Watch our <a href=\"https:\/\/www.youtube.com\/watch?v=BKpDkQRgUqk\">Automations webinar<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Jira helps teams plan, assign, track, report, and manage their work together in teams or in cross-departments. You can integrate Jira with Process Street\u00a0to make your workflows super powerful and automate your work via Webhooks or Zapier. Users: In Jira, you&#8217;ll need\u00a0a user account with read\/write access to the project you&#8217;d like to automate or [&hellip;]<\/p>\n","protected":false},"author":11,"template":"","meta":{"_acf_changed":false,"available_plan":"All plans","available_product":"Integrations","footnotes":""},"ht_kb_category":[194],"ht_kb_tag":[197,373],"class_list":["post-5874","ht_kb","type-ht_kb","status-publish","hentry","ht_kb_category-integrations","ht_kb_tag-integrations","ht_kb_tag-jira"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/5874","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb"}],"about":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/users\/11"}],"version-history":[{"count":4,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/5874\/revisions"}],"predecessor-version":[{"id":9404,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb\/5874\/revisions\/9404"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/media?parent=5874"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb_category?post=5874"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.process.st\/help\/wp-json\/wp\/v2\/ht_kb_tag?post=5874"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}