K2 Proposed Workflow
An Action is the label on a button. And Status is the state in which the issue currently resides. So, given a particular issue Status a number of Actions are available for a person to click on.
In the table below, the first column is the Action chosen to reach the state represented by the rest of the columns: Status, further actions available, etc.
In the last column, each available Action has the target row in parentheses.
# |
Action |
resulting Status |
resulting resolution |
description |
actions visible |
|---|---|---|---|---|---|
a |
(create issue) |
Open |
unresolved |
the issue has simply been initiated with values |
Close (k), Edit User Story (b) 1 |
b |
Edit User Story |
editing user story |
unresolved |
user story is being written and has not been finalized. |
Vote (c) |
c |
Vote |
Voting |
unresolved |
User Story is being voted on. This is for a consensus on the completeness of the user story. |
Approve (d), Reject (e)2 |
d |
Approve |
Approved |
unresolved |
User Story accepted by consensus |
Commit to work on task (f), Vote(c), Edit (b) |
e |
Reject |
Rejected 3 |
resolved |
(Probably indistinguishable from/same as Closed) |
Reopen (a) |
f |
Commit to work on task |
Commitment made |
unresolved |
An institution and or individual has made commitment to work on the task |
Start task (g), Rescind commitment (d) |
g |
Start Task |
task started |
unresolved |
Someone is actively working on the task |
Suspend Work (f), Complete (h) |
h |
Complete |
Completed for review |
unresolved |
Work has been completed and is ready for review |
Commit to work on task(f), Begin QA testing(i), Close (k) |
i |
Begin QA testing |
QA |
unresolved |
Someone is performing official QA |
Testing Completed(j), Work on task (f) |
j |
Testing Completed |
Testing Completed |
unresolved |
Review QA results, evaluate |
Close (k), Begin Testing (i), Work on Task (f) |
k |
Close |
Closed |
resolved |
Closed |
Reopen (a) |
1 ....or 'Edit Use Case' or 'Edit Narrative'
2 .... or Close
3 ... or Closed