How do I create an own filter to be useable from gadget "favorite filters" then?

[Volker Thiel]

• we want to have a favorite filter "which issues are assigned to <USER>" actually?
• how do we create such a filter in general?
• how can we manage it to the favorite filter gadget?
• 3 project leads will use this gadget on dashboard
• can <USER> be an input field to this filter or must we have hardcoded usernames for every teammember?  (team is less then 8 members)

[Volker Thiel · Accepted solution]

Hi,

no more answers necessary. I found solution myself.

• creating filter and share it with administrator group
• using favortie filter or filter results gadget

[Alana Fernando · Accepted solution]

Hi @Volker Thiel,

First of all let me give you a suggestion that might reduce this work load. I suggest you to minimize this work load just by adding a Adding the Two-Dimensional Filter Statistics Gadget.

users you are mentioned are in 5 projects, you have to create only one filter that contain project/projects names. and make the filter shared and use it in each of your project leads dash board with selecting the created filter and issue type and assignee in XAxis and YAxis. 

• how do we create such a filter in general?

1. navigate to jira search
2. type assignee = <user name> JQL
3. Hit search

• how can we manage it to the favorite filter gadget?

For server Saving your search as a filter

For cloud Saving your search as a filter

• 3 project leads will use this gadget on dashboard

In this case you need to share the filter among other project leads.

Managing shared filters in server

Managing shared filters in cloud

• can <USER> be an input field to this filter or must we have hardcoded usernames for every teammember?  (team is less then 8 members)

As far as I know this is not possible. you have to add filter for each user. 

Refer: Advanced Searching 

Hope this helps 😊

[Volker Thiel]

Hi,

this gadget is a really good tipp

[Alana Fernando]

Glad to hear @Volker Thiel 😊  

[Bastian Stehmann · Accepted solution]

Hi @Volker Thiel,

you can create the filter by going to issues -> search for issues. 

There you can search for the issues you want to get, for example "assignee=currentUser()", so you will get all issues, that are currently assigend to you. You probably will add a and-clause to show only unresolved issues.

Then there is a "Save" Button that saves your query as filter. You can also share the filter with others by clicking on "Details" next to save.

When you go to Issues -> "Manage Filters" you can add the filter to your favorites by clicking the star at the beginning of the line.

If you add the Filter Favourites Gadget to your Dashboard, you should now see that filter there.

Other can find this filter when they go to Issues -> "Manage Filters" -> "Search" and then search by name or owner.

You can not add <USER> as input field, but currentUser() will always only show the issues of the user currently using this filter, so if you use it, you see your issues, if your colleague views it, he will see his issues. If you want to see it for your team members, you will have to create an individual query for each one or one that includes all usernames to see them all at once.

[PJ Wysota · Accepted solution]

There is quite good documentation on JQL: https://confluence.atlassian.com/servicedeskserver/advanced-searching-939937012.html

1. Fields - firstly look at JQL construction:

First - FIELD, then OPERATOR, then VALUE

Means that your case would look like:

Assignee [OPERATOR] [VALUE]

2. Operator - as you are looking for current Assignee - disregard all WAS-like operators as well as IS/IS NOT (as these references to EMPTY/NULL)

I would use =/!= or IN/NOT IN, depending on next point

3. Values

OK, and here is a real issue:

- with =/!= operators you can use ONLY targeting to specific user or "currentUser()" so - either You hardcode it for all single names or make it dynamic for "own filter" for all users logging in

- with IN/NOT IN operator You could do a bit more: 
-- multiple users - in brackets, comma separated)
-- membersOf("") - where in "" you put groups names
-- organizationMembers("") - specific for JSD (where Organizations are used)
Please not in this case You will have not the results of particular user, but a bunch of users - depending on setup.

[Volker Thiel]

Thanks...similar like my solution