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:
Hi, thanks for sharing. Having some doubts here. How come these queries are bringing for my project different results
Was under the impression that the linkedIssuesOf would bring all related issues (no matter what the relation), while setting a relation parameter ("is epic of") should only narrow down the results?
...ttachments another team sends over from Jira. Much easier for everyone involved. True sync for 100% of Trello native fields Trello is one of the most popular work management tools out there, and more Unito u...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events