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.

[Camilli Santos de Araujo]

Hi Michelle!

I'm currently facing exactly the same issue with a Slack workflow that creates Jira tickets from a form. 

Were you able to find a solution or identify what was causing the problem in your case?

Any insight would be greatly appreciated!

[Marc -Devoteam-]

Hi @Camilli Santos de Araujo @michelle_samaan 

Is Slack integrated with Jira and is the command /jira create used in the workflow?

I also think this can only be done by licensed users, as the action is not via email or the portal.

So I don't think this can de done as a "customer"

Can you try to grant a user a license as test and see if it then works, this would confirm my theory

[michelle_samaan]

Hey @Marc -Devoteam- yes for both. All my customers are internal employees with a Jira user license. I wasn't able to find a solution, and the most intriguing thing is that the workflow works when I test it, but not when other people use it, and I built it by cloning a previous workflow targeting the same users that is still working as expected. I can't understand why one works and the other doesn't.

[Marc -Devoteam-]

Hi @michelle_samaan 

Who is providing the error, Slack or Jira?

If it is slack what is the full error, if that only shows "third_party_bad_request_error " then it's best to reach out to Atlassian Support or even Slack Support to get claritrty on the error.

As this indeed shows little information.

[Chachi Camejo]

I'm getting the exact same error. The destination project is a Jira Product Discovery project. In the error log, I have this error in the last step recorded:

Create an issue — There was a problem with the information the user provided.