Defect #13537

Filters will show issues with unused custom fields.

Added by Erik Jonsson over 4 years ago. Updated about 4 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Jean-Philippe Lang% Done:

0%

Category:Custom fields
Target version:2.4.0
Resolution:Fixed Affected version:2.2.1

Description

If I create a filter that looks for a particular value in a custom field,
issues that are in a project where the custom field has been removed
will show up as matches. This is strange and annoying! Why should a filter
match if the custom field is inactive in the project settings that
the searched issue belongs to?

Another way to explain this is that the results from this SQL-query
should not be returned when you search with a custom-field filter.

select 
    i.id, p.name, concat("\"", cv.value, "\"")
from 
    issues i, projects p, custom_values cv                             
where 
    i.project_id = p.id and
    i.id = cv.customized_id and
    cv.custom_field_id not in 
        (select custom_field_id from custom_fields_projects where p.id = project_id)
order by name, custom_field_id;

Associated revisions

Revision 12133
Added by Jean-Philippe Lang about 4 years ago

Filters show issues with unused custom fields (#13537).

History

#1 Updated by Jean-Philippe Lang over 4 years ago

  • Status changed from New to Confirmed

#2 Updated by Etienne Massip over 4 years ago

  • Target version set to Candidate for next minor release

#3 Updated by Jean-Philippe Lang about 4 years ago

  • Category changed from Projects to Custom fields
  • Status changed from Confirmed to Closed
  • Assignee set to Jean-Philippe Lang
  • Target version changed from Candidate for next minor release to 2.4.0
  • Resolution set to Fixed

The same happens if a field is disabled on a tracker. This is fixed in r12133, thanks for pointing this out.

Also available in: Atom PDF