action #32719
closed
- Subject changed from [functional][easy][fast]Test for dstat to [functional][easy][fast][u] Test for dstat
- Description updated (diff)
- Status changed from New to Workable
made workable, though I wonder why "new tests" are added as [fast] during the sprint -> added to discuss for retrospective
because I stated "let's be nice to …" and I thought an easy task could be handled. If you think we can't then let's plan it for a later sprint. IMHO no need to overdiscuss in retro.
- Subject changed from [functional][easy][fast][u] Test for dstat to [functional][easy][u] Test for dstat
- Due date changed from 2018-03-13 to 2018-03-27
It's a new test, let's schedule for the next sprint. We should not add tickets like this into the sprint. I guess we have to discuss it in the retro unless you've added this one to ask if it's ok. I moved it to the next sprint as of now, we will see the priorities.
- Target version changed from Milestone 14 to Milestone 15
- Priority changed from Normal to Low
- Status changed from Workable to In Progress
- Assignee set to okurz
- Status changed from In Progress to Resolved
- Related to action #33469: [qam] test fails in dstat - clean/update needles for dstat-fileoutput added
Also available in: Atom
PDF