Details on the report below - from Jesco von Voss: > I'm not sure quite how the second report works. Given a particular version, > list all the time assigned to different developers? How does the calendar > date part work? The idea is this: I want to know how much buffer time we have until a version is due. And a version is due on a release date, which is given by calendar date, not by the expression "in 45 work days". So I have a developer and sum up her current work load in days and hours, based on all issues assigned to her. (Minus the time worked on the issues, of course. And across all projects.) That is the first report I described. Now I give a calendar date, and the system should figure out how many days the developer will be in the office. How many times will the sun rise, minus all Saturdays and Sundays. That's how many days she has left to complete her work load. The difference is the buffer time for her. As you already have popups in date input fields that show the month, formatted by weeks, I imagine calculating the office days would not be too hard. Let's ignore July 4 or any other holidays for now. Ideally, one would like to see this for all developers in an overview page (Or maybe for all developers that are assigned to a project? ) But a start would be to show this on the start page for every developer. The question is how this "release date" would be stored. Ideally, I would like to set one project as being the reference in the global Administration settings somewhere. Then, the system would get that project, get the next upcoming version, and retrieve its "release date" value, which I have set appropriately. The fast version of implementing this would probably be to just set a "release date" somewhere in the Administration settings and use that value. There is a slight mismatch, as you might have noticed: I want the workload of a developer gathered across all projects, but one project should be used to determine how much time is left. But that's how we work ... we'd like to set up one project "Holidays", one project "Fairs + Exhibitions", and everyone would log issues there. This way we know: "Person A has two days off, is one day at a conference, and has 14 days worth of issues, that gives him two days left until day X, and that's ok".