I have one managed account that i used to link between "Jira" and "Gitlab" then suddenly the connection failed and returned me with this error "You currently don't have access to perform this operation."
I have checked and the API Token is still active.
As a comparison I have tried to create a API Token using my own personal account and it worked just fine, looks like the problem is only with this managed account.
Anyone know how to fix this? Any advice is much appreciated! Thank you.
Does the account still have a Jira license or is the managed account disabled?
The don't have access tells me there is something with the account itself.
I would look into that.
Thanks for responding.
The managed account still have access as follows:
Has access on this site YES
Jira Software NO
Confluence NO
Confluence GUEST NO
and it does have admin rights for the project we want it to manage.
there was no configuration changed done for this managed account.
Last time the api token was working was 8 January 2024. After that all connection failed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Project permissions don't help if the user in question has no license assigned.
No license is "No Access".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Marc - Devoteam
Thanks for replying me again.
If I understood correctly, you are saying that this "Has access on site" is not sufficient and I need to turn on the one for Jira so that the managed account has access to Jira as well?
Because as mentioned the configuration for this managed account remained the same for 2-3 years, it was just suddenly not working after 8 Jan 2024.
Is there any changes on Jira side that causing this to happens? (if you happen to know)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Has access on site only means the user would have access to an open JSM portal or anonymous accessible Confluence spaces is there are any.
The user wouldn't have access to a Jira project if not granted a Jira license and therefore wouldn't be able to provide any information from gitlab to a Jira issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks a lot for the help.
I have just enabled the Jira Software access then voila the api token start working again. Im not really sure whether there was any changes on Jira site prior to this, as it was working before.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.