Vote #74381: Issue journals should be ordered by created_on, not id - redmineorg-copy202205 - Redmine

編集操作

リンクをコピー

Vote #74381

完了

Issue journals should be ordered by created_on, not id

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

ステータス:

Closed

優先度:

通常

担当者:

カテゴリ:

Issues_2

対象バージョン:

3.1.0_90

開始日:

2022/05/09

期日:

進捗率:

予定工数:

Redmineorg_URL:

https://www.redmine.org/issues/14881

category_id:

version_id:

issue_org_id:

14881

author_id:

3866

assigned_to_id:

comments:

status_id:

tracker_id:

plus1:

affected_version:

closed_on:

affected_version_id:

ステータス-->[Closed]

引用

説明

r10547 changes the ordering of journals in @IssuesController#show@ from @created_on ASC@ do @id ASC@, is there a specific reason for this? Ordering by ID is probably right in most cases, we have a Jira import where this is not the case.

journals

This was changed because journals may have the same created_on value. We could use @created_on ASC, id ASC@ instead to fix your issue but importing journals in chronological order would have been a better option :/
--------------------------------------------------------------------------------
Ah, because of the split public changes/private notes journals? I understand.

@created_on ASC, id ASC@ would work, thanks!
--------------------------------------------------------------------------------

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

--------------------------------------------------------------------------------
#61 note order is strange.
#61#note-5 is oldest.

#61#note-5 -> #61#note-4 -> #61#note-3 -> #61#note-2 -> #61#note-1 ->
#61#note-6 -> #61#note-7 ...
--------------------------------------------------------------------------------

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

related_issues

duplicates,Closed,17852,Issue journals should be ordered by created_on, not id
duplicates,Closed,18440,Journals could be ordered using the create_on attribute instead of the id