Do filter subscriptions pull their results from cache?

We have a filter subscription that goes out once per day.  In the email sent, it displays the contents of a custom field (Scripted Field to be exact).  The problem is that even though the field has updated, the email still contains the old information.  It only seems to update after a re-index.  Any ideas on how to stop this?

3 answers

Hi Chris,

 

Is this issue with the scripted field containing cached values for the issue. If so you may want to add the following code below the import statements for the scripted field in order to disable the caching of values for the scripted fields on issues.

enableCache = {-> false}

More information can be found in the documentation here.

I hope this helps.

Thanks

Kristian

This may be related to when the "searchrequest" index is updated at the end of a system re-index. I tried re-indexing just the project and it didn't help. Is there a way to trigger the searchrequest index to be updated?

Hi Chris, Could you please send the script you use in order to update and save the scripted field ?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

373 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you