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
too much history for custom fields
Moderators: Developer, Contributor
Re: too much history for custom fields
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.
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
Re: too much history for custom fields
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 ?
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 ?