Creating card transitions

Card transitions give your team a shortcut for completing common actions in Mingle, such as closing a bug or marking a user story as complete. As the name suggests, your team can use transitions to move cards from one status to another.

Defining custom transitions

Transitions are the main way you define your project's workflow, and you can use transitions to assign work to various team members at different stages of the project lifecycle.

Hint: See List of common card transitions for example transitions you may wish to use in your project.

Card transitions add a link to cards that match the card properties you specify in the card transition. For example, in the Close defect transition below:

Any card that is of type = bug with a status = fixed will have a link on the card called Close defect. Clicking this link will change the card's status to closed and remove the card's previous owner.

Note: You must set up all card properties before you can create card transitions. If you hide a card property, any transitions that use the property will no longer display for team members.

How to create a new card transition

Transitions and card version numbers

Another benefit of card transitions relates to card version numbers. In the example above, if you were to change this card's status to closed and owner to (not set) manually, Mingle would advance the card's version by two. For example from v4 to v6. Using a transition always advances a card's version by one, e.g. v4 to v5.

Hidden card properties

In some cases you may have hidden card properties that you are no longer using. The Card transitions page indicates hidden properties with a green background. If a card property is hidden, this transition link will not display for cards that meet the card property criteria.

Transitions for specific team members

When you create transitions, you can make them available for all team members or only specific team members. When you select Only selected team members, Mingle displays all team members and you can select the checkbox next to their name to make the transition visible to these people only.

This is useful if you want only certain people performing specific functions. For example, only a tester should be able to close defects, so you may choose to make a Close defect transition available only to team members who are testers.

More info...

Back to Creating project properties