vsts - Active task = active story. Yes/ No? -
i have project in vsts. project consists of few features, stories , tasks shown:
f1 --f1s1 ----f1s1t1 ----f1s1t2
lets assume above mentioned items present in iteration 1
. if move task f1s1t1
new
active
, shouldn't story moved active in stories
board , feature moved active in features
board?
write if task active, have go , move story active , move feature active, colleagues can find feature undergoing development.
is there workaround move feature , story active automatically? or making use of vsts right way?
no, user story state has not direct relations task state. can find work flow user story , task here.
- when set user story state active: when started work on item (implementation started). , after user story active, can add tasks user story. , task states can of state (new, active, close or removed) since user story contains more 1 task.
- when set task state active: when started on task (work started).
so situation, when started on user story f1s1
, should change state active. when start work on task f1s1t1
, should change task state active. , before started on task f1s1t1
, user story f1s1
state should changed active already.
Comments
Post a Comment