User groups have been added to Mingle.

User groups are a way to structure the team members in your projects. You can restrict card workflow transitions so that only team members in certain user groups can execute them. For example, if your workflow includes a transition to indicate that story analysis is complete, you may only want team members in the "business analysts" user group to execute the transition. You can define any user groups you want in your project. User groups may be based on roles, organizations, skills, or whatever else you decide.

User groups go very well with Mingle project templates. You can create workflow transitions associated with user groups in a template. The specific users in the projects created from the template will differ, but the workflow transitions will still be applicable for the team members in the user groups.

The user management page has been improved in Mingle 3.3.

• You can now hide deactivated users. This allows you to focus on only active Mingle users.
• We have added "last login" information to help you manage your licenses more easily. You can sort the last login column to see who hasn't logged into Mingle recently. If you are running out of Mingle licensee users, the last login information can help you determine if you have users that can be deactivated in order to reclaim license seats.

Mingle 3.3 makes it easier to manage team membership.

• A user can now be added to multiple projects at once. This can be especially useful when people join your Mingle instance and need to be added to several Mingle projects.
• You can now remove multiple team members from a project at once. This is helpful when a project is ramping down or when several people have been accidentally added to a project.

On the list view and hierarchy view, there is a new option to only export properties that are shown in the view.

Card ranking has been updated to rank newly created cards at the bottom of the list rather than the top. The Mingle community has told us several times that ranking new cards as "most important" isn't desired. We have listened to the requests and made the change.

Go, our Agile release management solution, and Mingle are now more tightly integrated. Visibility into the health of your builds is now provided directly in Mingle with a live view of your Go pipelines available to all Mingle cards and wiki pages.

You now have access to Mingle history via the new events API. This is the first time that Mingle history has been available via the API, and opens up many new possibilities.

As part of the new user groups feature, we have added a user groups API. You can either get information about all of the user groups in a project or a single user group. The transitions API has also been enhanced to indicate which user groups are associated with a transition.

The user interface has been enhanced to feel more clean and crisp. Additionally, there are changes in the interface that should improve usability. For example, previously all actions looked the same, even though some actions are used much more frequently. In Mingle 3.3, the "primary" action on a particular page will stand out from the other actions on the page. In the following screenshot you can see that "Edit" is the primary action on this page:

There are many other changes like this that should make Mingle more intuitive and easy to use. In addition to improving the general look and feel of Mingle, a few areas have received special attention:

• The user profile page has been reorganized to make it easier to understand.
• The mechanism to search for users on the user management page and the team management page has been integrated more tightly into those pages.
• The Murmurs page has been updated to make it feel more like the conversation it is intended to be.

We are excited about the changes, and hope you enjoy the new interface as well!

We have added official support for the following in Mingle 3.3:

• Internet Explorer 8 is now a supported browser.
• Windows Server 2008 is now a supported operating system.
• Git is now a supported source repository.

Mingle 3.3 contains a beta feature to support nested IN MQL statements. This allows you to query for a set of cards based on conditions for a related card.

Mingle 3.2 introduces three new ways to access Mingle's extensive help content.

First, Mingle's new Explore Mingle page, which is included as part of each Mingle project, guides new and existing Mingle users to new and previously existing Mingle help content.

The Explore Mingle content serves a variety of functions:

• it introduces you to common Agile and Mingle concepts
• it helps you explore Mingle's capabilities
• it provides tips and recommendations on how to configure and use Mingle to meet your individual project needs
• it directs you to further information and learning resources about using and administrating Mingle

Secondly, contextual help has been created to provide specific "in context" help on Mingle's most popular views and administration screens.

Finally, further to the Explore Mingle page and contextual help, Mingle 3.2 also introduces the ability to search Mingle's online help content allowing you to more easily find the help you need.

Read more about Mingle and Studios help and support features.

Mingle 3.2 extends Mingle's current reporting capabilities by providing a new historical chart called, the Daily History chart. The Daily History chart allows you to create a burnup or burndown of a numeric property over time. Unlike Mingle's previous charts, which only used current Mingle data, the Daily History chart uses Mingle's historical data. This use of Mingle's automatically generated history means that you do not have to create extra reporting properties and these charts are always as accurate as a project's history.

