Project

General

Profile

Actions

Defect #18310

closed

Default issue columns don't follow the set order

Added by Anonymous over 9 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
UI
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
No feedback
Affected version:

Description

In the "Administration > Settings > Issue Tracking" page, we have the ability to select which columns are displayed by default and in what order they must be placed. However, running with 2.5.2 the column order is not applied to the issues list view.

Manually setting the column order in the "Options" expandable panel when viewing a list of issues works and the column order used for custom queries both work correctly, this only affects the default column order when using the "View all issues" view.

I'm unsure what version this issue started in, I was running 2.4.3 prior to upgrading straight to 2.5.2. No errors logged that I can see.

Actions #1

Updated by Jean-Philippe Lang over 9 years ago

  • Status changed from New to Needs feedback
  • Resolution set to Cant reproduce

Works for me with current trunk. I've added a test for that in r13583 and it passes.

Do you have plugins installed? Also, make sure that you reset the issue list (Clear button) after changing the default columns setting.

Actions #2

Updated by Anonymous over 9 years ago

Jean-Philippe Lang wrote:

Works for me with current trunk. I've added a test for that in r13583 and it passes.

Do you have plugins installed? Also, make sure that you reset the issue list (Clear button) after changing the default columns setting.

Hmm.. Thanks for the info. I have quite a few plugins installed, but none that modify the issue list view or the column sorting, so I didn't think they would make any difference here. I'll double check this in a clean install this evening and see that changes anything.

I did clear the column order after testing that in the issue list view though, I'm quite used to doing that thanks to the was custom queries work in the UI. :)

Actions #3

Updated by Jan Niggemann (redmine.org team member) over 8 years ago

  • Resolution changed from Cant reproduce to No feedback
Actions #4

Updated by Anonymous almost 8 years ago

I haven't been able to reproduce this issue.. Apologies for not doing this sooner, I was going through my list of reported/watched issues and noticed that this one was still here.

As far as I'm concerned, this can be closed off.

Actions #5

Updated by Go MAEDA over 7 years ago

  • Status changed from Needs feedback to Closed

Thanks for the feedback. Closing.

Actions

Also available in: Atom PDF