Defect #7144

custom queries making use of deleted custom fields cause a 500 error

Added by Gauthier Delamarre almost 10 years ago. Updated over 9 years ago.

Status:ClosedStart date:2010-12-21
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Custom fields
Target version:1.0.5
Resolution:Fixed Affected version:1.0.4

Description

Quite simple to reproduce:

1) create a custom field
2) create a custom query including this custom field in its columns selection
3) delete the custom field
4) run your custom query

As you cannot run it anymore, you also cannot delete it...

Associated revisions

Revision 4553
Added by Jean-Philippe Lang over 9 years ago

Fixed: 500 error on issue query grouped by a custom field that was deleted (#7144).

History

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

  • Status changed from New to Resolved
  • Target version set to 1.0.5
  • Resolution set to Fixed

After digging around (stack trace would be appreciated, see SubmittingBugs), I got a 505 error when the custom field was used to group the query results. Having it in the selected columns doesn't produce any error.
The problem that I was able to find is fixed in r4553.

#2 Updated by Jean-Philippe Lang over 9 years ago

  • Status changed from Resolved to Closed

Merged in 1.0-stable.

Also available in: Atom PDF