Multiple issueFunction customfield : Why ?

Related the Groovy Documentation, issueFunction is a customfield that can replace issue in JQL. Also, we use issueFunction in hasComments() instead of issue in hasComments().


  • Why do we have many occurrence of this customfield ?
  • In <Host>/jira/secure/admin/groovy/ViewScriptedJqlFunctions!default.jspa, we have 22 JQL Functions, but we have currentlt 59 issueFunction customfield. Why / How does it occurred ?
  • When this customfield is created ? On each Scripted JQL Function activation ?
  • Since the 59 customfields poluate the Bulk action, is it possible all of them excepted one ?


1 answer

Hi Vincent... this is I would add you as a watcher but I don't think you have logged in.

issueFunction is a custom field which just exists to use a different method of writing jql functions, as returning a list of QueryLiterals is way too slow.

There should only be one. I don't know yet under what conditions more than one is created... but yes likely it will be on plugin activation. It's safe to delete them all except one. Please could you watch the linked issue, I'll provide more updates there. Also could you comment on that ticket with the relevant version numbers.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,725 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you