プロジェクト

全般

プロフィール

Vote #75899

完了

Moving column to top of "Select Columns" results in loss of all other column selections

Admin Redmine さんが3年以上前に追加. 3年以上前に更新.

ステータス:
Closed
優先度:
通常
担当者:
-
カテゴリ:
Issues_2
対象バージョン:
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
2
version_id:
88
issue_org_id:
18777
author_id:
7914
assigned_to_id:
1
comments:
2
status_id:
5
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
81
ステータス-->[Closed]

説明

Workflow to reproduce:

choose a parent project that has sub-projects, click in Issues

by default, six columns are shown

expand options -> choose "Project" -> click right arrow to move it to "Selected Columns"

click the double up arrow (or click single up arrow multiple times) to move "Project" to the top of "Selected Columns"

click Apply

Expected: seven columns with "Project" being the first column after the issue id.

Result: only the Project column stays selected. The page, when it returns, has a column for Project and the issue id, but all the other columns are no longer displayed.

h2. Further Information

After more digging, its worse than just moving it to the top. Every time you move a column up in "Selected Columns" you lose the columns under it as selected when you click apply.


Environment:
Redmine version 2.6.0.stable
Ruby version 1.9.3-p484 (2013-11-22) [x86_64-linux]
Rails version 3.2.21
Environment production
Database adapter PostgreSQL
SCM:
Mercurial 2.8.2
Filesystem

Redmine plugins:
redmine_checklists 3.0.2
redmine_drafts 0.2.0


journals

Fixed in r13869, thanks for pointing this out.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------


related_issues

duplicates,Closed,18788,Not all columns are saved after their reordering in a custom query

Admin Redmine さんが3年以上前に更新

  • カテゴリIssues_2 にセット
  • 対象バージョン2.6.1_88 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0