Custom fields values are lost when changing the project on issue update
|Status:||Needs feedback||Start date:|
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
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
Database adapter mysql
#2 Updated by Etienne Massip about 5 years ago
- Subject changed from Updating issue, custom fields are not redrawn by changing the project and tracker to Custom fields values are lost when changing the project on issue update
- Status changed from New to Confirmed
- Target version set to Candidate for next minor release
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?
#4 Updated by Jean-Philippe Lang about 5 years ago
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?
#8 Updated by ko simo about 5 years ago
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.
#9 Updated by Daniel Felix over 4 years ago
- Affected version (unused) changed from 1.4.4 to 2.3.1
- Affected version changed from 1.4.4 to 2.3.1
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.
#12 Updated by Daniel Felix over 4 years ago
I found the line which rejects this.
I haven't seen any regressions to comment this line out. After commenting this out, the main application still works as expected.