nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation Authentication

Monica Velasquez

I'm building a fairly simple automation where

1 - If an item is transition from Done --> To Archive

2 - the automation does a PUT request to archive the iteam

I've tested my Basic Authentication using talend API tester, and it works in a web request.

When I test in Postman I get the following error

{
"errorMessages": [
"Issue does not exist or you do not have permission to see it."
],
"errors": {}
}

3- In my automation I have the following, and throws the following error. I've checked the permissions, and my user is a global admin and also part of the group that allows for archiving.

Any help appreciated.

Accepted answers

All comments

Duc Thang TRAN

Hello @Monica Velasquez

I think it comes from value of “authorization”.
For cloud, I'm using:

Key: Authorization
Value: Basic "Base64-encoded email + API token"
(There is a space between Basic and your encoded value)

Hope it help

Matteo Vecchiato

Hi @Monica Velasquez ,

The string after "Basic" must be the Base64 of useremail:api_token.

This question could help you: https://community.atlassian.com/forums/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Hope it helps

Bill Sheboy

Hi @Monica Velasquez -- Welcome to the Atlassian Community!

I recall the endpoint to archive a work item is still considered experimental:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-archive-put

The rule must include the additional header to "opt-in" for its use:

Key: X-ExperimentalApi
Value: opt-in

Kind regards,
Bill

Monica Velasquez

Thanks Matteo, I've done this. When I do a GET request via Talend it works and I receive a response. Talend also build the Basic Token in Base64

When I do the same request in Postman, it does not work.

When I use in the automation rule it keeps saying user not logged in

But clearly I'm logged in, as I'm the user building the automation.

Monica Velasquez

Added all headers - still issue with authorisation

Monica Velasquez

Thank you Bill

Monica Velasquez

Thanks Duc, as replied above - I keep having the same issue - but no clue. Tried your suggesstion and is the same. Postman and the automation have auth issue, but Talend does not.

Bill Sheboy

@Monica Velasquez -- Are you repeatedly calling this endpoint with the same work item key?

If so, it is already archived and so fails
If not, have you confirmed the token did not get revoked somehow?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud