nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

tempoEpicIssues() not working anymore?

Kathrine Lønning

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?

Accepted answers

Dave Meyer

Update 13 January 2017

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!

Dave Meyer

Senior Product Manager, JIRA

warning 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.

Original message

The 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.

Dave Meyer

Senior Product Manager, JIRA

All comments

Rahul Shah1

Facing the same problem. Any solutions please?

Jane Sherman

Same problem here. Very sad. The strange thing is I believe it was working 2 days ago. I just created a new board using this in the filter - definitely after 12/7.

Sue Marmion

This is broken for us as well. It seems to still be working ok for the boards, but it is not working in search issues. how about it Atlassian??? no response to another broken feature that we are counting on!!??

Christoffer Larsson

Same problem here!

Christoffer Larsson

I am having the same problem. Seems to have started around Dec 21 2016.

Relying heavily on tempoEpicIssues(), so hoping for a quick resolution.

Souni Breil

Same issue, feedback would be much appreciated!

Dave Meyer

Update 13 January 2017

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!

Dave Meyer

Senior Product Manager, JIRA

Original message

Thanks for your understanding and patience.

Dave Meyer

Senior Product Manager, JIRA

Souni Breil

Thanks Dave. But I tried to install tempo timesheets (for cloud) yesterday and even after install, the old filters didn't work. Do we need to change the syntax now?

Christoffer Larsson

I just tried the same thing and with the same result; still didn't work.

Dave Meyer

Hi guys,

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud