# JQL returning all issues

**URL:** <https://community.developer.atlassian.com/t/jql-returning-all-issues/58902>\
**Category:** Forge\
**Tags:** jql, forge-api, forge\
**Created:** [June 7, 2022, 8:12am UTC](https://community.developer.atlassian.com/t/jql-returning-all-issues/58902 "2022-06-07T08:12:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajay](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ajay/32/53765_2.png) [@ajay](https://community.developer.atlassian.com/u/ajay)\
**Post date:** [June 7, 2022, 8:12am UTC](https://community.developer.atlassian.com/t/jql-returning-all-issues/58902/1 "2022-06-07T08:12:52Z")

</div>

I am facing a weird issue with Forge since yesterday where the JQL results are not matching

```auto
/rest/api/3/search?jql=reporter in organizationMembers("GBS") OR reporter = "qm:d9d879d4-05b6-4eee-b93e-2e15c7cb337f:3830d79c-7c7f-4cce-8de5-876bc2bdb931"

```

The result via JQL search on the instance returns me 13 issues ( which is correct)  
whereas calling via Forge API returns 79 issues ( all the issues in the instance)

```auto
API.asApp().requestJira(route`${requestURL}`

```

---

<div class="post-metadata">

**Author:** ![CaterinaCurti](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/caterinacurti/32/42270_2.png) [@CaterinaCurti](https://community.developer.atlassian.com/u/CaterinaCurti)\
**Post date:** [June 7, 2022, 10:36am UTC](https://community.developer.atlassian.com/t/jql-returning-all-issues/58902/2 "2022-06-07T10:36:57Z")

</div>

Hi @ajay,

I could reproduce this behaviour in my test site as well. I’ve reached out to our developers to check what might be happening here.

Thanks for flagging this with us,  
Caterina

---

<div class="post-metadata">

**Author:** ![ajay](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ajay/32/53765_2.png) [@ajay](https://community.developer.atlassian.com/u/ajay)\
**Post date:** [June 8, 2022, 3:47am UTC](https://community.developer.atlassian.com/t/jql-returning-all-issues/58902/4 "2022-06-08T03:47:38Z")

</div>

@CaterinaCurti ,

Is there a Forge Jira issue created for tracking this bug?

---

<div class="post-metadata">

**Author:** ![CaterinaCurti](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/caterinacurti/32/42270_2.png) [@CaterinaCurti](https://community.developer.atlassian.com/u/CaterinaCurti)\
**Post date:** [June 8, 2022, 10:45am UTC](https://community.developer.atlassian.com/t/jql-returning-all-issues/58902/5 "2022-06-08T10:45:20Z")

</div>

Hi @ajay ,

Can you try to change the code to this and confirm that only the issues matching the JQL are returned?

```auto
const requestURL = route`/rest/api/3/search?jql=reporter in organizationMembers("GBS") OR reporter = "qm:d9d879d4-05b6-4eee-b93e-2e15c7cb337f:3830d79c-7c7f-4cce-8de5-876bc2bdb931"`;

const res = await api
      .asUser()
      .requestJira(requestURL);

```

I tested this today and it works for me, in this way the entire URL will be sent to Jira. This behaviour didn’t change on our end since some time so maybe the way `requestURL` was defined and used changed in the app code in the recent past.

About creating a tickets, we would normally create one once confirmed that it is a bug. That’s why I didn’t create one right away yesterday.

Hope this helps,  
Caterina
