SOLVED: What serves the JQL "team()" function? ANSWER: Tempo Timesheets

Question

I was approached by a user complaining that a Filter had stopped working

He was getting "Unable to find JQL function 'team(jira-administrators)'."

Their Filter contained contained:

"... AND assignee in ("Blah Blah", team(jira-administrators))"

I advised him to use membersOf() instead, and he's gone away happy.

But I'm wondering what serves the team() function - I can't seem to find it online anywhere, and the user is convinced this was working before...

Anyone know, please?

UPDATE:  This is solved: please see Accepted Answers below.

Mirek · Accepted Answer

Hi @Darren

I suggest to look at the list of plugins. I suspect that this is related to Tempo or any other plugin that could use field like this e.g Advanced Roadmaps / Portfolio for Jira..

Darren_3xxj1j · Accepted Answer

I found the answer:

It's Tempo Timesheets.

Something interesting I found whilst troubleshooting this and getting to the bottom of it:

The client had evaluated Tempo Timesheets back in 2019 (using an Evaluation license) but had decided not to go ahead with it, and so the Evaluation License expired (back in 2019)

For reasons unknown, Tempo Timesheets had not been uninstalled since 2019 so it remained installed - with an expired 2019 Evaluation License - for the past 4 years.

The client is now in a Jira Upgrade process:
Stage first so they can thoroughly test to ensure critical functionality isn't broken somehow by an upgrade.
Tempo Timesheets - being a 4yo expired app - was uninstalled on Stage, and all evaluations over the following weeks passed.
As part of the final part of due-diligence ahead of physically upgrading Prod, the client had disabled Tempo Timesheets on Prod to surface anything obscure before they physically uninstalled the app during the Prod Upgrade.

Just one user reached out:  they had found something online that caused them to use Tempo Timesheet's team() function in their JQL rather than Atlassian's membersOf()

What was interesting for the client is that an app that expired 4 years ago was still serving its functions today.

Ah well - the nature of dealing with Complex Systems :)