JQL Support
Power Scripts for Jira Cloud may really enhance your ability to search for issues using JQL. It has the ability to transform your searches into something really powerful and unique, tailored to your specific needs.
However, it is important to point out the difference between a traditional, server-hosted JQL function and a cloud-hosted JQL keyword. In cloud-based environments, everything is asynchronous. Jira and Power Scripts are on different hosts and they communicate via HTTPs calls.
Integration on cloud is therefore based on keywords, each encompassing a certain functionality used for the search. A JQL keyword is meta-data for an issue that has been evaluated and saved in Jira, prior to the JQL search, asynchronously.
By default, auto-synchronization of the keywords is disabled. It is recommended to enable auto-synchronization if you want to harness the true power of this feature. Details may be found in the “Keyword Syncing“ page.
Note that enabling auto-synchronization is not enough. For search to be accurate, you need to synchronize at least once the collection(s) or issues you want to query. This can be done either by adding project / project category or for the entire JIra if there are none projects / projects categories configured.
The synchronization process may take a long time, depending on the number of enabled JQL keywords and, of course, the number of issues.
Prior to that, though, you need to decide what to synchronize between Power Scripts and Jira
Decide what you want to synchronize
Power Scripts offers you either predefined keywords or custom ones. For optimal performance you should enable just the ones you want to use.
The standard keywords may be enabled on a category basis (i.e. you cannot control individual keywords, you need to enable the whole category to use a certain keyword).
For a complete list of standard predefined JQL keywords, please examine this page.
Custom keywords are synchronized only if you enable them from their tab.