Integration issue with KIWI TCMS while reporting a bug?

Arun_81ifnv

---

I’m integrating Kiwi TCMS with Jira to report bugs automatically. When I generate an API token with specific scopes (for example:
read:jira-user, read:jira-work, write:jira-work, read:issue-type:jira, read:issue:jira, read:issue:jira-software, etc.), I receive an “index out of range” error when trying to report a bug from Kiwi TCMS.

However, if I use an API token without restricting the scopes (default full access), everything works correctly.

It seems like the issue is related to one or more required scopes missing, but I’m not sure which exact permissions Kiwi TCMS requires to create Jira issues.

Has anyone successfully integrated Kiwi TCMS with Jira using a scoped API token?
Which scopes are needed for issue creation, project lookup, and issue type retrieval?

Any guidance would be appreciated.

Jason U

 

Hi Arun,

This behavior makes sense — KIWI TCMS cannot create issues unless the API token includes all required write + read scopes for Jira Cloud. When you restrict the token scopes, one of the required permissions is missing, which causes KIWI’s “index out of range” error.

Here are the scopes Jira Cloud requires at minimum for issue creation, project lookup, and issue-type retrieval:

Required Jira REST API Scopes

1. Issue write access (mandatory for creating bugs):

 

<span>write:jira-work </span>

 

2. Issue read access (needed for issue type lookup, transitions, metadata):

 

<span>read:jira-work read:issue:jira read:issue:jira-software </span>

 

3. Project + configuration read scopes (KIWI needs these to find project, issue type, fields):

 

<span>read:jira-user read:project:jira read:configuration:jira </span>

 

Minimum working scope set (tested with other CI/CD and test tools):

 

read:jira-user read:jira-work write:jira-work read:issue:jira read:issue:jira-software read:project:jira read:configuration:jira

When using a full-access token, all of these scopes are implicitly included — which is why your integration works only in that mode.

If even one of these is missing, KIWI TCMS cannot:

• fetch issue types

• read metadata

• create the issue

• or validate fields

…and that leads to the error you're seeing.

Recommendation

Try generating a new scoped API token including all scopes listed above.
This should allow KIWI TCMS to report bugs without switching to a full-access token.