This will enable users to easily track who reported a User Feedback ticket. Currently, it requires adding an email custom field and setting up Jira automation to perform the mapping of the email to the Jira "Reporter" field.

Would be nice to have the possibility to set custom component, issue type etc for issues that gets forwarded to Jira. Also, it would be great if we could further customize the JIRA reports. And when closing the JIRA ticket, it would close the Shake ticket as well, to prevent duplicated manual work.

It'd be great if we could manually set a value of some custom field that would be forwarded to our Jira. Why? We've set some fields as mandatory (e.g. "Components") for creating the Bug in Jira, which means Shake is and will not able to create a new Bug there until it starts forwarding some placeholder value there.

https://atlassian.com/software/jira • At the moment Shake supports automatic Jira field mapping but it's an experimental feature. We want to have full control to reliably and manually control which Shake fields are mapped to which Jira fields.

Context: It seems like I can't set up a second Zapier webhook if I already have one. The problem is -- if I want to set up more than one workflow on my end, then I have to stack all of the workflows into the same Zapier automation -- which can complicate things.

https://zendesk.com

https://www.pivotaltracker.com

https://www.make.com

Have you considered adding an integration to Segment.io , so your data could then be forwarded to any number of services they support and combined with user behavior data?

https://canny.io/