プロジェクト

全般

プロフィール

Vote #75185

未完了

Store the status name in the issue history

Admin Redmine さんが約4年前に追加. 約4年前に更新.

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

0%

予定工数:
category_id:
2
version_id:
0
issue_org_id:
16748
author_id:
54354
assigned_to_id:
0
comments:
2
status_id:
1
tracker_id:
2
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

Currently, @journal_details@ table only stores the @id@ of the standard issue fields in @old_value@ and @value@.

This leads to the Issue History displaying the current value of the @id@, and if that @id@ is deleted, the @id@ itself.

For example:

  • I change the Status from @New@ to @Accepted@. ** Issue History indicates: @Status changed from New to Accepted@.
  • The Admin then change the name of the status to @Just-Before-Accepted@. ** Issue History indicates: @Status changed from New to Just-Before-Accepted@.
  • Some time later, issue is closed and this status is deleted. ** Issue History indicates: @Status changed from New to 2@.

Displaying of the current name, or id, breaks the audit trail and the context under which the original action was taken.

One way of addressing this is to add @old_id@ and @new_id@ fields to capture the field relations (which if useful for linking, etc) and use the @old_value@ and @value@ fields for displaying.


journals

--------------------------------------------------------------------------------
Note that this affects _all_ standard list/enumeration fields, not just *Status*.

I've confirmed the behaviour (value changes to current value, or to @id@ when deleted)
* *Assignee* (deleted Group => @id@, deleted User => @Anonymous@),
* *Category*,
* *Priority*,
* *Target version*.

(I have only checked Issue fields, not Document, etc.)
--------------------------------------------------------------------------------

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

いいね!0
いいね!0