Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,317
Community Members
 
Community Events
165
Community Groups

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

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?

3 answers

1 accepted

2 votes
Answer accepted

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. 

 

Thanks for your quick reply, Jamie.

This perfectly answers my question!

Hi, thanks for sharing. Having some doubts here. How come these queries are bringing for my project different results

  • issueFunction in linkedIssuesOf("filter=34148") AND type = story
    -> brings 75 results 
  • issueFunction in linkedIssuesOf("filter=34148", "is epic of") AND type = story
    -> bring 155 results
  • While issueFunction in issuesinepics("filter=34148") AND type = story
    -> Also brings 155 (which seems to be the correct)

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?

Any ideas?

The 2-nd paramter of linkedIssuesOf is optional. If omitted the function returns all kind of issue links. 

That's what the documentation says ("With no link name argument, will search for the linked issues whatever the link type"), but as per ALam7, that's not what I get. I only get all the epic's children if I include "is epic of".

My interpretation is that "is epic of" is implemented as a special case for 'link name', given it is actually a different kind of link within Jira itself.

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

Marketplace Partner Spotlight: AppLiger

This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity.    Atlassian:...

383 views 0 7
Read article

Community Events

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

Events near you