We have been using this filter in a Project Board for over a year, and it stopped working yesterday/today.
issue in ("Epic-ID") OR "Epic Link" = "Epic-ID" OR parent in tempoEpicIssues("Epic-ID") ORDER BY Rank ASC
Error message: Unable to find JQL function 'tempoEpicIssues("Epic-ID")'.
Any changes this week related to the tempoEpicIssues() function?
I'm pleased to announce the
parentEpic function is now available in JIRA Cloud.. Searching with
parentEpic will return all the issues in the specified epic(s) AND their sub-tasks. The syntax is a little bit different than a standard JQL functions – it's more like searching with a field. So
project = JRA and parentEpic = JRA-123
will return all issues and sub-tasks in the JRA project that are in the JRA-123 epic. The function also supports the
!= , IN , and NOT IN operators. So you could also search something like
project = JRA and parentEpic in (JRA-123, JRA-456)
and you will get all issues and sub-tasks in either the JRA-123 or JRA-456 epics.
Refer to the documentation for more information. Happy searching!
Senior Product Manager, JIRA
Note: If your JIRA Cloud instance currently has a license for Tempo Timesheets, the
tempoEpicIssues() JQL function should still be available. You can manually change your filters to use the
parentEpic function, or wait until they are automatically updated as part of the migration to Tempo's new Cloud technology platform.
tempoEpicIssues function was provided by a paid third-party add-on called Tempo Timesheets that was previously pre-installed in JIRA Cloud. Using this add-on required purchasing a license from the Atlassian Marketplace, but due to an error this JQL function was available even if the add-on was not licensed.
As part of ongoing efforts to improve reliability, performance, and security for our JIRA Cloud offering, this add-on is no longer pre-installed on JIRA Cloud instances that do not have an active license for it, which is why the JQL function is no longer available.
We are working hard to implement a native JQL function developed and supported by Atlassian that provides the same functionality that you will be able to use to replace
tempoEpicIssues. We expect to release this in the next couple weeks.
Thanks for your understanding and patience.
Senior Product Manager, JIRA
The new version of Tempo Timesheets for JIRA Cloud built on the new technology framework does not include the tempoEpicIssues function. We've developed a replacement for Tempo customers and non-Tempo customers alike and we are doing our best to get it released as soon as possible.
Unfortunately we did not realize that there was a licensing issue that allowed the function to be used on instances that did not have a license for the old version of the add-on, so when we removed the add-on for instances without licenses, the function stopped working. At this point, it will be faster for us to roll forward with our native replacement. I will comment again here once it's shipped.
Thanks for the fix. One small issue. I use this for creating swimlanes on a scrum board. When I edit the filter for the swimlane if I don't capitalize the key value, I get an internal server error when I try to view the board.
parentEpic in (api-27) vs. parentEpic in (API-27).
I tested this with other queries and the small letters work fine.
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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