in the past we used the JQL Script Function linkedIssuesOf() to find Issues in certain Epics or Epics of certain Issues. In a newer version of the Script JQL Functions, it seems like there are some more convenient functions introduced (IssuesInEpics() and epicsOf()) to achieve the same result:
issuefunction in linkedIssuesOf(SUBQUERY, "is Epic of") issueFunction in issuesInEpics(SUBQUERY)
issuefunction in linkedIssuesOf(SUBQUERY, "has Epic") issueFunction in epicsOf(SUBQUERY)
Does those new functions have a better performance than the linkedIssuesOf() function? Does it make sense to migrate all existing Filters to use the new Functions?
No - performance will be identical. If one way was faster we'd do a migration job, or at least encourage people to change them manually. (You could probably verify they have similar performance characteristics using the provided profiler).
My advice would be to use epicsOf etc going forwards, as it's more intuitive and has a simpler syntax, but no need to migrate.
both functions are very well documented in the Adaptavist Wiki, including examples:
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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!
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