Why do I get the error message "Field 'issueFunction' does not exist or you do not have permission to view it."?

We are using JIRA v6.2.7 with ScriptRunner v2.1.7, and today we are getting the error "Field 'issueFunction' does not exist or you do not have permission to view it.".  This happens for all users we have tested.  We have filters and dashboards using ScriptRunner scripts, and this has been working until today.  To test this, when I try to create a filter, issueFunction is not available, but it is in the list of Custom Fields.

7 answers

This is happening in our test environment, also. I restarted JIRA in the test environment and we still see the error message.

Just saw another entry int the log file: 2015-01-15 13:49:59,728 http-bio-8080-exec-15 ERROR ##### 829x2876x1 148cy93 ###.###.###.159,###.###.###.37 /issues/ [jira.groovy.jql.ScriptedJqlFunction] Function scriptedFunction didn't have a data type, returning Issue. Possibly plugin not started yet

It is working now, as soon as we have a definite answer, I will post that answer here. Something with our field and screen schemes is the root cause.

We had made several changes before we saw the problem, when we undid all the changes, the problem went away. We are still trying to find out which of the changes caused the problem.

Adding global scheme context to the issueFunction field solved it for us.


Hi Anatolijs,

I am facing this issue as well. As suggested I have made sure the scheme context is set to Global mode.

It didn't solve my issue and keep getting the same error. By the way I am using curl from the command line.

The exact error is, "Field 'issueFunction' does not exist or this field cannot be viewed by anonymous users."

Any help is really appreciated.

When I said I am using "curl" I am using JIRA rest API services with curl.

Are you authenticated? Referring to "cannot be viewed by anonymous users." part of the error.

The JIRA project here is meant to access for all the users and hence anybody can view all the issues inside this project. Also I am able to access all the issue fields anonymously without any issue. It is only when I use this script runner's 'issueFunction' throwing the authentication issue.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,081 views 13 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot