Oscar from Daylite says:

quote:

The report seems to crash out of Daylite on my computer too when I try to run it. You can maybe ask Brendan the creator of the report to post up on the forums a very simple sample database on which it works and that way we can compare it, maybe even give a glimpse of what might be happening.

I ran the report against the built-in sample database that Daylite creates when installing and it worked fine. Although the project that came up had no organization link, so the organization name showed as <null>. Also there wasn't much data so the report was only 1 page with 1 task in 1 project.

I'm still baffled why it's crashing on your systems.

I've made some updates to the report. I've also renamed it to "Est. Projects and Tasks by Org" due to the fact that the times are calculated based on the task estimates. I did this because I will be creating a new version based on the actual time for subtasks to go along with my SubTask Timer plug-in.

Please let me know if this one crashes on you.

Thanks,

Brendan

This is working for me! Sweet!

Hi,

I added a new report that uses the subtask information generated from my SubTask Timer plug-in.

The new one is called " Act. Projects and Tasks by Org.dlreport.zip"

You can download the Projects & Tasks by Organization Report here.

This one uses subtasks to calculate the duration rather than task estimates. Also note that if a task has no subtasks, it will display the time for that task. However, if the task has subtasks, the time will not include the parent's time, but will only include the subtasks time. The individual subtasks are not printed out. Only the parent tasks are printed out.

Let me know if there's any problems with this report.

I'm using the latest version of DL, but I can't seem to make this report work for me. It's stored in the proper location, but it brings back no data even though I believe the test tasks I created are properly linked to organizations and projects, has start and completion data, etc. Any ideas what I'm doing wrong here?