When I go to "advanced search" and enter:
Field 'issueFunction' does not exist or you do not have permission to view it.
What do I need to enable to run this JQL command?
We have recently released a feature in ScriptRunner for JIRA Cloud that now supports the kind of JQL Function queries you were looking to do.
You can find more information here: http://scriptrunner-docs.connect.adaptavist.com/jiracloud/enhanced-search.html
I hope that helps!
We implemented commented as an alias you can use in the regular search page as well as the Enhanced Search page.
See http://scriptrunner-docs.connect.adaptavist.com/jiracloud/jql-aliases.html for more information, particularly the table at the bottom of the page.
@Jon Bevan [Adaptavist] @jamie_Echlin
i have installed this in jira cloud and synced all issues in jira cloud.
I am site-admin.
but i am still getting same error in advanced search-
"Field 'issueFunction' does not exist or you do not have permission to view it."
it works in SR enhanced search.
There is no option Disable and enable in Jira cloud!
Can you help to resolve this issue?
Hi Raju, you are correct, JQL Functions provided by ScriptRunner for Jira Cloud only work on the Enhanced Search page, it is not possible to use them in Jira's own issue search page. However, you can create and share filters from the Enhanced Search page so that you can use JQL Functions in queries that power Agile boards etc.
Using issueFunction in the Escalation Service in Cloud is not currently possible. However, if you create a filter (e.g. 'My Escalation Service Filter') for your query using the Enhanced Search Page, then you can reference that filter within the JQL field on the Escalation Service page using filter = 'My Escalation Service Filter'
I hope that helps,
Hi @Jon Mort (Adaptavist)
We're using JIRA Cloud right now in our project. We split our space for several projects per platforms. We really need to reach out a lot of issueFunctions like as linkedIssues(), etc., which included in Script Runner.
Can you provide please the ETA of resolving the issue of support JQL functions on the JIRA Cloud?
We'd like to align our activities depend of your answer.
Thank you a lot.
with best wishes,
Hi @Kirill Romanov,
We are working on it at the moment. It is not a simple solution and we need to be fully comfortable with it before we launch it. The functionality won't be exactly the same as in the server because the Connect Framework gives us different extension points to the plugin system in Server. I can't commit to a date, but I would expect a launch to be weeks rather than months away.
Hi @Kirill Romanov
We are currently testing the first part of the JQL feature. I don't want to commit to a date because it has already taken longer than we anticipated. I stated weeks in the comment above and failed to deliver on that . Having said that it is likely that we will be able to launch in the next week or two.
We know this feature is important to many customers which is why we want to get it right.
ok @Jon Mort (Adaptavist) this thread is incredibly confusing.. should the function `issueFunction in commented` work on JIRA cloud or not? from this thread i get the impression that script runner isn't currently working on the cloud.. but then it also implies that it's not working on the hosted version either
@Kirill Romanov, @abdullah bakhach, @Matthew Vanderzee, @Jesse Sanford, @Nikola Marić, @Ostap Naida, @Amir Primov (sorry if i missed anyone off).
We launched the first part of this functionality this week. See http://scriptrunner-docs.connect.adaptavist.com/jiracloud/jql-aliases.html for details. There is an initial setup stage to synchronise the issues (similar to a re-index) but from then you can use aliases like
issueLinkType in ('Blocks', 'Duplicate') and
numberOfAttachments > 0 AND attachmentType = 'jpg'
Please give it a try and send us any feedback. The next part of the functionality with more complex queries is coming soon.
The functionality for subtasksOf(subquery) will be weeks away. You can see what we support right now here: http://scriptrunner-docs.connect.adaptavist.com/jiracloud/jql-aliases.html
Depending on what your query is you may be able to workaround with the aliases we have and a filter.
That's awesome news, Jon! Thanks for sharing...
For the initial sync process, is there any effect on the data that the Alias sync process is touching? Or is it just reading the data (not writing)?
What adverse effects should I expect if the ScriptRunner doesn't have read/write access to all of the projects within my JIRA instance and I trigger the sync process?
Again, really excited for these changes. Cheers!
The sync process writes properties to issues so ScriptRunner needs both read and write permissions (which it asks for on install). If the ScriptRunner user doesn't have write access then search results will possibly be incomplete and there will be no indication that is the case.
If you can restrict your search to just a single project or group of projects you can write a query to save as a filter that finds all parent issues that are closed. Once you have that filter you can then use issueType = subtask AND parentKey in FILTERNAME (or something like that - i can't test it right now)
Yes, you should be able to use issueLinkType to find issue that are linked to an Epic, however if you want to restrict which Epics they are linked to you'll need to wait for the next release of ScriptRunner for JIRA Cloud.
We are actively working on completing the functionality required to provide support for the "issueFunction" queries that ScriptRunner customers are used to. Our current estimate is that this will be released in the next few weeks.
I can't be more specific other than very soon. We are in the final stages of testing so it will be weeks not months. The funcitonality will not be exactly issueFunction, but should cover all those use cases.
If you would like to be a beta tester please email me jmort [at] adaptavist.com
Any update on the issueFunction for JIRA Cloud? I really need this feature, that's the only reason why we purchased this plugin.
It's been more than 3 months since the last "weeks not months" update...
UPD: I did find a workaround for my case. Even though Jon Bevan writes above "if you want to restrict which Epics they are linked to you'll need to wait for the next release of ScriptRunner for JIRA Cloud", I managed to get it to work.
I enabled ScriptRunner Enhanced Search (http://scriptrunner-docs.connect.adaptavist.com/jiracloud/enhanced-search.html) and created a query looking like
issueFunction in issuesInEpics("labels = test_label“)
then, I saved it as a filter and it was successfully converted into something like
issue in (TP-2, TP-1)
Thank you Jon!
Still, that's a bit of an ugly solution in terms of performance, as the JIRA filter with hardcoded IDs is being updated every minute behind the scenes. What if we have a few hundreds of such filters...
So, is introducing issueFunction or a similar concept for JIRA Cloud still in the plans?
Enhanced Search IS the JIRA Cloud equivalent of issueFunction.
But I agree with you! :D If you can think of a better solution that works within the confines of a Connect Add-on then please let us know!
We've recently optimised the way we perform the filter synchronisation so that it only runs if your JIRA instance is actively being used (ie no synchronisation happens when you've all gone home from work or out for a long lunch).
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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!
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