Activity for David Tuma
-
David Tuma modified ticket #408
HTML ID attribute missing from tables in EV reports
-
WBS icon colors are too similar for Universal MCF phases
-
Out of memory error on Mac OS X
-
Legacy WBS Editor does not trust internally-generated SSL certificates
-
Debugging window does not include java.util.logging output
-
Nested workflow tasks lost on save
-
Non-ASCII characters in person's name can interfere with PDES lock
-
QuickLauncher overlooks backup ZIP data for some projects
-
Personal data corruption after offline edits to WBS in cloud storage
-
Loss of recent WBS edits after cloud storage sync conflict
-
Deadlock on startup when PDES password change needed
-
Dashboard prompts for name from logged in PDES user
-
Read-only WBS nodes become editable in subprojects
-
Read-only WBS nodes become editable after save
-
It's quite a bit more complex than a simple max(0, xxx) calculation. As you've stated: when computing the Replan date for in-progress tasks, the dashboard will subtract actual time from planned time to produce remaining time. Remaining time is then used as the "weight" for a new earned value calculation, as described here, to produce a set of replan dates. The Forecast calculation is similar, except it divides planned time by CPI before subtracting the actual time. If some of the in-progress tasks...
-
It's quite a bit more complex than a simple max(0, xxx) calculation. As you've stated: when computing the Replan date for in-progress tasks, the dashboard will subtract actual time from planned time to produce remaining time. Remaining time is then used as the "weight" for a new earned value calculation, as described here, to produce a set of replan dates. The Forecast calculation is similar, except it divides planned time by CPI before subtracting the actual time. If some of the in-progress tasks...
-
It's quite a bit more complex than a simple max(0, xxx) calculation. As you've stated: when computing the Replan date for in-progress tasks, the dashboard will subtract actual time from planned time to produce remaining time. Remaining time is then used as the "weight" for a new earned value calculation, as described here, to produce a set of replan dates. The Forecast calculation is similar, except it divides planned time by CPI before subtracting the actual time. If some of the in-progress tasks...
-
Different people have different work schedules: which days they work, and which hours. The Team Member List in the WBS Editor does not have a way to record those nuances; and the dashboard has no way to respect nuances that it knows nothing about. So the Replan and Forecast dates are based purely on calendar-time proportions: 24 hours a day and 7 days a week.
-
After testing, I was able to verify the root cause I suspected earlier: the size of the appended signature can change from one run to the next. Timestamping could be a contributing factor. Fortunately, the size isn't completely unstable; it usually differs by a few bytes, and toggles between two (or occasionally three) possibilities. This makes it feasible to produce a successful signature by iterating until the sizes match in two consecutive runs. I took a look at modifying the original sign4j.c...
-
I've been experiencing this too. Unfortunately it is nondeterministic; sometimes it works and sometimes it doesn't. When it works the file is signed successfully; when it doesn't, running the EXE results in an error message "Invalid or corrupt jarfile" from the launched javaw.exe process. Nothing in my build process changes; I can run the build again, and it might work the next time or it might not. Overall my success rate is only about 50%. The worst problem is that I can't detect this failure in...
-
I've been experiencing this too. Unfortunately it is nondeterministic; sometimes it works and sometimes it doesn't. When it works the file is signed successfully; when it doesn't, running the EXE results in an error message "Invalid or corrupt jarfile" from the launched javaw.exe process. Nothing in my build process changes; I can run the build again, and it might work the next time or it might not. Overall my success rate is only about 50%. The worst problem is that I can't detect this failure in...
-
I've been experiencing this too. Unfortunately it is nondeterministic; sometimes it works and sometimes it doesn't. When it works the file is signed successfully; when it doesn't, running the EXE results in an error message "Invalid or corrupt jarfile" from the launched javaw.exe process. Nothing in my build process changes; I can run the build again, and it might work the next time or it might not. Overall my success rate is only about 50%. The worst problem is that I can't detect this failure in...
-
Loss of recent WBS edits after cloud storage sync conflict
-
Personal data corruption after offline edits to WBS in cloud storage
-
QuickLauncher overlooks backup ZIP data for some projects
-
Non-ASCII characters in person's name can interfere with PDES lock
-
Non-ASCII characters in person's name can interfere with PDES lock
-
Nested workflow tasks lost on save
-
Debugging window does not include java.util.logging output
-
Legacy WBS Editor does not trust internally-generated SSL certificates
-
Thank you for the clarification. I believe you need a newer version of the Enterprise Server. Please email me directly and I'll be glad to help. pdes at tuma-solutions.com
-
The error message you've attached pertains to errors surrounding JNLP files and Java Web Start. This is odd because the Process Dashboard is not a Web Start application, and neither is the installer. I have a few questions: 1. Which operating system are you using? Windows, Mac, Linux, something else? 2. Which Process Dashboard installer did you download? 3. How are you launching the installer? Are you double-clicking on it, or running something from the command line? Thanks in advance, David
-
Out of memory error on Mac OS X
-
WBS icon colors are too similar for Universal MCF phases
-
HTML ID attribute missing from tables in EV reports
-
Join sometimes fails for federated team project
-
Fixed in Process Dashboard version 2.7
-
Team member lookup fails for federated server project
-
Fixed in Process Dashboard version 2.7
-
Custom WBS columns not copied forward on relaunch
-
Fixed in Process Dashboard version 2.7
-
Incorrect size rollup for multiply-assigned PSP/PROBE tasks
-
Fixed in Process Dashboard version 2.7
-
UI hangs while saving data backup for large server-based dataset
-
Fixed in Process Dashboard version 2.7
-
Incorrect dock icons on Mac OS X
-
Fixed in Process Dashboard version 2.7
-
"Export My Data" misses recent changes on Size Inventory Form
-
Fixed in Process Dashboard version 2.7
-
Unable to launch multiple server datasets on Mac OS X
-
Fixed in Process Dashboard version 2.7
-
Exception thrown starting up process dashboard.
-
Fixed in Process Dashboard version 2.7
-
Custom WBS column widths not preserved
-
Fixed in Process Dashboard version 2.7
-
Data Error for ad-hoc tasks starting with '['
-
Fixed in Process Dashboard version 2.7
-
PDES Launcher Startup Error
-
Fixed in Process Dashboard version 2.7
-
Calculation Error Encountered window
-
Fixed in Process Dashboard version 2.7
-
Component assignments don't propagate into role-driven workflows
-
Fixed in Process Dashboard version 2.7
-
Time not applied to workflow after component type is edited
-
Fixed in Process Dashboard version 2.7
-
Time not applied to single-step workflows
-
Fixed in Process Dashboard version 2.7
-
Fixed for projects that are newly created/relaunched using Process Dashboard version 2.7
-
New windows open on different monitor
-
Fixed in Process Dashboard version 2.7
-
Error opening WBS exported Excel file
-
Fixed in Process Dashboard version 2.7
-
Defect Import fails for Smartbear Collaborator 12
-
Fixed in Process Dashboard version 2.7
-
Network/VPN issues trigger hang on startup/shutdown
-
Fixed in Process Dashboard version 2.7
-
Deleting schedule does not delete baseline storage file
-
Fixed in Process Dashboard version 2.7
-
High-Maturity Planning Task loses "LOC" units on relaunch
-
Fixed in Process Dashboard version 2.7
-
Original planned time is lost for relaunched overspent in-progress tasks
-
Fixed in Process Dashboard version 2.7
-
WBS doesn't show actual size data from PROBE Size Estimating Template
-
Fixed in Process Dashboard version 2.7
-
Excel date format
-
Fixed in Process Dashboard version 2.7
-
Application won't close on Mac OS X
-
Fixed in Process Dashboard version 2.7
-
UI hangs after applying estimating proxy to workflow step
-
Fixed in Process Dashboard version 2.7
-
Use of JSP EL 'test' expression causes exception
-
Fixed in Process Dashboard version 2.7
-
Timing icons not displayed in EV reports for personal rollup
-
Fixed in Process Dashboard version 2.7
-
Dashboard fails to start on Mac OS X with UnsatisfiedLinkError
-
Fixed in Process Dashboard version 2.7
-
Startup messages appear behind splash screen on Mac OS X
-
Fixed in Process Dashboard version 2.7
1 >
