Timeline for Is an event based approach the right way to think about this problem?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2018 at 1:55 | vote | accept | user1620696 | ||
| Jul 2, 2017 at 22:06 | comment | added | Kwebble | First get more detailed requirements on the result. Report the hours between start and end (what about multiple days), just the working hours of that period, or anything else like a total of all periods worked on? How that is recorded in the system is not relevant for the requirement, that is part of the solution you should come up with. | |
| Jul 2, 2017 at 16:13 | history | tweeted | twitter.com/StackSoftEng/status/881546268090269697 | ||
| Jul 2, 2017 at 14:40 | answer | added | Doc Brown | timeline score: 6 | |
| Jul 2, 2017 at 4:43 | comment | added | Brendan | There's nowhere near enough information in the requirements to make any recommendation of anything. It looks like you need to spend $5 on a cheap stopwatch and don't need any software at all. | |
| Jul 1, 2017 at 22:59 | answer | added | Erik Eidt | timeline score: 2 | |
| Jul 1, 2017 at 22:40 | comment | added | John Kouraklis | The requirement implies that each project has ONLY one employee. It sounds more like a Task rather than a Project. Can you clarify? | |
| Jul 1, 2017 at 21:16 | answer | added | Ewan | timeline score: 3 | |
| Jul 1, 2017 at 20:39 | history | asked | user1620696 | CC BY-SA 3.0 |