Using REST API to move stories to next sprint error

[Alisa Gromova]

I've created an automation that POSTs to the "rest/
agile/1.0/sprint/{sprintnumber}/issue" endpoint to move stories from one sprint to the next. I subsequently end the current sprint and start the next. This has worked for about a year and but suddenly this specific endpoint started throwing this error: "We couldn't make that happen because you don't have Schedule Issues permission." (code 403).

I do have the permissions, I was able to manually stop the current sprint and start the next. I can't seem to find any kind of answers on this elsewhere. Anyone have any ideas?

[Trudy Claspill]

Hello @Alisa Gromova 

Being able to start and stop a sprint confirms only that you have the Manage Sprint permission.

Can you tell us which identity is being used to run the Automation? In the Rule Details what is the value of the Actor field?

Does the identity specified there have the Schedule Issues permission in the project against which the rule is running?

[Alisa Gromova]

Sorry, by automation I mean separate code, not JIRA Automations. My role allows me to add stories to future sprints, etc. That is the role that is used to authenticate for the API call.