New Google map and Google calendar macros:

• ability to embed a Google map using the new Google map macro.
• ability to embed a Google calendar using the new Google calendar macro.

Improvements to the Cross Project Macro:

• ability to use predefined properties, such as name, in the cross project rollup macro. This is a valuable addition to the cross project reporting features in Mingle.

Excel Import improvements:

• More intuitive and consistent naming for "number" column during Excel import
• Improved property column option names when importing via Excel

Displaying user display name on all charts and tables:

• When reporting against a Mingle user, in any of Mingle's charts and table macros, Mingle now displays the user's display name as well sign-in name

Card pop-up updates:

• Quicker access to cards from the card grid view and tree view pop-ups by clicking the Card number
• Transition names are easier to read on card pop-ups

Card property updates:

• To show more of your project structure information, if a card property has a description, the description will be displayed as a tooltip when hovering over the property names on cards, transitions, filters and grid view actions (e.g. group by, sort by, color by)

The Mingle API now supports creation of a card property and a card type.

The Mingle API now supports viewing all transitions for a project.

Mingle 3.2 supports a beta feature to query historical card information. Using this feature, you can see what the final values of a card property are at the end of a day.

Mingle 3.1's new My favorites allow you to create and manage your own personal project favorites. Like Team favorites, My favorites, are a shortcut for you to quickly access your view, the project data and elements of the project workflow that are relevant to them.

Further to the new collaboration feature, Murmurs, that was introduced in Mingle 3.0, Mingle 3.1 has enhancements to this functionality to allow you to:

• return to the Murmurs tab from murmurs on cards
• create card comments as murmurs and automatically indicate the card where a murmur came from when displaying murmurs
• search for murmurs, both in global search and on the Murmurs tab

Further to the existing THIS CARD functionality which allows you to create card specific reports easily, Mingle 3.1 provides increased ability to access values of a card's properties in MQL and macros using THIS CARD. This new functionality allows you to create more specific card related queries and charts that, when combined with card defaults, allows you to define your reports once and automatically have them available on each card as it is created.

In addition to Mingle's existing history filters, you can now search for and subscribe to updates for any change to a particular property.

Mingle 3.1 allows Mingle and project admins to set a project as visible in the project list to non-project members. When this option is set, non-project members can request access to the project and admins will be notified of their request for access.

Mingle 3.1 has a variety of different usability improvements:

Improvements to the Mingle views:

• ability to maximize list, grid, hierarchy and tree views and create maximized favorites
• ability to hide the card quick add when not in use

Other usability improvements:

• ability to navigate to a value of a card property from a card
• ability to navigate to card from the grid and tree views without having to open the card popup
• ability to use keyboard arrow keys to select values from property drop downs
• more card filters updated with the improved property value selector introduced in Mingle 3.0
• improved value selector for tree properties
• improved card comment formatting
• warn users of the consequences of changing a card's type

The Mingle API now supports formatting the results of the Execute MQL API in JSON and JSONP.

The Mingle API now supports viewing and configuring Mercurial and Perforce source repositories.

Mingle 3.1 now supports working with PostgreSQL 8.4.

Read more about Mingle's system requirements.

Murmurs are a new way to capture unstructured project and card information in Mingle. They allows the team to keep all relevant project and card information in one place, making contextually relevant information available for the whole team when it is needed.

The Macro Editor is a new feature introduced in 3.0. It is an editor to help users to create charts and tables using Mingle’s existing macros and this works for all our existing in-built chart and table macros.

In Mingle 3.0 we have introduced a variety of different features to support program management and cross project functionality. These include:

• Ability to copy a card from one project to another.
• Extended page and card linking syntax to support cross project linking.
• Extended the Macro Development Toolkit to support cross project reporting.
• A custom macro to chart property aggregations across multiple projects. This adds an important feature to Mingle's cross project reporting functionality.
• Add the ability to use "project" in the MQL SELECT statement.

As well as specific improvements we have made to improve cross project reporting for program management, Mingle 3.0 also provides updates to aggregate and formula functionality and MQL to increase the ability to create flexible and bespoke reports in Mingle.

Updates to aggregate and formula properties

