I am using this https://<domain>/rest/api/2/issue endpoint to automate creation of some scheduled tasks which was working fine for months now but all of a sudden i can see this automation failing with all the error statements indicating
The mentioned projectId <projectID> for project name <project-name> is invalid. Specify a valid projectId
The reporter <email-id> doesn't seem to be part of project. Specify a valid reporter mail Id
I have verified manually by creating an issue from console and the reporter and task assignee are valid. Project ID is also correct which I have verified from this below api
https://<your-domain>.atlassian.net/rest/api/3/project
I am using python 3.9 running on lambda with requests library to make these requests.
I tried creating new api token and tested with that as well but that didn't help.
So, not sure the reason why the automation fails all of a sudden now. Any help or insights would be appreciated.
Thankyou
Does the user that is making the API call, have a JSM agent license and is this user in a the role service desk team in the JSM space?
Is the API token related with the users mail address converted to base64?
If a working actin fails, its because the API token used expired or that the user actioning has not got permissions or the permissions are not sufficient
Hi @Vikas Mahajan ,
Please also check the actor of the automation is having correct permission in the project. As per the issue you describe, it sounds like there is some change done in permission scheme which is stopping automation actor to be the reporter of the ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vikas Mahajan ,
please check the API token scope (https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/ ) in order to be sure that token is able to create items.
Hope this helps,
Fabio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.