Jira Release Approver Automation

[Anthony Pugliese]

Hi all

am trying to follow this document around sending Approvers within Releases an email
How to send emails Approvers of Jira release using Automation for Jira | Jira and Jira Service Management | Atlassian Support

what issue i am facing is that the following error appears

=======================

Send Web Request 05/11/2026, 13:14:22

Unable to publish the web request - received HTTP status response:

404

Error found in the HTTP body response:

{"errorMessages":["You must have browse project rights in order to view versions."],"errors":{}}

============================

i am assuming since i dont have browse rights in all projects in my org, i am having this error? would i be correct in that assumption?

is there a way to define the URL this further down that i am only asking to browse a specific project rather than all projects within the jira instance/account??

• Web request URL: https://sitename/rest/api/3/version/{{version.id}}?expand=approvers

[Trudy Claspill · Accepted solution]

Hello @Anthony Pugliese 

In the Rule Details for the Automation Rule, how have you set the Scope for the rule? That is where you define the Projects to which the rule will apply.

[Anthony Pugliese]

yes the scope is specific to my project 
and this project i am the space admin, iteration manager

i have also checked permissions and all users have "browse" permissions on this project

this answers my question about being specific to the project, but doesnt help me understand why the error appears since i have access

[Trudy Claspill]

Hello @Anthony Pugliese 

I apologize for not getting back to you sooner. I haven't yet had time to investigate this more.

I see you marked my answer as Accepted but I don't feel like I've actually answered your question.

With the rule scoped to a specific project you should not need access to every project. The permissions check would be getting applied to the user for whom the token was generated, where you are using that token in the Send Web Request action. So the next question would be the one posed by @Bill Sheboy about the permissions allocated in the target project for that user.

[Anthony Pugliese]

my rule was scoped to the project so there was no issue running it on all projects

but the problem lied with the token. when i converted it to base64, something was a miss with the copy and output

once i fixed up the copy error the token and automation worked

[Bill Sheboy]

Hi @Anthony Pugliese 

Does the user for the API token in the rule action have permissions needed for that project / space?  If not, please try with a different user's API token.

Kind regards,
Bill

[Anthony Pugliese]

token had access, it was due to a copy error