• Ability to use aggregate properties in formula properties.
• Ability to use conditional criteria in aggregate properties, e.g. count all children where status is open.

Extensions to the Macro Development toolkit

• In Mingle 3.0 we have extended the Mingle Macro Development Toolkit to allow for multiple/cross project reporting.

Additional MQL functionality

• MQL has been extended to support the ability to use "Created on" and "Modified on" in MQL select and condition statements.

Mingle 3.0 includes a variety of usability updates the views and value selectors. These updates include:

Improvements to views and property selectors

• An improved column/lane selector on the list, grid and hierarchy views
• Improved property value selectors
• The ability to show and update hidden properties on the card show/edit.

Transition improvements

• Allow a transition prerequisite that requires a property to be '(set)'.

Concurrency improvements

• Always load the latest card and page version when editing a card or a wiki page

Use of personal icons

• In Mingle 3.0 users can upload a personal icon their profile. Personal icons will be displayed on comments, Murmurs and history updates.

Manage history subscriptions

• Users now have the ability to manage email history subscriptions via their user profile page.

As well as making improvements to Mingle's existing APIs, in Mingle 3.0 the API has been extended in a variety of ways to include the ability to:

• get card types and associated properties via a Card Types API.
• execute MQL via the Execute MQL API.
• get and create card comments via a Comment API.
• get and create Murmurs via a Murmurs API.

Mingle 3.0 includes improvements to support Mingle clustering which facilitates horizontal scaling for larger organizations.

With Mingle 3.0 we have added support for Mercurial source repositories.

We have also update our Subversion source integration to support up to Subversion 1.6.5.

With the 3.0 release, Mingle will no longer support MySQL. Mingle will warn users trying to use 3.0 with MySQL that this is no longer supported. MySQL users will need to migrate their data to a supported database.

Mingle 2.3 introduces the concept of card ranking in the grid view. It provides the ability to rank and prioritize cards by positional ordering in a grid lane. This allows you to simulate ranking, as you would using a physical card wall, on Mingle's card walls.

You can now print a single Mingle card including the entire Mingle description, all properties and comments.

We now support the use of project variables in card defaults, card property value selectors on single cards and in the bulk editor, card transition pop-ups and as the value of more Mingle macro parameters.

Mingle already supports the ability to generate charts for multiple projects in a single project. In 2.3, Mingle allows you to report on multiple projects in a single chart by adding cross project support at the series level on Data Series and Stack Bar charts.

In Mingle 2.3 we have extended the Mingle Macro Development Toolkit by allowing custom macros to output JavaScript.

Card transitions can now be filtered by card type and property allowing you to easily find specific transitions and see how they relate to one another in a workflow.

Mingle 2.3 introduces the ability to Generate a transition workflow. This helps users to generate transitions according to their specific workflow.

Mingle now supports Oracle 10g.

In Mingle 2.3, many configuration options have been moved from the installation to the Mingle data directory which means upgrading your Mingle instance and keeping your existing configuration between upgrades is now much easier.

Learn more about Mingle's advanced configuration options.

Mingle 2.3 now includes an option to automatically enroll all existing and new users of the Mingle instance as team members of a project. This reduces the need for manual user management on global projects where all users should be team members.

Mingle 2.3.1 includes a variety of performance improvements especially with regard to grid and tree view card loading.

Mingle 2.3.1 now includes the ability to expand and collapse children cards in the tree view.

The Mingle Macro Development Toolkit provides users the ability to write custom reports and visualizations against Mingle project data.

All charts now support sizing parameters, ensuring that all labels, legends and axes can be seen.

We've listened to user feedback and have simplified the card quick add feature. Card quick add is now decoupled from property filters, and card defaults are always applied.

The REST API now includes the ability to add, update, or remove attachments.

The REST API now includes the ability to create and update wiki pages.

A card's membership in one or more trees will no longer prevent its deletion.

The user and project team pages now have pagination and search capabilities to ease user management.

Mingle 2.2 now supports source integration with Subversion 1.5.

Moving cards on the card wall can now trigger transitions that you have setup for your project. This gives you all the benefits of using the card wall, without having to worry about cards getting into an inconsistent state.

