Actions
Defect #7144
closedcustom queries making use of deleted custom fields cause a 500 error
Start date:
2010-12-21
Due date:
% Done:
0%
Estimated time:
Resolution:
Fixed
Affected version:
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...
Updated by Jean-Philippe Lang about 14 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.
Updated by Jean-Philippe Lang about 14 years ago
- Status changed from Resolved to Closed
Merged in 1.0-stable.
Actions