# Custom JQL function for search issues workflow

**URL:** <https://community.developer.atlassian.com/t/custom-jql-function-for-search-issues-workflow/21118>\
**Category:** Jira Cloud\
**Tags:** jql, jira-software, confluence-cloud, jira-cloud, rest-api\
**Created:** [July 16, 2018, 3:23pm UTC](https://community.developer.atlassian.com/t/custom-jql-function-for-search-issues-workflow/21118 "2018-07-16T15:23:28Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![RhysDiab](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/rhysdiab/32/38004_2.png) [@RhysDiab](https://community.developer.atlassian.com/u/RhysDiab)\
**Post date:** [November 15, 2019, 3:54am UTC](https://community.developer.atlassian.com/t/custom-jql-function-for-search-issues-workflow/21118/13 "2019-11-15T03:54:16Z")

</div>

Great discussion.

I’m trying to do something similar.

Is the best way to get all the issues initially by requesting them inside the ‘install’ lifecycle hook?

I’m having a problem requesting the issues initially as the addon without acting as the user. See my post [here](https://community.developer.atlassian.com/t/status-400-when-accessing-jira-cloud-api-endpoints-anonymously-inside-ace-lifecycle-hook/33448).

Thought you guys might have some insight.

Best Regards,  
Rhys

---

_[View the full topic](https://community.developer.atlassian.com/t/custom-jql-function-for-search-issues-workflow/21118)._