In mantis 2.4.0 (Schema Version 209), I can't get Changelog to work.
The project has versions configured:
An issue is set to be fixed in a version:
However, no changelog:
Yes, all screenshots show the same project. Any clue?
Changelog doesn't work
Moderators: Developer, Contributor
Re: Changelog doesn't work
Oomph, I thought the status "closed" would do the job. Thanks for the hint.
Is it possible to remove "Resolution" and just let Status "closed" (which is after "resolved" which had me assumed that the issue is solved) creating the changelog?
It is really amazing how everything in Mantis seem to take 10 clicks more for everything. Would be nice to have a quicker way to breeze through issues by finishing them with customizable buttons directly in "view.php" or even "view_all_bug_page.php".
Is it possible to remove "Resolution" and just let Status "closed" (which is after "resolved" which had me assumed that the issue is solved) creating the changelog?
It is really amazing how everything in Mantis seem to take 10 clicks more for everything. Would be nice to have a quicker way to breeze through issues by finishing them with customizable buttons directly in "view.php" or even "view_all_bug_page.php".
Re: Changelog doesn't work
There are some options to determine which issues are shown in change log.
You could write a custom function custom_function_overrride_changelog_include_issue, see https://www.mantisbt.org/docs/master/en ... cs.defined
You could also set
Patch submissions can be made in several ways. In the order of preference:
1. Send us a Pull Request on our Github repository [1]
2. Attach a GIT patch to the issue
3. Attach a Unified Diff, clearly specifying the patch's base release
Kindly avoid to upload entire modified PHP files.
Please make sure that your submissions adhere to our Coding Guidelines [2], if they don't your patch might be rejected.
[1] https://github.com/mantisbt/mantisbt
[2] http://www.mantisbt.org/wiki/doku.php/m ... guidelines
You could write a custom function custom_function_overrride_changelog_include_issue, see https://www.mantisbt.org/docs/master/en ... cs.defined
You could also set
Code: Select all
$g_bug_resolution_fixed_threshold = OPEN;
Submitting a patch is always a good idea, as it increases the chances of improvement eventually making it into MantisBT core. All contributions are welcome and greatly appreciated.Knubbi wrote:It is really amazing how everything in Mantis seem to take 10 clicks more for everything.
Patch submissions can be made in several ways. In the order of preference:
1. Send us a Pull Request on our Github repository [1]
2. Attach a GIT patch to the issue
3. Attach a Unified Diff, clearly specifying the patch's base release
Kindly avoid to upload entire modified PHP files.
Please make sure that your submissions adhere to our Coding Guidelines [2], if they don't your patch might be rejected.
[1] https://github.com/mantisbt/mantisbt
[2] http://www.mantisbt.org/wiki/doku.php/m ... guidelines