Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Best answer

Jira>Discord Zap

  • February 27, 2020
  • 5 replies
  • 176 views
M

Hi All,


A little confused here. I have created a Jira to Discord Zap so when a new issue is created in my jira cloud instance, a message is posted to a Discord channel in my server. However, it doesn't pass any of the issues data. It seems like it would be simple to solve, as I'd hoped there would be an area in the discord section of the zap to say what it should be copying from the jira portion, but it doesnt, it just seems to let me post a message saying something like "An Issue is created" What am I doing wrong here? I was hoping this was going to be something like Jira's slack integration.


Best answer by Danvers

Hi @MisterPariah! If you click on any of those fields then when the Zap runs it will use the information in that field.

For example if you click the 'Key' field, then 'BV21' will show in the box in the editor to let you know what the message will look like, but when the Zap runs, it will use the Key of whichever issue triggered the Zap. Does that makes sense? So, basically, look at the text in bold on the left - that's the field that will be added to the message. The lighter text is an example of what you'll see based on the sample that we have from the trigger step.


This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

5 replies

Danvers
Forum|alt.badge.img+12
  • DanversZapier Staff
  • Zapier Staff
  • March 3, 2020

Hi @MisterPariah Sorry for the delay in getting an answer on this for you!

Could you please show a screenshot of what you can see in the Discord step? If you're using the 'Send Channel Message action' then there should be a field for the message text.


M

@Danvers Thanks for the reply

Ive attached the screenshot. There is a space for the message, but nothing to reference the ticket number, etc. I would think there would be something that would display the ticket id (preferably with a link) and at least the summary of the issue. The only thing I can do is utilize the text of an already created issue, which kind of seems to be missing the point imo.

Screen Shot 2020-03-05 at 5.23.25 PM.png


jesse
Forum|alt.badge.img+9
  • jesseArchitect
  • Architect
  • March 8, 2020

Hey @MisterPariah just stepping in for Danvers here!

If you click on the "+" to the right of the "Message Text" field, that should show you some options from Jira that you can use in that step.

Does that help? Let us know!


M

Hi @jesse

Thanks for your response. I did try that previously but

image.pngas you can see it just asks me to reference an issue already created. For example with the way I have it configured, every time a new issue is created, it will post a message about "Bv-21", the same ticket, over and over. What I need is for the currently created ticket information to copy over, it needs like a (CurrentIssue) type of reference, you know?


Danvers
Forum|alt.badge.img+12
  • DanversZapier Staff
  • Zapier Staff
  • Answer
  • March 9, 2020

Hi @MisterPariah! If you click on any of those fields then when the Zap runs it will use the information in that field.

For example if you click the 'Key' field, then 'BV21' will show in the box in the editor to let you know what the message will look like, but when the Zap runs, it will use the Key of whichever issue triggered the Zap. Does that makes sense? So, basically, look at the text in bold on the left - that's the field that will be added to the message. The lighter text is an example of what you'll see based on the sample that we have from the trigger step.


Terms & ConditionsAccessibility statement