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.

[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

[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. 

[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 :)

[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]

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]

Added all headers - still issue with authorisation

[Monica Velasquez]

Thank you Bill

[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?

[Monica Velasquez]

Yes, the token is not revoked. Expiry date is in 2026. 

1 - Item is not archived as I'm transitioning manually. 

The automation is such that when a colleague moves the work item from done to 'archive (status)', the item is archived. 

2 - I have tried multiple times, but we keep receiving the same issue even with another admin. 

[Bill Sheboy]

As you have tried the common causes of this symptom, and are on a Premium license level, I recommend working with your Jira Product Admin to submit a ticket to Atlassian Support here:

https://support.atlassian.com/contact/#/

I recommend focusing on the automation rule example rather than the standalone endpoint calls.  When you hear back from them, please post what you learn to benefit the community.  Thanks!