Custom JQL Pre-computation API - Need a Delete API/Disable Pre-computation

Shenba_o95yrc

Hi,

I am trying to write a custom jql. But the precomputation functionality is bit complex to implement for my usecase. I can't store all precomputation ids and the parameters and check every one of them every time when there is a change in data to update with new computation. For example, some of my custom JQLs can be impacted by actions like update in custom fields or linking issues. For that I may have to update hundreds of precomputations. Also it is hard for tracking all the parameters for the precomputations. 

As a solution, I expect a way to delete precomputation via REST API or to disable pre-computation via atlassian-connect.json config. It seems, with precomputation, I have to make hundreds of requests to JIRA every minute.

Mercy_dt1a1g

Jira Cloud’s custom JQL functions use precomputation to cache results for performance reasons, and that behavior is controlled entirely by Jira’s internal query engine. There isn’t a public REST endpoint or `atlassian-connect.json` flag to delete or disable precomputed results. The platform automatically invalidates cached results when issue data changes, but if your function depends on complex conditions such as issue links or custom field updates, you’ll need to manage the cache lifecycle yourself within the JQL function module by implementing the `invalidatePrecomputation` logic in your app’s backend.