moving to cloud: loss of JQL functions?????? e.g., childissuesof()

[Peter Heffner]

Is there a resource that covers the non-backwards compatibility issues???  

[Cristiano Alves -Appfire-]

Hello @Peter Heffner 

Cristiano, with the AppFire Team here.

Unfortunately, there are some functins not available on native Jira Cloud (or some functions are limited)

If you're interested in third part solutions, the app our team works, JQL Search Extensions for Jira, adds a lot of functions to it.

issue in childrenOfIssuesInQueryRecursive("project='ACME' and type=Initiative") 

Finds all epics, stories, and subtasks in initiatives in project ACME.

issue in childrenOfIssuesInQueryRecursive("assignee=currentUser() and type=Initiative", 2)

Finds epics and stories of all of my epics and skips the subtasks.

If you need any help, feel free to contact our support team.

Regards,

[Trudy Claspill]

Hello @Peter Heffner 

For the specific case of the native childIssuesOf() function, in Cloud you can use the portfolioChildIssuesOf() function. It takes the same parameters.

I'm not immediately recalling if Atlassian provides a document that specifically covers the feature parity of native JQL functions between DC and Cloud. There may be one, but I apparently have saved a link to it if such exists.

If you use third party apps that extend JQL capabilities (or any third party apps for any purpose) you should be reviewing the migration information for each app. They often list links for migration guide information and feature parity information on the Support tab of their Atlassian Marketplace listing.

[G subramanyam]

Hi @Peter Heffner welcome to the Atlassian community.

Please be informed, on Jira Cloud, the way you solve for a "parent-child" relationship search is slightly different and relies on a combination of native JQL and marketplace apps.

As far as I know, unfortunately, there is no single, comprehensive Atlassian resource that lists every single non-backwards compatible JQL function from every third-party app. That would be an incredibly difficult document to maintain.

Workaround:

• Go to the Atlassian Marketplace and search for the Cloud version of the apps you use. App vendors (like Adaptavist, the creators of ScriptRunner) usually have their own dedicated migration guides that detail any functional differences, including JQL.
• This video provides an overview of the childrenOf JQL function.

[Peter Heffner]

thanks for jumping in with info.   Disappointing that my org's migration gave no warning, leaving a lot of filters and dashboards SOL.