View Issue Details

IDProjectCategoryView StatusLast Update
0011531mantisbtcustom fieldspublic2011-08-05 02:31
Reporteramoulton Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionduplicate 
PlatformUnixOSSolarisOS Version10
Product Version1.1.8 
Summary0011531: custom field value is lost on update
Description

I have a project with a custom field that has three possible values. When an issue is updated it loses the custom field value.

After some testing this is specifically When a new issue has been reported and the dafault value is selected (i.e. not left to get set to the value by default). When you then update the issue the custom field value is not highlighted and will then get lost if not highlighted by the updater.

Steps To Reproduce

On a project with a custom field that has several possible values:

  • report a new issue
  • make sure to specifically select what would be the default value
  • view the issue and select update
  • note none of the custom field values are highlighted
  • select update information
  • now note the custom field value is empty
TagsNo tags attached.

Relationships

duplicate of 0003767 closedgrangeway Enumeration Custum fields with html-special chars get unselected on bug-update 

Activities

amoulton

amoulton

2010-02-23 05:45

reporter   ~0024465

The above is wrong. After further investigation it seems that is the use of an ampersand chartacter in the list field that is causing this problem. Is that invalid character to use or dis this still class as a bug?

SL-Gundam

SL-Gundam

2010-11-15 17:52

reporter   ~0027370

Last edited: 2010-11-15 17:53

Still a bug. I fixed this sometime ago with a private patch. I'll add it here for the mantisbt 1.2.3 branch

I believe there was an issue like this 2 years ago aswell allthough i can't remember the issue number

atrol

atrol

2010-11-16 02:24

developer   ~0027373

SL-Gundam , confusing to me, or maybe blind at the moment.

1.2.3 : contains $t_custom_field_value = string_attribute( $t_custom_field_value );

1.2.x : removed call of string_attribute , see 0003767 and http://git.mantisbt.org/?p=mantisbt.git;a=commitdiff;h=76c9a79ef7d88a135e226088c167e90065ef9277

Your Patch: adds the call of string_attribute but you write it's for 1.2.3
Or did you mean it's for 1.2.x ?

dhx

dhx

2010-11-16 05:06

reporter   ~0027374

Thanks atrol, I think you're right in saying this was fixed with the changesets attached to 0003767.

atrol

atrol

2010-11-16 05:34

developer   ~0027375

Now I am even more confused

SL-Gundam adds one line to fix this issue 0011531
dhx removes the same line to fix another issue 0003767

Is this the game of patch ping pong?

Or just that simple, that some more changes together in 1.2.x will solve 0011531 and 0003767 .
If yes, SL-Gundam's patch is not needed or even better is removed (at least if we push out 1.2.4 in near future)

SL-Gundam

SL-Gundam

2010-11-16 11:30

reporter   ~0027381

My patch was meant for the 1.2.x branch.

But i think 0003767 is a better solution for the same problem. So please ignore my patch

atrol

atrol

2010-11-16 11:56

developer   ~0027382

Thanks for the feedback