-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zero work time in Science Tool and Science tab #1318
Comments
I don't know if it was after CollaboratorStats was added that the work time are no longer being tracked. Can you see what went wrong ? |
I'm pretty sure Collab stats were working. I will check the UnitTests to reproduce it |
@mokun This is not a bug. If you look the Study is in the Invite Collaborators phase so no one can contribute yet. |
But why would the See the screenshot above. |
When I look through any science studies in Science Tool, I have yet to find anyone having done non-zero work. What does Work mean ? Even in Study Proposal phase, it should accumulate the work spent in sols. So far, it's always zero. |
Because the Invite phase is that much completed. Each phase goes to 100% before advancing |
Q: why is the first person's Contribution column always blank ? |
No the logic has always been that work is only counted when research is actually being done via a Task |
Primary researcher has to do the Science of the Study. This is a UI problem I can fix. |
Changes: - Resarchers list in ScientificStudy window show contribution from Primary researcher - Person Science Study tab reworked to use standard UI compnents, e.g. Border and AttributePanel - Study model uses EntityModel so user can double click to Science Tool close #1318
Describe the bug
Expected and unexpected behavior
Java classes involved
Screenshots
If "Phase Completed" is 75%, then a lot of work should have been done by the following collaborators but no work time is reported
Hong Kuang shows zero work in Research and Paperwork column
Specifications
Details
The text was updated successfully, but these errors were encountered: