Viewing card comments, murmurs and history
Mingle lets your project team view a complete history of all changes made to a card, and any comments made against that card.
You can view a complete history of all changes made to a project (or to specific card types, wiki pages or revisions) by clicking the main History tab. You can even subscribe via feeds or email to stay up-to-date with any relevant project changes.
You can view a card's history and comments in the top right corner of the screen when viewing a card.
By default, all comments for a card show first with a blank space to add a new comment.
Click the History component to display card history.
Click the View link next to a card version to see the card's status at that version.
And click the Show latest link to return to the current version.
Mingle creates an entry against card history and revises the card version number each time somebody makes a change to a card. Whenever there's a change to a card Mingle creates a snapshot of the previous version, so you can view the state of a card at any stage throughout its lifecycle.
You may want to view previous versions of a card page if:
- you or a team member accidentally overwrote a card's content
- you want to view information captured at an earlier stage of your project
- you remembered that there was some useful information or attachment in a previous version of a card.
For each card's historical version, Mingle shows:
- who updated the card and when (relative to your current time)
- a summary of the changes made for each version
- a link to view a previous card version.
Mingle updates card history whenever you or a team member:
- creates or imports a new card (version 1)
- changes the card's description
- adds a comment
- commits source code and includes the card number in the commit message
- changes a card as part of a bulk update
- adds, edits or removes tags
- updates a card property (from either opening the card, or dragging it to another property value within the Grid view). If you change more than one property, Mingle creates more than one history entry/card version)
- clicks a transition link
- imports an updated version of the card.
You can use card transitions to update multiple card properties at once. Clicking a transition link only updates a card's history once - regardless of how many card properties it updates.
Card comments and murmurs
Comments and murmurs aren't designed as a substitute for talking to your team mates! Their main purpose is to contribute collective intelligence about the development process.
Card comments are a way to discuss and explain team actions and decisions relating to cards. For example, comments can explain reasons why a developer fixed a bug a certain way, or provide clarification to a developer implementing a user story.
You can add card comments whenever you open a card because the card comments field is open and ready for you to type by default.
Murmurs card links
Like other areas in Mingle (such as source revisions), murmurs content renders card and wiki page links so that murmurs provide links to other information stored in Mingle. These card links work by using the existing project card keywords. In addition to providing links to other cards and pages, murmurs that are associated with a card are also displayed on the card in the Comments/Murmurs section of the card. To associate a murmur with a card either murmur from a card or include a link to that card in the content of you murmur.
In Mingle 3.1, most card links in Mingle will display a tooltip to show you the name of the card when you hover your mouse over the card links. This allows users to better understand the context of any content (comments, murmurs or card descriptions) which contain the card links.
Please note that when murmurs are displayed on a card there is a small navigation icon at the end of each murmur. When you click on this icon it will take you to that murmur on the Murmurs tab. This will allow you to understand that murmur in the context of other murmurs that occurred before or after it.