Issue Accessing Story and Epic Data via Jira API During Marketplace App Review

[hasanozdisci]

We are currently in the process of developing a new application for the Atlassian Jira Marketplace. Our application interacts with Jira's API to retrieve user data, tasks, issues, epics, and stories. During our internal testing environment, everything functions correctly, and we are able to access all required data without any issues. We receive the expected 200 status codes from the Jira API, and all relevant data (including stories, epics, etc.) is returned as expected.

However, during the review process for publishing our application on the Atlassian Marketplace, we encountered a problem. Although the Jira API returns a 200 status code during the Marketplace review tests, we are unable to access specific data related to stories, epics, and similar issue types.

We would like to understand why this discrepancy is occurring during the review process, and how we can resolve this issue to successfully pass the review and publish our application on the Marketplace.

We logged the JQL query that our application uses to retrieve data, and as shown in the attached image, the query returned no results during the Marketplace review.

When we manually enter the same JQL query into the Jira application’s filter section, the expected data is returned correctly, as shown in the second attached image.

[Deniz Oğuz - The Starware · Accepted solution]

Hi,

The response you get from the Jira JQL search can be different than what you see on the UI if you are using asApp() in your API calls. App may have a different permission than normal Jira users.

[hasanozdisci]

Hi,

Yes, I use the asApp() method for calls within the application. I will change these to asUser() and start the process again.

If I do not encounter any issues during the remainder of the review process, I will mark this as the accepted answer.

Thanks for your support.