A forum for technical support discussion related to Fogbugz.
We just started using FogBugz, and it's growing on us quickly. I've set up a WebSVN server (with MultiViews for nice URLs), too. We've got the TSVN -> FogBugz -> WebSVN integration working, but we think it could be improved.
Currently, each commit against a task will generate a link to the file in WebSVN, and a link to the revision where it changed. That's fine as far as it goes. But it becomes unwieldy in two cases:
a) There are many commits to fix/implement the issue - the list grows with each one.
b) There are many files touched by the commit - the list grows with each one.
Just now, I updated my bugtraq properties, project-wide, recursively. This put ~200 lines into this space of the case UI, at the top in the Checkins section, meaning anyone looking at it now has to scroll a long way.
So, what we'd like...
a) The checkins section to be split up and put into the case's history. Ideally, the act of committing with TSVN will create a new case history item, inserting the log message and a list of changed files, and the revision, into the case history item.
- no longer does a developer have to document the same action in two places; log and tracker. Time saved. Less time "out of zone" as Joel might possibly say.
b) A thing that lets the user expand or collapse the list of files touched by the checkin.
- If the checkin is all in one place (as currently), then we'd like a treeview, whose first-level nodes are links to revisions against this case, and whose second-level is a list of files changed in each revision.
- If the checkin section is implemented as (a) above, we'd like just a link to the revision's diff (which in WebSVN would be a link to the diff of the revision that's linked to the case n, and n-1).
We realise that we have the FogBugz source code, and thus the capability to have a go at this ourselves; however, we think the request probably isn't original, and that there's a chance someone might have already done it. If so, would you mind telling us, or perhaps sending us a patch?
We'd appreciate it too if this could be filed as a feature request for a coming version of FogBugz, since we reckon it'd improve the usability quite a lot, and we know how you guys like good usability ;-)
This topic is archived. No further replies will be accepted.Other recent topics