Welcome to the FogBugz Knowledge Exchange

Question

1

Excuse me if this is the wrong forum to be asking this, but I have a group of 4 students (myself included) that will be working on a plugin to automate creation of weekly wiki-based status reports. These reports are meant (in our situation) to be given to an adviser so that the team has feedback and stays on-track with their plans.

Although we do have a list of things we want to automate, we'd like more input about what fogbugz data might be useful in a status report, ideas on what we could potentially automate, and any miscellaneous questions or comments that are relevant.

flag	asked Sep 18 2010 at 7:27 Furwin 11●1

	Can you describe the projects that you are managing in FogBugz? How do you define "status"? e.g. ship-date predictions from EBS, number of cases open, specific pieces of information in key cases? – adambox♦ Sep 20 2010 at 15:20
	The projects are wide ranging (as they are often student directed), but they all incorporate a large amount of software engineering. A project 'status' is defined as an evaluation of the teams' progress in relation to their goals for the week. It's meant as a progress report. Currently, it includes an overview of meeting minutes, recent cases added to the plan, cases worked on in the past week, cases that will be worked on in the next week, and descriptions from the team about plans for the next week and beyond. Each case has the current time worked on and original estimates attached. – Furwin Sep 22 2010 at 19:03

adambox · Answer 1 · 2010-11-04 18:48:12Z UTC

I would take a look at EBS ship date predictions for your projects, including burn-down charts showing the amount of work remaining over time. I would also look at the new Reporting features in FogBugz 8.

ideas for what could be included in automated status reports (developing a plugin)

1 Answer