Skip Navigation LinksHome Page > Forums > Announcements > Rants and Raves > Worklogs screen
Hello, Inflectra team,
Many thanks for implementing worklogs feature in Spira in Version 8.4. That is what I was waiting for!
Some thoughts what to improve ranked by it's priority (the most needed features are at the top):
Hi Ilya,
You're very welcome!
The good news is that we have more functionality coming in v8.5 and 8.6:
For item 5 that is possible already through the task/incident workflow pages.
I have logged items: 2,3,4,6,9 as a new enhancement.
Regards
David
Thank you. Also what is missing right now is an ability to easy decrease remaining effort at the time of logging hours in worklogs screen. Previously there was such an option.
So now people track their hours better but often forget to decrease remaining hours.
Let's have one column at the left (right after "artifact") with an ability to edit remaining hours. Not too hard to implement but a big step with usability.
Also, we need to have a customizable period freeze.
Example: a manager has approved employees’ worklogs for some period. After that an employee shouldn't be able to change or delete it or to add more for that period.
(low priority request)
Hi Ilya
Also we checked and:
Delete incident/task from worklog's screen list
will also be in v8.5.
I have also logged the issue of the remaining effort.
Hello,
Many thanks for a new version of Spira, where now we have:
1. Edit and delete worklogs
2. Delete incident/task from worklog's screen list
3. An ability to use it in a custom reports
That is a huge step forward for Spira-users.
Also based on your answers I agree that we consider as resolved:
5. Ability to disable changing "actual effort" not from worklogs page
Now in Spira we have two ways how users may increase actual effort: via actual effort field and via worklogs. And bad news there that there is no linkage between them and that may cause some bad consequences in understanding what has happened in Spira in reality:
An architect in the past for such systems, I suggest to consider a direct change of actual effort as timesheet record too (and have it at "R_TimesheetEntries" table too) but with the EFFORT_DATE equals to the date of change (CHANGE_DATE in R_HistoryDetails). Or another option (even better) to have under one CHANGESET_ID in R_HistoryChangeSets clearly stated that with the same CHANGESET_ID there was increase of actual effort and changes in Timesheet with mentioning proper TIMESHEET_ENTRY_ID.
Remaining features:
All those ideas just to have it solid. Developers do not like time-reporting, so that part of Spira should be perfect to avoid any push back from developers to Spira or Inflectra.
And if you have any questions, please email or call us at +1 (202) 558-6885