Timeline for User stories about one and the same functionality for two different roles
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13, 2020 at 9:05 | vote | accept | Hristo K | ||
| Jan 11, 2020 at 20:10 | comment | added | Hristo K | @BobDalgleish, your comment was the answer that helped me the most. I currently threat this as design specifics. Especially as some of the functionality could be implemented inside the mobile app. It was a design decision to implement it this way and this is the reason to stumble upon my question. Had we done it the other way, this issue wouldn't have existed at all. | |
| S Jan 10, 2020 at 18:17 | history | suggested | Mike P | CC BY-SA 4.0 |
Punctuation, spelling, language use.
|
| Jan 10, 2020 at 15:00 | history | tweeted | twitter.com/StackSoftEng/status/1215649702915514373 | ||
| Jan 10, 2020 at 14:56 | review | Suggested edits | |||
| S Jan 10, 2020 at 18:17 | |||||
| Jan 10, 2020 at 13:04 | answer | added | Dogs | timeline score: 2 | |
| Jan 10, 2020 at 9:07 | answer | added | Christophe | timeline score: 1 | |
| Jan 10, 2020 at 2:28 | answer | added | Stian Diehard | timeline score: 0 | |
| Jan 9, 2020 at 23:39 | answer | added | Greg Burghardt | timeline score: 4 | |
| Jan 9, 2020 at 22:33 | answer | added | Kain0_0 | timeline score: 2 | |
| Jan 9, 2020 at 22:15 | comment | added | BobDalgleish | This is not story material, but rather recognition of design and implementation constraints or goals. Economy of communication becomes one of the evaluation criteria you use when designing or selecting protocols, and can help guide the those processes. | |
| Jan 9, 2020 at 22:10 | review | First posts | |||
| Jan 9, 2020 at 22:15 | |||||
| Jan 9, 2020 at 22:03 | history | asked | Hristo K | CC BY-SA 4.0 |