too much history for custom fields

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
atrol
Site Admin
Posts: 8366
Joined: 26 Mar 2008, 21:37
Location: Germany

too much history for custom fields

Post by atrol »

when I report a new issue with custom fields, history is written for every field.
Is there a way to avoid this?
I want history only to be written when custom fields are updated
Please use Search before posting and read the Manual
atrol
Site Admin
Posts: 8366
Joined: 26 Mar 2008, 21:37
Location: Germany

too much history for custom fields

Post by atrol »

what do others think?
Is this behaviour a bug or a feature?
Please use Search before posting and read the Manual
vboctor
Site Admin
Posts: 1293
Joined: 13 Feb 2005, 22:11
Location: Redmond, Washington
Contact:

Re: too much history for custom fields

Post by vboctor »

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.
Migrate your MantisBT to the MantisHub Cloud
atrol
Site Admin
Posts: 8366
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: too much history for custom fields

Post by atrol »

I created the report

I don't know much about internal things of Mantis, but I think if custom fields would be treated like any standard field, there would be no need to disable and enable a function.

Nevertheless, I would be very happy to have your quick solution, may be I can hope for 1.1.2 ?
Please use Search before posting and read the Manual
Post Reply