Issue's custom fields don't appear on some filters and custom queries editor
|Status:||Needs feedback||Start date:||2008-07-18|
|Target version:||Candidate for next major release|
When you create an issue's custom field and mark it to be used on filters it works fine except in the following situations:
- Custom fields don't appear on the "View issues on all projects" page.
- You can go to a project and create a Custom Query using that field, but if you try to edit the query afterwards the field doesn't show up in the edit interface.
Note that the custom field I've tried in only allowed in some trackers.
#2 Updated by frank guthorel almost 9 years ago
I can confirm this issue.
Custom fields seem to be dropped when editing filters, and apparently a custom field is not available when using cross-project filters/queries.
This is a bit annoying - since this is mighty fine for checking in an overall list of projects what has to be invoiced for instance, or what is not billable - using custom fields Invoiced and Billable, for instance.
Any chance of incorporating this in a revision somewhere in the future?
For now, what does work - to have fi. Invoiced behaviour -- is using a a status Invoiced for an Issue. Only when invoiced does it become closed, so that way, it keeps showing up on MyPage. This is a good solution for account managers, but less so for developers, since their list grows longer and longer that way, until all said Issues are invoiced.
Well - it seems not to be too difficult an update from my perspective, but I could be wrong of course.
Thanks in advance for having a look.
#3 Updated by Stephanie Collett over 8 years ago
This is a very strange bug, but I was able to find a workaround for version 0.7.3 for custom fields that are included for all projects.
1. Create your custom query with the custom fields for a specific project and save (Do not check 'For all projects').
2. Edit the custom query checking 'For all projects' and save.
The custom query should work for all projects including the cross-project issue list. Do not edit the custom query or it will drop the custom fields.
#5 Updated by Daniel Felix over 4 years ago
- Target version set to Candidate for next major release
One suggestion of this could be to reload the issue fields after selecting "global filter".
Redmine couldn't provide filters which are systemwide, if the filter items won't be available systemwide.
Another suggestion would be, to throw out all projects which haven't these fields and just filter those projects which have this field enabled.
#7 Updated by Daniel Felix over 4 years ago
This one seems to be fixed in the 2.3 release:
•You can go to a project and create a Custom Query using that field, but if you try to edit the query afterwards the field doesn't show up in the edit interface.
This is still reproducible:
•Custom fields don't appear on the "View issues on all projects" page.
•If you create the Custom Query inside a project (and make it globally available) you can use in the "View issues in all projects" page but the custom field is not being uses anyway.
The points which are still reproducible seem to be legit. Only fields which are enabled for all projects should be selectable on this filters.