We have a JQL used issuesInEpics and as simple as it is, but it now return none issues, is there some way I can check what's the problem? any logs I can check?
The JQL is like this:
issueFunction in issuesInEpics("project = AFB and status = 'Open'")
Hi @Haishen
Have you tried fully re-indexing your Jira instance before running the JQL Query? If not please do so.
Once you have finished re-indexing your instance, please run these two JQL Queries,
issueFunction in issuesInEpics("project = DEMO AND status = 'To Do'")
and
project = DEMO AND "Epic Link" is not EMPTY AND status = 'To Do'
and please share the output.
I am looking forward to your feedback.
Thank you and Kind regards,
Ram
Hello,
Has anyone found a resolution for this issue? I have the same problem, and Adaptavist support has no idea how to resolve it.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Which issues do you expect to be returned? @Radek Dostál posted the explanation of the currently used JQL function - maybe you need something else?
There is no Log for JQL, only Syntax correction. The syntax is fine though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We don't know what you expect to find, what it shows you instead, nor frankly what you even are asking about due to spelling typos, could be anything as far as I can guess.
Unless you have general problems with indexes it probably comes down to what the function does, according to https://docs.adaptavist.com/es/latest/features/jql-functions#issuesinepicssubquery:
This function allows you to find issues related to epics found by the subquery. For example, find all stories for open Epics in a project:
issueFunction in issuesInEpics("project = DEMO AND status = 'To Do'")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I can tell what the original poster's issue is - "but it now return none issues", it seems fairly obvious that this is not what they expect or else they would not be asking a question. So it seems issuesInEpics is incorrectly returning no results when the query passed to it does match Epics which do have child issues.
As it happens, I have the same issue. Using ScriptRunner Enhanced Search, I have a query using issuesInEpics that returns zero results. When I run the sub-query in Jira, it returns 762 Epics, and when i examine a sample of those Epics, they have child issues. I am using Jira Cloud.
Can anyone explain why this is not working? There definitely seems to be a mismatch between the results returned by teh sub-query, and then no results being returned when that same query is wrapped in an "issuesInEpics" function.
(BTW, the link you have posted is not working)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rude? Have you noticed "edited"? Do you know that links can get broken over time because the site restructures or the page is removed/changed?
Why and how can I explain what is not working, when I have no idea what you are querying for and what data you have on your cloud. As you might have noticed I am also not affiliated with adaptavist so I have access to about the same information as you do when it comes to function descriptions. Not only can I not solve your cloud issues, I also really don't care to, win win.
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.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register NowOnline 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.