Well, all I know is you need to use 'target version' which can only be used if you click advanced report when entering a new defect. Still not sure why this isn't on the normal report or how to get it there....
Hi,
Hmm... I have the target version combobox even on the simple report...
Changelog : Manage Configuration > Workflow Thresholds > OTHERS > View Change Log. (Configurable per user types.)
Roadmap : I think I always had it visible. I actually had to modify the php manually to hide it.
---fixed_in_version is what changelog is driven off of.
---target_version is where roadmap is pulling from.
Both these fields are populated off (get drop down from) the mantis_project_version_table. Roadmap looks for projects and project versions which are not marked as released and have unresolved bugs. changelog does the opposite -- looking for bugs with closed status.
If nothing is working, make sure you have versions on each of your projects
roadmap --> manage --> manage projects --> create a new project --> Mark project as in development --> roll down the page to enter the versions for that project --> make sure version is not set to released.
changelog --> manage --> manage projects --> create a new project --> Mark project as in development --> roll down the page to enter the versions for that project --> make sure version is set to released.
repp wrote:Well, all I know is you need to use 'target version' which can only be used...
joan wrote:
Changelog : Manage Configuration > Workflow Thresholds > OTHERS > View Change Log. (Configurable per user types.)
zhirsr wrote:
changelog --> manage --> manage projects --> create a new project --> Mark project as in development --> roll down the page to enter the versions for that project --> make sure version is set to released.
And changelog page is still blank.
I surf a bit through search, but found nothing, and forum is very big (maybe i used wrong keywords)
The key is to have a version defined that is unreleased. One then sets issues to be resolved in the target with the same version number. Issues that have not been resolved stay in the Roadmap under that version number. Once they are resolved they get a line through them and they show up on the changelog under the same version.
So:
1) Define a version
2) Edit it so that is marked as "unreleased"
3) Update issues to the project in question to be targeted with the same version
Am still not clear how to assign the change log for the Mantis installed in my system. Followed the steps mentioned here. But all i can see is a blank page when i hit the change log link. Can anybody explain it little bit clear from the scratch???? Please provide the steps to be followed to initiate the change log.