-
Suggestion
-
Resolution: Low Engagement
-
None
-
None
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Currently we can do JQL commands like "assignee in membersOf(groupName) but there's no way of doing the opposite, I.E. customGroupPickerValue in groupsOf(assignee)
Use-case: when setting up a service desk under a single project to manage issues via Group Ownership, it'd be useful to create a "my tickets" queue which could show tickets that are assigned to the currentUser as well as unassigned tickets that are assigned to the user's group within a single queue. That way they could see quickly all the work available to them without having to browse through multiple queues (especially if they are in multiple groups)
- relates to
-
- Closed
[JSDSERVER-5003] JQL groupsOf(user), an inverse of membersOf(group)
Hi everybody,
If you are using Jira Server you can install the FREE app called JQL Booster Pack throught Atlassian Marketplace and use the requested functionality.
After install this app, you should be able to create a query using groupsOf() function, that will allow you to retrieve the groups the current user / the provided user belongs to.
This is the complete information of this JQL function:
Description:
Perform searches based on groups that the given user belongs to.
If any user is provided, it will return all the groups that the current user belongs to.
Syntax groupsOf()
groupsOf(user, ...)Available since v1.0.0-RELEASE Supported fields custom fields of type Group Supported operators IN , NOT IN* Unsupported operators = , != , ~ , !~ , > , >= , < , <=
IS , IS NOT , WAS , WAS IN , WAS NOT , WAS NOT IN , CHANGEDExamples:
• Find issues whose 'QA Team' group picker custom field value is a group that the current user belongs to:
"QA Team" IN groupsOf() • Find issues whose 'Dev Team' group picker custom field value is a group that 'John Smith' belongs to:
"Dev Team" IN groupsOf("jsmith")
Kinds regards.
Hi,
Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.
This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).
We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.
To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.
Regards,
Charlie
Jira Service Management, Server & Data Center