View Issue Details

IDProjectCategoryView StatusLast Update
0009235mantisbtbugtrackerpublic2010-04-23 23:22
Reporteratrol Assigned Tovboctor  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Product Version1.1.1 
Fixed in Version1.2.0rc1 
Summary0009235: history should not be written for custom fields when a new issue is created
Description

when I report a new issue with custom fields, history is written for every field.
I want history only to be written when custom fields are updated

Additional Information

from: www.mantisbt.org/forums/viewtopic.php?f=3&t=4795

vboctor on Jun 06, 2008 2:33 am
This is not a bug, but it is something that can be enhanced to be consistent with native fields. The reason for these entries is that internally the issue is added and then the custom fields are set on it. The fix would be to add a history_disable() and histoy_enable() APIs and do the following:

  1. Create the issue.
  2. Call history_disable()
  3. Set all custom fields.
  4. Call history_enable()

Please report an issue in the bug tracker and include the above suggestion and link to this forum thread.

TagsNo tags attached.

Activities

giallu

giallu

2008-06-06 06:17

reporter   ~0018029

I am not sure I really like the history_enable/disable method, but I'd need to look at the code to propose a sensible alternative.

atrol

atrol

2009-06-26 12:30

developer   ~0022273

Seems to be fixed in 1.2rc1

vboctor

vboctor

2009-06-26 12:43

manager   ~0022274

Based on @atrol feedback, I will mark as fixed for 1.2.0rc1.

msae

msae

2009-11-05 10:22

reporter   ~0023598

Last edited: 2009-11-23 03:50

The problem still occurs in version 1.2.0rc2 with user defined fields of the type MultiSelectionField. All other field types work fine.
-> see http://www.mantisbt.org/bugs/view.php?id=11209