Getting EDIT_ISSUES error when trying to add steps to the test case using Jira Cloud API

[Sai Audithya Sarvabhotla]

Hi,

I am trying to add steps using below API by generating the JWT token and passing correct accountID, secret keys and access tokens but i am not able to add steps using the API

End point: https://prod-api.zephyr4jiracloud.com/connect/public/rest/api/1.0/teststep/713627?projectId=10010

Request headers - Authorization  and zapiAccessKey

Response:
{
"errorType": "ERROR",
"clientMessage": "User does not have EDIT_ISSUES permission to perform the operation...",
"errorCode": 169
}

i have created the testcase using jira api and it got created successfully and also checked mypermissions for that test case and it says i have edit access but using the above API getting error

https://epssw.atlassian.net/rest/api/3/issue

{

    "id": "713640",

    "key": "TESTPROJ-20729",

    "self": "https://epssw.atlassian.net/rest/api/3/issue/713640",

    "watchers": {

        "status": 200,

        "warningCollection": {

            "warnings": []

        }

    }

}

 https://epssw.atlassian.net/rest/api/3/mypermissions?projectKey=TECHNIQUE&issueKey=TECHNIQUE-20729&permissions=EDIT_ISSUES

https://epssw.atlassian.net/rest/api/3/mypermissions?projectKey=TECHNIQUE&issueKey=TECHNIQUE-20729&permissions=EDIT_ISSUES

[Hari Krishna]

Hi @Sai Audithya Sarvabhotla 

When using the Zephyr API to add test steps, this error usually means the account used in the API call (via the JWT token) doesn’t have the necessary permissions in that Jira project  even if Jira shows that EDIT_ISSUES is granted.

Here’s what to check:

- Make sure the JWT token is signed with the correct `accountId`   the same user who actually has permission in the project.
- Zephyr APIs run in the app context, so permissions need to be valid not just for the Jira UI but also for API-level operations.
- Try giving Project Admin permissions to the user used in the token as a quick test  if it works, it confirms a scope issue.
- Also ensure that the `projectId` and `issueId` used in the API call are accurate and that the issue belongs to the specified project.

This usually resolves the “User does not have EDIT_ISSUES” error when calling Zephyr Cloud APIs.