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.

I want to set the Reporter name to someone else when creating a new issue in Jira Cloud. Sadly, that’s not supported today so it makes it seem like I, the Zap creator, am opening all of the Jira tickets, which breaks our workflows. :(

Does anyone have any hacks to get around this?

 

This seems to be a know issue for several years:

Hi @dstack 

You can look into using the Jira Cloud API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/

App APIs can be used in Zaps with the Webhooks app as an action step: https://zapier.com/apps/webhook/help

 

Maybe try sending the desired value in a custom text field to Jira, then configure Jira Workflows to detect the value in the custom field and set the Reporter: https://support.atlassian.com/jira-work-management/docs/how-to-create-workflows/

 

Or consider hiring a Zapier Expert: https://zapier.com/app/get-help

 

Otherwise, you can try opening a ticket with Zapier Support: https://zapier.com/app/get-help

Terms & Conditions