プロジェクト

全般

プロフィール

Vote #72427

未完了

Custom fields values are lost when changing the project on issue update

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

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

0%

予定工数:
category_id:
2
version_id:
0
issue_org_id:
11731
author_id:
1172
assigned_to_id:
0
comments:
14
status_id:
10
tracker_id:
1
plus1:
0
affected_version:
closed_on:
affected_version_id:
71
ステータス-->[Needs feedback]

説明

When you change a project on issue updating, if the tracker available differ between projects and the project change-to dosen't have the tracker before the project's change, tracker was automatically default.
But custom fields are not redrawn.
However, re-select the project for the second time, to be redrawn.

About application's environment
Redmine-1.4.4
Database Mysql 5.0.95
Ruby version 1.8.7 (i686-linux)
RubyGems version 1.7.2
Rack version 1.1.3
Rails version 2.3.14
Active Record version 2.3.14
Active Resource version 2.3.14
Action Mailer version 2.3.14
Active Support version 2.3.14
Application root /var/redmine
Environment production
Database adapter mysql


journals

--------------------------------------------------------------------------------
Eventually got it (on trunk).

You mean that the values of the custom fields are lost on project change despite the fact that the fields are also tied to the target's tracker when automatically selected as a fallback if the source tracker is not tied to the target project.

Is that right?

--------------------------------------------------------------------------------
Yes. That is right.
Thank you.
--------------------------------------------------------------------------------
I can't reproduce with trunk:

* I have project A with defect and feature trackers, project B with feature only.
* Defect and Feature trackers have a "Resolution" custom field
* I have a defect on project A with a value for the Resolution custom field
* I change the project from A to B while editing the issue
* => tracker is defaulted to Feature but the Resolution value is kept

What am I missing?
--------------------------------------------------------------------------------
Nothing.

I'll reproduce again as I'm sure I triggered it and let you know.
--------------------------------------------------------------------------------
Actually I can't reproduce neither; I'm pretty sure I mixed up custom fields and Version/Category fields the first time :|
--------------------------------------------------------------------------------
I'm sorry, this isssue might be due to a plugin, could you try without anyone installed?
--------------------------------------------------------------------------------
I confirmed without any plug-in.

I am sorry. Condition is missing.

In the case of Custom field setting "For all projects" ON,
to switch the project (And also switched Tracker), the field will remain on the screen.
-> This custom field is set to not use in that tracker (which is automatically selected), so should disappear from the screen.
However, in the case of "For all projects" OFF, it disappears from the screen. This is the expected behavior.

Thank you.
--------------------------------------------------------------------------------
I can reproduce this on Redmine 2.3.1.

Ways to reproduce:
* Create Custom Field (CF)
* Create Project A (PA) with CF assigned
* Create Project B (PB)
* Create issue in PA and assign value to CF. Save.
* Edit issue, move to PB. Save. Field disappeared (as expected)
* Edit issue, move back to PA. Save. Field is empty.
* Expected: CF should hold back the content.

Any suggestions?

Best regards,
Daniel
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I think this is related to:
source:trunk/app/models/issue.rb#L447
--------------------------------------------------------------------------------
I found the line which rejects this.

source:trunk/lib/plugins/acts_as_customizable/lib/acts_as_customizable.rb#L146

I haven't seen any regressions to comment this line out. After commenting this out, the main application still works as expected.
--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
I think this issue is fixed by #22600, right?
--------------------------------------------------------------------------------


related_issues

relates,Closed,22600,Add warning when loosing data from custom fields when bulk editing issues

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

  • カテゴリIssues_2 にセット

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

いいね!0
いいね!0