Use transitions to automatically drop cards from a tree, and to optionally set values during transition execution. These features give you more flexibility than ever before in designing your project workflow.

Recognizing the many requests we have had for these features, Mingle now supports two new kinds of user access. Read-only team members can be configured on a per-project basis and have a much more restricted set of options when it comes to editing and updating information. In addition, a project can be configured to have anonymous access which allows a project to be accessed by a user that does not have a login in Mingle.

MQL supports a new syntax for a macro to refer to the card that it is contained in. The "THIS CARD" syntax in a macro on a card allows the macro to refer to the card itself. Used in conjunction with the existing feature of card type defaults, this allows you to create template reports that come into existence the minute you create a new card of that type.

Also new in MQL is a new syntax to print the value of a Project Variable.

All pivot table links have now been enabled. Using the flexibility of the new MQL filtering feature, all links now point to the exact set of cards that created them.

Harness the full power of the same MQL language that you use for reporting and charting to filter your cards. In cases where the interactive filter does not suffice, or when the conditions are too complex to be expressed through the interactive filters, there is now a more concise option.

With the 2.1 release of Mingle, the hierarchy view introduces new features including the ability to sort by various columns and keep track of collapsed and expanded states of various levels of the hierarchy.

Mingle 2.1 comes with a revised tree view, which simultaneously allows you to see more of your tree, while affording better navigation with zooming and panning features. All existing features including the ability to quickly build up your tree and modify its structure, continue to work with the new layout.

The REST API to fetch cards now allows you to fetch, in a single request, all cards in a particular project, in addition to supporting an easy paging mechanism, should you wish to use it that way. This allows extension/plugin writers to use the the API is a much more flexible way.

Mingle 2.1 introduces the ability to create properties of type ‘Card’. These card relationship properties allow you to link cards together without the need to create a tree.

With the addition of read-only and anonymous users in Mingle 2.1 we have made some updates to our licenses. If you have an expired or invalid license all users will be made read-only.

With the 2.0.1 release of Mingle, we support Perforce in addition to Subversion as a version control system. All the power and features that users have grown to know and love with our Subversion integration are now available with Perforce too.

Support for Single Sign On is provided through a plugin. This authentication plugin supports the JA-SIG Central Authentication Service.

The REST API can now be used to query a Mingle instance for all projects on it.

For when you don't have access to online help, Mingle now comes with the exact same help as you will find online on our site.

You can access your local help at http://your.mingle.instance:port/help/index.html

Card trees allow the creation, viewing and manipulation of hierarchies of card types.

You can view cards in a tree using two new views, Tree view and Hierarchy view.

You can create aggregate properties to display the Sum, Average, Min or Max of properties of descendant cards, or Count of descendant cards in a card tree.

Aggregate values can be viewed in the column header in Grid view.

Mingle now provides a RESTful API which allows you to integrate it with other systems.

Set project variables that can be used in MQL, transitions and filters

You can now create formula properties, where the property value is derived from the values of other card properties. Formulas can refer to card properties or project level variables and can operate on numeric or date values.

You can now create consolidated reports across a set of projects.

• Card Defaults for individual Card types
• Reordering of display properties on cards by Card type

You can now include MQL and macros (graphs and tables) in card descriptions

• Create a table which lists all defects that are children of the current story
• Create a pie or data-series chart that shows what proportion of an iteration or sprint's cards are completed

Saved views have been renamed to Favorites in Mingle 2.0. You can now create favorite wiki pages as well as favorite card views. Both kinds of favorite can be made into tabs.

• Wiki Toolbar and New Preview Pane for Wikis and Cards
• Wikis as Favorites and Tabs
• Recently Viewed Pages panel for Wiki pages
• Support for multiple attachment uploads on Wiki pages
• New Data Series Chart (Trending up and Down, Data Points and Labels, Multi-Bar Charts)

These provide additional functionality for using the Mingle wiki.

You can see how the new features of Mingle 2.0 have been incorporated and used in the standard Mingle templates.

• Easier integration with multi-project Subversion repositories
• Support of certificate based login for Subversion

These features enhance Mingle's integration with Subversion.

• Support for group authentication in the LDAP plugin

Enhancements for configuring email settings:

• SMTP TLS encryption
• SMTP Configuration Console