Project

General

Profile

Actions

Defect #1499

closed

Issue filters based on custom fields cannot be saved

Added by Justin Waters over 16 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
2008-06-19
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

It doesn't look like you can save a custom filter that uses a custom field. While the save appears to work, the filter won't recognize the custom field when you click the link. If you attempt to edit the filter, the custom field isn't even available in the "add filter" box.

Actions #1

Updated by Jean-Philippe Lang over 16 years ago

Actually, queries with custom fields only work when inside a project but not on the cross-project issue list.
I'll try to fix it.

Actions #2

Updated by Ewan Makepeace over 16 years ago

+1
Just hit exactly the same bug. To illustrate we have added a custom field globally to all issues 'Sprint' with a list of defined values (June 08, July 08, Aug 08 ect). Now across all projects I should quickly be able to pull up who has closed what for the current sprint ect.
Unfortunately as mentioned the filter seems to work the first time but then not save, and the custom field is then no longer available for selection.

Actions #3

Updated by Mischa The Evil over 16 years ago

I have just tested this with a fresh checkout at r1725 and this issue seems to be fixed.
Looking at the SVN-log it seems to me that the custom fields refactoring in r1592 has fixed this issue.

Can anyone else confirm this?

Actions #4

Updated by Jean-Baptiste Barth over 14 years ago

  • Status changed from New to Closed
  • Resolution set to Fixed

Confirmed, it's fixed for a loong time

Actions

Also available in: Atom PDF