WHY JQL and why not reports?
JQL is very powerful and it brings in all the advantages of Issue Navigator. You can combine them with other JQL functions to narrow down the search. Exporting into different formats, different views, sorting etc comes with Issue Navigator and hence JQL!
Can I subscribe using these new JQL functions?
Yes, you can. You can do anything that is possible with the Issue Navigator and filters.
Does it affect the JIRA performance?
No. JQL Tricks Cloud App uses the native JQL aliases functionality and doesn't add extra load on the system during a search. The indexes itself are built asynchronously to reduce the performance overhead when issues are updated.
There a quite a lot of functions but I am not interested in few of them. Can we have a subset of functions?
This is only an option in Jira DC version of the plugin. However, the JQL aliases are neatly namespaced so that the users can easily find out the functions they are interested in.
How to trouble shoot?
Please create a support ticket in our JIRA and we will surely be able to help!
HOW DO i request for new functions
Please raise a "New Feature" in our JIRA and we will prioritize it based on the criticality of the request.
Has JQL Tricks Cloud transitioned to the Forge framework?
Yes. JQL Tricks for Jira (Cloud) is already built on the Forge framework. It is a Forge-native application and does not rely on a temporary Connect-on-Forge wrapper.
- Timeline & Cutover: The transition has already occurred, meaning Atlassian’s Connect end-of-support deadlines (December 2026 / January 2027) present no migration risk or operational impact for JQL Tricks Cloud customers.
- No Action Required: Existing Cloud customers do not need to reinstall, upgrade, or migrate to a successor app.
How does JQL Tricks Cloud process and store customer data?
JQL Tricks Cloud prioritizes data security and minimizes external storage by leveraging Atlassian’s native infrastructure:
- Data Residency: Searchable metadata generated by the app is stored within Jira issue entity properties under the jqlt.* namespace. This data resides directly within your Jira Cloud instance and fully abides by your site’s Atlassian Data Residency configuration.
- Data Storage: We do not maintain a separate long-term database copy or data warehouse of your Jira issue content, comments, attachments, or user profiles.
- Forge Remote: Selected backend operations (specifically full index rebuilds initiated by a Jira administrator) are processed via Forge Remote. While temporary processing occurs on vendor-hosted infrastructure during full reindexes, the processed data is written back directly to Jira entity properties. Incremental indexing (via Jira events) and JQL function execution run natively on Atlassian Forge infrastructure.
- Security & Compliance: The application is Cloud Fortified and actively participates in the Atlassian Marketplace Bug Bounty program.