Project

General

Profile

Actions
Copy link

Defect #24995

closed

Custom query - error 500 if irrelevant field chosen

Added by Yao Li about 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues list
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:
3.3.0

Description

Hi there,

Now I'm using redmine 3.3.0.

1. In the issues page, filter issues with tracker
2. Set columns in Options panel, choose a field which is irrelevant with the tracker
3. Click apply, server returns Redmine 500 error with below information

Internal error

An error occurred on the page you were trying to access.
If you continue to experience problems please contact your Redmine administrator for assistance.

If you are the Redmine administrator, check your log files for details about the error.

Back

Compared with 2.3.0 version, if a irrelevant field is chosen, the column just leaves empty in result page, no 500 error occurred.

Files

production.log (481 KB) production.log Yao Li, 2017-02-13 03:47
Actions
Copy link
 #1

Updated by Yao Li about 8 years ago

update .. should be error 500 in the subject ..

Actions
Copy link
 #2

Updated by Go MAEDA about 8 years ago

  • Subject changed from Custom query - error 404 if irrelevant field chosen to Custom query - error 500 if irrelevant field chosen
Actions
Copy link
 #3

Updated by Go MAEDA about 8 years ago

  • Category set to Issues list
  • Status changed from New to Needs feedback

I cannot reproduce the error in the current trunk.
Could you paste the error messages in log/production.log file?

Actions
Copy link
 #4

Updated by Shreyas Moolya about 8 years ago

Yao Li wrote:

update .. should be error 500 in the subject ..

+1

Actions
Copy link
 #5

Updated by Toshi MARUYAMA about 8 years ago

What do you mean "a field which is irrelevant with the tracker"?

Actions
Copy link
 #6

Updated by Yao Li about 8 years ago

Toshi MARUYAMA wrote:

What do you mean "a field which is irrelevant with the tracker"?

For example, we have trackers A and B, customized fields m,n,p,q. A uses m and n, B uses p and q.

1. Setup a query to display all tracker A issues
2. Choose columns m and n to display - it works well
3. Choose columns m, n, and p to display - server returns 500 error.

Actions
Copy link
 #7

Updated by Yao Li about 8 years ago

production log attached.

Actions
Copy link
 #8

Updated by Go MAEDA about 8 years ago

Yao Li wrote:

production log attached.

Please see line 52. It is obvious that the error was caused by a plugin named 'extended_fields'. I think that uninstalling the plugin will resolve the problem.

Actions
Copy link
 #9

Updated by Toshi MARUYAMA about 8 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to Invalid

Please contact plugin author.

Actions
Copy link

Also available in: Atom PDF