Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: tracker.moodle.org
-
Labels:None
-
Environment:jira-admin user
Description
Today, after 1.7 release, I've marked it as released in Jira. Automatically all the pending tasks/bugs... pointing to 1.7 have been moved to 1.7.1 Cool!
Then I've tried to edit current 1.7 filters in order to add 1.7.1 to their parameters but I've discovered that it's impossible, because the author is MD and it seems that one admin cannot edit filters created by others. So filters are now showing incomplete info.
I think it would be great if any administrator could change any of these public filters. This can be achieved by:
- Some option inside Jira I haven't been able to find.
- By using one common "admin" account to handle shared filters.
Ciao 
Activity
- All
- Comments
- History
- Activity
- Source
- Test Sessions
I suppose it's relative to it : the link "Moodle 1.8.x bugs" in the head of the tracker (and so, the associated filter) doesn't include bugs declared for 1.8.5, and/or having fix version = 1.8.6 
All global filters have been moved to "Filter Manager" account, so I guess we can safely close this. If new global filters are created by other accounts (xxxxx) we have the possibility to move them at any moment with something like:
update searchrequest set authorname = 'filter manager' where authorname='xxxxx' and username is NULL;
Ciao
Hi Michael. I guess we can safely close this, correct? I've seen that next version of Jira introduces some changes so admins can edit anything. But current approach (Filter Manager user) can continue being used after upgrade IMO.
Resolving as fixed. Ciao
You're right Eloy, there is no way to update a global filter created by someone else. MD & I have stayed on top of global filters by creating new filters when moving to the next version (I've created filters for 1.7.1.) I'm not sure it's worth the effort to create and manage a shared login for this purpose given how easy it is to create new filters.
Probably best to log a request with Jira for admins to have shared responsibility for global filters.