Hello dear Community,
There are two issues I’d like to get your thoughts on. I hope you can help me or share your ideas.
Firstly, I have an automation in place. It consists of 12 steps and sends three web requests.
The purpose of the automation is to create a ticket and a ‘linked work item’ from Instance A to Instance B.
To achieve this, an ‘Application Link’ was created between the two instances, and the automation was set up by writing these steps using Web Requests. However, this automation was created using an Organisation admin account and uses its API token.
The aim here is to make this automation operational using a ‘Service Account’. Listing the steps taken in order:
1. A Service Account was created, and under ‘Apps’, Jira Admin (App Admin) + Jira (User) were added to ensure it is valid for both instances; no other options were available.
2. For credentials, an API Token was generated and the following permissions were granted: (I think this is actually too much, but I wasn’t entirely sure.)
3. The API Token was converted from Base64 and integrated into the Basic c2V....
4. The system account was added as an admin to the projects; additionally, ‘Browse Project’ and ‘Create Issue’ permissions were added for a single user via the project permissions section. As I tested each stage in turn, I considered this as an option and added it for testing purposes
5. The permissions for the service account were tested via the Permission Helper, and the permissions appear to be in order in both projects.
However, following the tests carried out, the system continues to display the same error :
Hi @Y_ Oezl
What is the API endpoint you are using?
Here is an example of a properly formed URL for a request to the Jira app: https://api.atlassian.com/ex/jira/{cloudId}/rest/api/3/project/{project_key}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.