How can I set up bidirectional comment sync between Slack and Jira Software for created tickets?
Hi Everyone, We want to achieve: Bidirectional comments Sync from slack to jira software: Tickets created through slack in Jira Software after that comments syncing should happen into that same ticket. Here is the loom for further clarification. I am in touch with the Zapier support from last one moth but still they are not able to solve this issue. Can anyone please help! Thanks in advance.
Page 1 / 2
Hi @Shikha Verma
Make sure you are using the updated Slack Zap app version in the Zap steps.
For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode with the field mappings visible for the Zap that triggers from: Slack - New Message Posted to Channel
No. Zapier does not support two-way syncing between apps right now. Think of Zaps like one-way workflows.
In certain scenarios, you can fake two-way syncing by setting up two different Zaps that perform opposite actions. For instance, you could have one Zap that creates a new spreadsheet row for every new contact created and another that creates a new contact for every new spreadsheet row.
Thanks for your quick response. Below is the screenshot of my Zap. We have two scenarios: first, when we click on the emoji to create a ticket in Jira from Slack, and we have a Zap functioning properly for that. Now, we want to ensure that after the ticket is created, the comments from the Slack thread sync into that Jira ticket and vice versa. The screenshot I’m sharing shows that it works fine during the Zap test, but it doesn't function correctly during real tests. It seems it might not be able to find the Slack thread or something similar; I'm not sure what the issue is.
@Shikha Verma
No screenshot included.
@Shikha Verma
For Zap step 5, try removing the double quotes.
For Zap step 6, post screenshots showing how your Zap step is configured in EDIT mode.
Check your live Zap Runs history details to see the DATA IN/OUT for each step to help you trace the data flow and troubleshoot: https://zapier.com/app/history/
Hi @Troy Tessalone, Thanks for getting back to me! I've tried multiple times to resolve the issue, but it persists. All new tickets and comments created in a specific channel are syncing to a single ticket (FS-865) from the beginning. I've explored various options, including changing the trigger from "any message posted" to "when an emoji is added," but nothing has worked. Could you please assist me with this? If needed, I can share Loom videos for a better understanding of the issue. For now, I'm sharing screenshots of the successful Zap setup (Output), which shows that any message posted in that channel is being synced to the FS-865 ticket which I used as an example during the Zap creation and testing. Solving this issue will greatly appreciated as the Zapier team was not able to solve this in 25-30 days.
@Shikha Verma
For Zap step 6, for the Issue field, you need to use the h...] button to switch to “Custom” mode, then use the s+] button to map the ID of the Issue from Zap step 5.
Hi @Troy Tessalone Thank you for the information! I checked but everywhere its showing the ticket number 865 (which is the wrong one, used for the testing purpose) Can you please suggest. Thanks!
Do I need to change something in step 4 because I am assuming Input is-865 thats why all comments are syncing to the 865. (Screenshot for your reference)
@Shikha Verma
See screenshot for the ID variable to map from Zap step 5.
Hi @Troy Tessalone I tried so many options available in step 4 (tried Input Ts, Text, link etc) but then its showing different errors in Step 5 (like the screenshot below).
@Shikha Verma
Post screenshots from Jira showing a related ticket that you are trying to find based on the Zap trigger data.
Hi @Troy Tessalone I tried ID also but there is no data.
@Shikha Verma
We would need to see how the 2 Formatter steps are configured in the CONFIGURE tab for full context.
The ID variable from Zap step 5 should be mapped to the Issue field in Zap step 6.
Still have not seen screenshot from Jira showing a ticket that you are trying to find with the Zap step data.
Hi @Troy Tessalone Can a loom will help you to find the issue? If Yes will share the whole Zap step by step with you.
Hi @Troy Tessalone Here is the screenshots of Zap step 4 and 5
This is the ticket which is supposed to be linked comment.
This is the ticket where all the comments are synced.
@Shikha Verma
In Zap step 4 (Formatter), if you are try to get just the Issue ID (e.g. FS-886), then you you will need to use a different Formatter action.
Zap action: Formatter > Text > Split
Split by: /
Segment: Keep the last segment
That will take the URL from Step 3, split by all of the forward slashes and keep the value after the last forward slash which should be the value of the Jira Issue ID.
For Zap step 5 (Jira Find Issue), set the “Key” value to be the output value from Zap step 4.
Click on field labels to see tooltips with more info that can provide guidance about expected values and formatting.
@Troy Tessalone I followed the steps you provided and showing the following error after test.
However Zap passed all the test and also showing correct jira issue ID in the output (screenshot below). But when I actually test it with other message then it failed.
@Shikha Verma
The best way for you to troubleshoot is to review the Run Details for each Zap step.
Check the DATA IN tab and the DATA OUT tab to see the actual data that was used.
You may need to add a Filter steps to make sure the Zap steps are returning the desired data point or output before trying the next Zap step to prevent Zap Run errors.
@Troy Tessalone I am assuming that the comment Test 2 and one more test does’t contains the Issue ID-886 that’s why the Zap is not able to find the issue and showing the error. If that is the case then how we will resolve it? Do we need to add/delete any extra step or Do we need to change the trigger?
@Shikha Verma
If I’m understanding correctly, the purpose of Zap step 3 would be to get the URL from the thread of comments.
But you have a variable mapped from Step 1 instead of Step 2.
Ideally, the first message of the thread is found to use to extract the URL.