|
[
Permlink
| « Hide
]
Salar Mesdaghinia added a comment - 21/Oct/05 05:39 AM
I do not mean sharing filters that already is there
Thanks for the suggestion! We always like to hear how customers think Jira can be improved.
Cheers, I have problem that couple of persons have created shared filters and then they have left our company. Now nobody can delete the filters, also nobody (including administration) can even delete the users, as they have these shared filter ownerships.
I see only a dirty way how to solve it: I must change user's passwords to something I know and then I can log in as these users and then delete filters. Any better solution? Unfortunately at the moment there is no better solution (other than change them directly from the database).
Sorry for the inconvenience in the mean time. Cheers, I also have the same problem, a user left our compagny and is the owner of shared filter.
I can not log with is account to change the password, because to log to JIRA we are using a single sign one authentification. This user is no more in the repository. I tried to update the database, but it doesn't work. JIRA is more and more used in our compagny, I suppose I will have often this problem. I am waiting for a solution for the Administrator only. Thx I have the same "ex-employee as owner of shared filter" problem, but I will also add two other issues that I am hoping this may fix.
1. Staff member and owner of team filters moved to another department, therefore he should not have access to certain projects and items. The only current solution is for him to remove his filters, and a new staff member re-create them. However, this changes the ID of the filter, and every portlet that uses that filter is now broken as well. This means every team member has to update their dashboard. 2. The Risk Plugin requests two saved filters for it's use. (It used the column order on those filters to order it's own display items.) However, they just make my filter list larger with filters that I am never going to use. I would like to be able to define them via admin screen, or be able to give them to a role account login. (Like the limited permission account I have for xml-rpc / SOAP scripts) Carole,
We also have the same issue of using a single sign on so we are unable to change the password. Would you be kind enough to tell me what did not work for you when you tried to change the database? We have not yet attempted to modify the database and would liek to know the type of issues we may encounter. Thank you in advance for your responce. Thanks again and have a great day. Thanks, Stacy,
Since January, by changing directly in the database it's work fine. // Remplace of the owner by another one, on ONE filter (ID= id of the filter) The update is taken into account immediatly, no need to restard the serveur or do a reindex. I hope it will help you, it is very easy to do. We have the same issue with not being able to move filters to a new user. Also to through another item in the mix. JIRA now has the ability to use Roles instead of Groups in defining permissions. I would really be nice if Filters could be assigned to roles and the person with that role, say FILTER ADMIN could then modify and administer the Filters on the server.
It seems that this request is something that is a no brainer for Atlassian to emplement i.e. transfer of Filters to different users. And there are are compelling reasons for them to get this done asap. I have a slightly different use case for this, we have several users who maintain shared filters that are used in portlets exported to confluence. It's a pain to have to track down the person who originally created the filter and ask them to tweak the column order.
Adding my vote. When staff leave, or change positions, it's a pain to have to modify the database by hand. Any mechanism to alleviate this is welcome.
We have to same problem, staff in charge of maintaining JIRA is leaving. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Major
Ability for global ownerity of filters (or at least changing the filter owner)
