Moving to Cloud soon... how can I continue to benefit from scripted fields?

[Matt Ayres]

Hi,

Any help appreciated with this predicament...

In the next few months, we'll be moving from JIRA Server to JIRA Cloud.  We have several plugins that are key to how we work as a team, and most will migrate over fine... but I am concerned that when we move to Cloud, one of the things we have grown accustomed and is fundamental to the way hundreds of us work day-to-day to is going to stop working.

As it stands, we have 10-15 "calculated" fields that are implemented using Jira Misc Custom Fields (JMCF).  Our requirements mean that we need most of these fields to be searchable fields displayed on the JIRA tickets in question - i.e. using scriptrunner searches won't cut it.   I am aware that JMCF doesn't have a Cloud product because it is incompatible.  

Here are a few example scripted fields we have:

- "Sprint Resolved In" - to show which sprint a ticket was completed in.

 - "Epic ____" - fields on stories and sub-tasks that display details of fields on the epic (e.g. Epic Quarter is the quarter in which an epic is planned - this would show as a field in the ticket).

 - "Reporting Status" - this generates a value based on the status of other custom and calculated fields.  

- "Epic Reference" - a concatenation of the epic ID and epic name that is displayed on tasks and subtasks, for the purposes of reporting

 - "Deliverable Readiness" - generates a markup table in a field that displays the readiness values pulled from up to 8 sub-tasks.

Now I think that most of these can be re-creatred in JMWE or ScriptRunner using post-functions and listeners.

However, herein lies the problem... In JIRA Server, if I make a change to Field A of Issue A, then I can run a re-index to re-calculate the scripted field values of issues that may have been affected by this change.  This in turn means that my JQL searches will pull back the correct results.  

... in JIRA Cloud, I gather that the re-index feature has been removed as it is "no longer needed".  I have a feeling that that is incorrect in the case of calculated/scripted fields, as based on information on the Adaptavist and Innovalog support sites, searches will only pull back the correct data once an issue has been displayed in a browser (i.e. reindexed).  

Is anyone able to help shed some light on this for me?  Thanks!