|
|
 |
Editing committed file list We have integrated CVS with fogbugz, and have a question about changing the list of commits to a case. For example, what do you do when a developer accidentally commits a file with the wrong BugzID? There doesn't seem to be any way to fix it. The same can be said if he forgets to include the BugzID; how can you add in the file to make that list thorough and accurate?
Philip Yurchuk
The only way to edit these things is in the database table itself... CVS...
Michael H. Pryor
Wouldn't the database to be modified (in my case) be MySQL? Or are you saying that FogBUGZ somehow queries CVS to get the list of checkins? I thought that upon commit, CVS runs the Fog Creek-supplied perl script, which connects that file/version to the specified case within the database, and from then on queries the database. If that were true, FogBUGZ could have a screen to add/edit/delete files/versions associated with the case. This would allow project managers to keep that list thorough and accurate.
Philip Yurchuk
Just an opinion, but the trouble with adding screens to allow people to change things is that that people will as often when they shouldn't as when they should...
Murph
I see your point, but I also see a difference between "changing" and "correcting". To help prevent (or at least minimize) frivolous modifications, you could restrict that function to the admin role. I'd be happy with that. In fact, I'd probably prefer it.
Philip Yurchuk
Michael is a man of few words. He was referring to the CVS table in your FogBUGZ database.
Dmitri Kalmar
|
