REQ: Bulk assign of "Fix For"
It is common at the end of a release cycle to end up with a set of tasks that get pushed off to the next release. The process of changing the reference manually for all tasks, one at a time, is painful. Please consider addressing this use case.
Friday, April 2, 2004
I've recently started using FogBUGZ and I had to import a whole lot of cases from an old Excel spreadsheet.
This meant that I was going directly into the database and changing the id of the bugs to match my old system.
I can tell you that the database schema is pretty straightforward and simple to change, and didn't break anything when I made my changes.
So I would advise you to have a quick look in the database schema and see how it stores the "fix for" and "active" settings, and then write an SQL query to push back the active features to the next release.
Should be about a ten minute job.
Although I agree that this would be a handy feature to have in the software.
Saturday, April 3, 2004
Problem with that approach is that then there is no history record generated for the change, which breaks the idea of a full audit at the core.
Thursday, April 8, 2004
Fog Creek Home