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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is happening in our test environment, also. I restarted JIRA in the test environment and we still see the error message.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.