"Unauthorized" error when executing JQL

[Admin Jira SQS]

I get This error when looking up issues by JQL in an automation:

BUSCAR INCIDENCIAS

Se ha producido un error al ejecutar una búsqueda durante la definición del valor personalizado: .

Custom Smart Value JQL Search: "Status = Done" - Unauthorized

The action is very simple:

Status = Done

How could I solve this?

Thank you!

[Andy Heinzer]

Hi @Admin Jira SQS 

I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-959168

If you want to 'grant data access' you can do so in that link, this might help our support team to investigate a bit faster, but is not always required.

While I don't have access to your site, I couldn't see a clear cause for this error.  My hunch is that your environment might have a team managed project that is restricted access, and/or a project that contains a custom field called "Status" as well.  This could cause JQL to get confused about which field that service account (Automation for Jira) is able to query on.

You could try to run the automation as a different user, such as a site-admin as a means to troubleshoot this, but if that doesn't work, I'd recommend reaching out in that support case so that our team can take closer look at your environment.

Andy

[Admin Jira SQS]

Thank you, Andy.

I have reviewed the custom fields, and I don't see any "Status" field. I attach the corresponding screen image showing no fields among "Start date" and "Story point estimate" (where any field starting with "Status" should be) in the alphabetical custom fields list.

I've tried to configure the automation with an admin user (I attach the rule details screen image). But when I press on run rule, no execution is registered in the audit log (I attach also screen image).

[Trudy Claspill]

Hello @Admin Jira SQS 

Can you provide screen images that show us all the steps in the rule, the details of the step where the JQL is being used, and the complete details from the Audit Log for the rule execution?

[Admin Jira SQS]

Hello Trudy.

Thank you for your interest. 

I attach the required screen images. Of course, you can ask me for any other image or information you could require.

[Admin Jira SQS]

[Trudy Claspill]

What happens when you click Validate Query in the Lookup Issues step?

Who is listed as the Actor for the Rule on the Rule Details page?

What is the project scope for the rule? Is it one project or multiple projects?

For all the projects in scope of the rule, does the Rule Actor have permission to browse all those projects?

[Admin Jira SQS]

Thank you again, Trudy.

The validate query returns OK with 5 issues found (see attached image).

The Actor for the Rule is "Automation for Jira" (see attached image).

The project scope for the rule is "Global" (see attached image). This Jira only has one  project created.

For all the projects in scope of the rule, does the Rule Actor have permission to browse all those projects? I supposed so. Do you know wether the user "Automation for Jira" has the required permissions by default? If not, how could I enable the required permissions for the user "Automation for Jira"?

Thank you again.

[Trudy Claspill]

Check the permission scheme for the project. Confirm that the Browse Projects permission is granted to 

• Project Role (atlassian-addons-project-access)

[Admin Jira SQS]

Thank you again, Trudy.

In the permission scheme for the project, the Browse Projects permission is granted to

Project Role -> atlassian-addons-project-access. I show you the snapshots.

Thank you!

[Trudy Claspill]

As an experiment can you try changing the rule scope from Global to Single Project and specify the project, then see if the same error occurs when the rule executes?

[Admin Jira SQS]

Thank you, Trudy.

Unfortunately the result is the same.