Slack third_party_bad_request_error

[Egor Shchukin]

Hi! I have set up a workflow in Slack so that managers with guest accesses will use Slack form to create ticket in Jira. At the start of the year flow looked like this: press the button, connect your Jira account, fill the data, ticket is created

Now when managers open this form, step to link account doesn't exist, and at the end of doing everything correctly, any manager with Slack guest access gets third_party_bad_request_error
Any manager with full access in Slack is able to make ticket through this flow.
I've managed to change setting in Slack workflow so that every ticket done by this form will use my account to make Jira ticket, but then that leaves a room for misinterpretation. How i can make it so that Jira ticket will again be created by the person who used the form, even if the access in Slack is guest one?

[Marc -Devoteam-]

Hi @Egor Shchukin 

Welcome to the community.

IS the created ticket via slack ending in a JSM project?

How are the customer permissions set on this project, have there been any changes?

[michelle_samaan]

I have a similar issue, and I'm stuck trying to find a solution. I created a workflow on Slack where users click on a button within a channel, fill out a form, then an issue is created in Jira, and a message confirmation is sent to the Slack channel. When I test it, it works perfectly, but another person is trying to submit the form and they see an error:

This workflow didn't finish/ We couldn't complete the create an issue step:
| This happened because there's a problem with the information that you provided.

When I look at the logs, the only thing I see is the error third_party_bad_request_error with no further information. 

I tested with the same information the user was trying to input and it worked for me. The user has access to the Jira project, so not sure how to troubleshoot this.