Script JQL Functions: linkedIssuesOf() vs. epicsOf() & issuesInEpics()

[Dennis Markwart]

Hi,

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?

[JamieA · Accepted solution]

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. 

[Dennis Markwart]

Thanks for your quick reply, Jamie.

This perfectly answers my question!

[Prabhakaran Nachimuthu]

How to run the  (IssuesInEpics() and epicsOf()) functions?

[Dennis Markwart]

Hi Prabhakaran,

both functions are very well documented in the Adaptavist Wiki, including examples:

https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_epicsof

https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_issuesinepics