Below is a list of suggested card transitions that you may wish to use in your project. The actual transitions you choose will depend upon your project's workflow and the card properties you have set up.
Hint: Once you've created your card transition values in a project, it's a good idea to define these in a wiki page for your team. This helps people understand the transitions you've chosen and so people know how/when to apply them consistently.
Hint: You can create shortcuts for common new cards in Mingle's navigation, e.g. New user story, New bug, New task, New risk.
| Suggested transition | How you might use this | Example card property transitions |
|---|---|---|
| Story analysis complete | Project manager, product owner or iteration manager has finished analyzing the content of a user story. User story is open, ready to be assigned to a developer. |
Criteria: type = story, status = new, owner = (iteration manager), release = R1 Output: status = open, owner = (not set) |
| Move to bug | Project manager, product owner or iteration manager indicates that the user story is actually a bug. |
Criteria: type = story, status = new, owner = (iteration manager) Output: type = bug, status = open, owner = (not set) |
| Move to next release | Project manager, product owner or iteration manager decides that a user story is not essential for the current release and decides to push it back to the next release. |
Criteria: type = story, status = new, owner = (iteration manager), release = R1 Output: status = open, release = R2, priority = low |
| Assign story | Project manager, product owner or iteration manager assigns an open user story to a developer. You may have multiple versions of this transition for different developers. |
Criteria: type = story, status = open Output: status = assigned, owner = (developer) |
| Open bug with priority X | Project manager, tester/QA or iteration manager has analyzed a bug, decides that it should have a certain priority and assigns it to a developer. You may have multiple versions of this transition for different priorities. |
Criteria: type = bug, status = new, owner = (iteration manager) Output: status = open, priority = (high, low etc.), owner = (developer) |
| Move from bug to story | Project manager, tester/QA or iteration manager has analyzed a bug and decides that it is really a user story. |
Criteria: type = bug, status = new, owner = (iteration manager) Output: status = open, type = story, owner = (not set) |
| Move wish to story | Project manager, product owner or iteration manager has analyzed a wish list item and determines that it should go into the product. |
Criteria: type = wish Output: type = story, status = open |
| Suggested transition | How you might use this | Example card property transitions |
|---|---|---|
| Start development | Developer indicates that they're starting to work on a user story. |
Criteria: type = story, status = assigned, owner = (developer) Output: status = in progress |
| Development complete | Developer indicates they've finished working on a user story and all code is now in the application. The user story is assigned to a tester/QA. |
Criteria: type = story, status = in progress, owner = (developer) Output: status = ready for testing, owner = (tester) |
| Bug fixed | Developer has fixed a bug and assigns it to a tester/QA. |
Criteria: type = bug, status = open, owner = (developer) Output: status = fixed, owner = (tester) |
| Suggested transition | How you might use this | Example card property transitions |
|---|---|---|
| Start testing | Tester/QA indicates that they are now working on testing a user story |
Criteria: type = story, status = ready for testing, owner = (tester) Output: status = testing in progress |
| Test passed | Tester/QA indicates that the user story passes testing. |
Criteria: type = story, status = testing in progress, owner = (tester) Output: status = complete, owner = (not set) |
| Test failed - user story | Tester/QA indicates that the user story fails testing. |
Criteria: type = story, status = testing in progress, owner = (tester) Output: status = assigned, owner = (developer) |
| Close bug | Tester/QA has tested the bug fix and determines that it has been fixed correctly. |
Criteria: type = bug, status = fixed, owner = (tester) Output: status = closed, owner = (not set) |
| Test failed - bug | Tester/QA has tested the bug fix and determines that it has not been fixed correctly. |
Criteria: type = bug, status = fixed, owner = (tester) Output: status = open, owner = (developer) |
Back to Creating card transitions