[#JRA-6985] Project-level Filters

JIRA

Project-level Filters

Created: 13/Jun/05 03:44 PM Updated: 15/Jan/08 07:55 AM

Component/s:

Filtering & Indexing

Affects Version/s:

3.12.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-9997 Allow administrators to manage filters owned by other users

JRA-6561 Administrators should be able to delete all filters

JRA-6490 permission to un-share filters

~~JRA-1195~~ Allow editing of others saved filters

This issue is related to:

JRA-6527 Allow filters to be built upon other shared filters (combined filters)

Participants:	Andy Armstrong, Bart Selders, Melissa, Nick Minutello and Sakari Maaranen
Since last comment:	32 weeks, 3 days ago
Labels:

Description

« Hide

Currently the filter-sharing is something we use a lot. And it works really well.
However, the problem with sharing the filters is that only one person can modify them - and that they can only be shared with one group.
Ultimately, the filters are owned by a user.

What would be nice is if you could save filters at the Project Level - and anyone who is a project administrator can Manage them.
They would be public by nature - ie if you can browse the project, you can see the filters.
I guess they would also be for that project only...

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Nick Minutello added a comment - 13/Jun/05 03:45 PM

I meant to add - you would want to be able to see them (ie a tab) on the Project Dashboard.

[ Permlink | « Hide ]

Bart Selders added a comment - 14/Jun/05 04:46 PM

Nick, Exactly. I can't agree more. This is what I meant in JRA-1340.

[ Permlink | « Hide ]

Andy Armstrong added a comment - 19/Dec/05 05:04 PM

We have exactly this problem too. We have a number of shared filters for our team to use, but currently only the person who created them is able to edit them. When that person is on vacation then nobody can change them. Since these filters are a team resource, it would be ideal that all project administrators would be able to edit them.

For now, our workaround seems to be to create a new user just for this purpose. Then when an admin wants to change a shared filter they have to:
1. Log out
2. Log in as the shared filter user
3. Make the changes
4. Log out again
5. Log back in as themself

While this is possible, it is pretty painful. I would much prefer to see project filters shown as an aspect of a project, as components and versions are currently. It would also make sense to have some system wide filters that use only global values (e.g. "My issues this week", "My unresolved issues").

An alternative for us would be to allow system administrators to edit shared filters created by another user. Since they are administrators that doesn't seem unreasonable. However, I'd prefer the idea of project filters.

[ Permlink | « Hide ]

Andy Armstrong added a comment - 22/May/06 01:26 PM

This topic just came up again on the Atlassian forums:

http://forums.atlassian.com/thread.jspa?forumID=46&threadID=11445

Any news as to when this feature can be implemented? It strikes me as very odd to leave administrators so powerless to control shared filters.

[ Permlink | « Hide ]

Melissa added a comment - 02/Jun/06 04:55 PM

I've received several requests to modify the sharing of filters, as many of our users make their filters 'global' instead of limiting to their group. It would be handy to be able to simply go in and update the filters to make sure other users aren't being spammed with too much information.

[ Permlink | « Hide ]

Sakari Maaranen added a comment - 15/Jan/08 06:23 AM

Several people in our organization has the need to share project-specific filters on a project-specific manner.

Our project teams are coming up with various kinds of very useful filters for that project and that team at that particular time, but those filters are not useful for other projects.

So, we need shared filters for the project team. Global filters alone are definitely not the answer because they are far too wide. Our organization may have dozens of projects simultaneously with different people. Different projects need different filters for themselves, but not for every other project.

At least these levels of filtering are needed:

Global shared filters (manageable by JIRA administrators)
Project-owned shared filters (visible for everyone in that project, manageable by the project administrators)
Personal filters (manageable by individual users)