What's new in Mingle
What's new in Release 3.0
Introducing Murmurs
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.
Click here to read about Murmurs.
Introducing a Macro Editor
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.
Click here to read about Mingle's Macro Editor.
Functions to support program management
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. Click here to read more about copying cards between projects.
- Extended page and card linking syntax to support cross project linking. Click here to read more about page and card linking.
- Extended the Macro Development Toolkit to support cross project reporting. Click here to read more about the Macro Development Toolkit.
- A custom macro to chart property aggregations across multiple projects. Click here to read more cross project reporting in Mingle.
- Add the ability to use "project" in the MQL SELECT statement. Click here to read more about MQL.
Reporting improvements
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. Click here to read more about formula properties.
- Ability to use conditional criteria in aggregate properties, e.g. count all children where status is open. Click here to read more about aggregate properties.
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. Click here to read more about the Macro Development Toolkit.
Additional MQL functionality
- MQL has been extended to support the ability to use "Created on" and "Modified on" in MQL select and condition statements. Click here to read more about MQL.
Usability and other inprovements
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. Click here to read more about viewing hidden properties on the card view.
Transition improvements
- Allow a transition prerequisite that requires a property to be '(set)'. Click here to read more about creating transitions and using the (set) value.
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. Click here to read about more about adding an icon to your profile.
Manage history subscriptions
- Users now have the ability to manage email history subscriptions via their user profile page. Click here to read about managing your subscriptions.
API updates
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. Click here to read more about the Card Types API.
- execute MQL via the Execute MQL API. Click here to read more about the Execute MQL API.
- get and create card comments via a Comment API. Click here to read more about the Comments API.
- get and create Murmurs via a Murmurs API. Click here to read more about the Murmurs API.
Click here to read about more about the Mingle API.
Clustering and Scalability
Mingle 3.0 includes improvements to support Mingle clustering which facilitates horizontal scaling for larger organizations.
Click here to find out more about scaling Mingle.
Additional source intergation support
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.
Click here to learn more integrating your Mingle projects with Subversion, Mercurial or Perforce.
Database changes
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. For more details on migrating to another database please see here.
Upgrading from previous versions
Upgrading from Mingle 2.3.1
Before you get started
Starting with Mingle 3.0 MySQL will no longer be supported. All existing MySQL users will need to migrate their data to Postgres or Oracle before upgrading to Mingle 3.0. See here for help migrating to Postgres or Oracle.
These instructions are for upgrading from Mingle 2.3.1 to Mingle 3.0. Look here to see how to upgrade from Mingle 2.3 and here to see how to upgrade from Mingle 2.2. Upgrades from earlier versions such as 1.0, 1.1, 2.0, 2.0.1, 2.1 and specifically, the 1.0 Early Access & 2.0 Early Access versions are not supported.
- Please ensure that no-one, other than Mingle administrators completing the upgrade, has access to Mingle during the upgrade process. We expect that the upgrade of Mingle is completed by Mingle administrators only.
- The upgrade to 3.0 involves migration of your existing data which is a very sensitive process. We strongly recommend that you make a backup of the Mingle data directory and your database before starting the upgrade process. DO NOT SHUT DOWN THE SERVER IN THE MIDDLE OF THE UPGRADE PROCESS AT ANY COST.
- ANY TEMPLATES THAT WERE INSTALLED WITH THE PREVIOUS RELEASES WILL BE REPLACED. This has no impact on any of your existing projects or any templates that you have created yourself. If you have modified the pre-installed templates and wish to keep them you must export them and then import them using a different name before the upgrade.
- The Mingle database will be upgraded and any projects in your 2.3.1 database will be upgraded and fully usable as soon as you start a newly installed 3.0 Mingle server.
- Any old project export files (.mingle files) can be directly imported into the 3.0 version of the application. They will be automatically upgraded upon import.
- If you are migrating to Mingle 3.0 and have properties already called "Created On" and/or "Modified On" these will be renamed to be called "Created On_1" and/or "Modified On_1" and any previous uses of these properties (in Favorites, Formulas etc...) will be updated. Use in MQL (including MQL filters) will not be updated and, as a result, any previous MQL using "Created On" and "Modified On" will now use Mingle's predefined properties of the same name in the query.
- Mingle 3.0 now allows specification of a configuration directory config files. Please read the upgrade steps below for details on setting a config folder.
Installing the software
Windows
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080.
- Run the Mingle uninstaller to remove your current installation. The uninstaller will stop the Mingle service if it is currently running.
- Run the new installer.
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
If you do not uninstall Mingle manually and try to install a newer version at the same location as an existing installation, Mingle will automatically uninstall the existing installation of Mingle before installing the new version.
OS X
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080. These are both visible from the Mingle launcher application window.
- Stop Mingle and quit the Mingle launcher application.
- Drag the new copy of the Mingle application (Mingle_3_0_xxxxx.app) into your Applications directory (overwriting the old Mingle).
- Start Mingle
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Linux/Unix (except Solaris)
- Note the location of the Mingle data directory on which Mingle is currently running. This is contained in the mingle.properties file in the Mingle data directory.
- If the Mingle server is currently running, stop it using the './MingleServer stop' command inside the 'mingle' application directory.
- Untar the newly downloaded archive.
- Start Mingle, using './MingleServer --mingle.dataDir=/path/to/your/data start' where /path/to/your/data is the location of your data directory.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Solaris
The steps to install on Solaris are very similar to that on any other UNIX except
- You would use the UNIX zip installer rather than the tar.gz installer due to the fact that the default Solaris tar command is incompatible with the format with GNU tar.
- You will have to ensure that the MingleServer script in the application directory has execute permissions.
After installation is complete...
Configuring Mingle's authentication
The authentication settings for Mingle are controlled through the [mingle_data_directory]/config/auth_config.yml file. This file is created by default on all brand new installations. For a detailed explanation of how to change Mingle's authentication please see here.
Advanced configuration
For further information on configuring Mingle see here.
Upgrading from Mingle 2.3
Before you get started
Starting with Mingle 3.0 MySQL will no longer be supported. All existing MySQL users will need to migrate their data to Postgres or Oracle before upgrading to Mingle 3.0. See here for help migrating to Postgres or Oracle.
These instructions are for upgrading from Mingle 2.3 to Mingle 3.0. Look here to see how to upgrade from Mingle 2.3.1 and here to see how to upgrade from Mingle 2.2. Upgrades from earlier versions such as 1.0, 1.1, 2.0, 2.0.1, 2.1 and specifically, the 1.0 Early Access & 2.0 Early Access versions are not supported.
- Please ensure that no-one, other than Mingle administrators completing the upgrade, has access to Mingle during the upgrade process. We expect that the upgrade of Mingle is completed by Mingle administrators only.
- The upgrade to 3.0 involves migration of your existing data which is a very sensitive process. We strongly recommend that you make a backup of the Mingle data directory and your database before starting the upgrade process. DO NOT SHUT DOWN THE SERVER IN THE MIDDLE OF THE UPGRADE PROCESS AT ANY COST.
- ANY TEMPLATES THAT WERE INSTALLED WITH THE PREVIOUS RELEASES WILL BE REPLACED. This has no impact on any of your existing projects or any templates that you have created yourself. If you have modified the pre-installed templates and wish to keep them you must export them and then import them using a different name before the upgrade.
- The Mingle database will be upgraded and any projects in your 2.3 database will be upgraded and fully usable as soon as you start a newly installed 3.0 Mingle server.
- Any old project export files (.mingle files) can be directly imported into the 3.0 version of the application. They will be automatically upgraded upon import.
- If you are migrating to Mingle 3.0 and have properties already called "Created On" and/or "Modified On" these will be renamed to be called "Created On_1" and/or "Modified On_1" and any previous uses of these properties (in Favorites, Formulas etc...) will be updated. Use in MQL (including MQL filters) will not be updated and, as a result, any previous MQL using "Created On" and "Modified On" will now use Mingle's predefined properties of the same name in the query.
Installing the software
Windows
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080.
- Run the Mingle uninstaller to remove your current installation. The uninstaller will stop the Mingle service if it is currently running.
- Run the new installer.
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
If you do not uninstall Mingle manually and try to install a newer version at the same location as an existing installation, Mingle will automatically uninstall the existing installation of Mingle before installing the new version.
OS X
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080. These are both visible from the Mingle launcher application window.
- Stop Mingle and quit the Mingle launcher application.
- Drag the new copy of the Mingle application (Mingle_3_0_xxxxx.app) into your Applications directory (overwriting the old Mingle).
- Start Mingle
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Linux/Unix (except Solaris)
- Note the location of the Mingle data directory on which Mingle is currently running. This is contained in the mingle.properties file in the Mingle data directory.
- If the Mingle server is currently running, stop it using the './MingleServer stop' command inside the 'mingle' application directory.
- Untar the newly downloaded archive.
- Start Mingle, using './MingleServer --mingle.dataDir=/path/to/your/data start' where /path/to/your/data is the location of your data directory.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Solaris
The steps to install on Solaris are very similar to that on any other UNIX except
- You would use the UNIX zip installer rather than the tar.gz installer due to the fact that the default Solaris tar command is incompatible with the format with GNU tar.
- You will have to ensure that the MingleServer script in the application directory has execute permissions.
After installation is complete...
Configuring Mingle's authentication
The authentication settings for Mingle are controlled through the [mingle_data_directory]/config/auth_config.yml file. This file is created by default on all brand new installations. For a detailed explanation of how to change Mingle's authentication please see here.
Advanced configuration
For further information on configuring Mingle see here.
Upgrading from Mingle 2.2
Before you get started
Starting with Mingle 3.0 MySQL will no longer be supported. All existing MySQL users will need to migrate their data to Postgres or Oracle before upgrading to Mingle 3.0. See here for help migrating to Postgres or Oracle.
These instructions are for upgrading from Mingle 2.2 to Mingle 3.0. Look here to see how to upgrade from Mingle 2.3 and here to see how to upgrade from Mingle 2.3.1. Upgrades from earlier versions such as 1.0, 1.1, 2.0, 2.0.1, 2.1 and specifically, the 1.0 Early Access & 2.0 Early Access versions are not supported.
- Please ensure that no-one, other than Mingle administrators completing the upgrade, has access to Mingle during the upgrade process. We expect that the upgrade of Mingle is completed by Mingle administrators only.
- The upgrade to 3.0 involves migration of your existing data which is a very sensitive process. We strongly recommend that you make a backup of the Mingle data directory and your database before starting the upgrade process. DO NOT SHUT DOWN THE SERVER IN THE MIDDLE OF THE UPGRADE PROCESS AT ANY COST.
- ANY TEMPLATES THAT WERE INSTALLED WITH THE PREVIOUS RELEASES WILL BE REPLACED. This has no impact on any of your existing projects or any templates that you have created yourself. If you have modified the pre-installed templates and wish to keep them you must export them and then import them using a different name before the upgrade.
- The Mingle database will be upgraded and any projects in your 2.2 database will be upgraded and fully usable as soon as you start a newly installed 3.0 Mingle server.
- Any old project export files (.mingle files) can be directly imported into the 2.3.1 version of the application. They will be automatically upgraded upon import.
- If you are migrating to Mingle 3.0 and have properties already called "Created On" and/or "Modified On" these will be renamed to be called "Created On_1" and/or "Modified On_1" and any previous uses of these properties (in Favorites, Formulas etc...) will be updated. Use in MQL (including MQL filters) will not be updated and, as a result, any previous MQL using "Created On" and "Modified On" will now use Mingle's predefined properties of the same name in the query.
Installing the software
If you have an existing Mingle configuration that you would like preserved copy your existing mingle.properties file, which can be found in the previous installation directory of Mingle, into your Mingle data directory before you start Mingle 3.0. Please refer to the mingle.properties.example file in your Mingle 3.0 installation folder as an example of the latest mingle.properties format.
Windows
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080.
- Run the Mingle uninstaller to remove your current installation. The uninstaller will stop the Mingle service if it is currently running.
- Run the new installer.
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
If you do not uninstall Mingle manually and try to install a newer version at the same location as an existing installation, Mingle will automatically uninstall the existing installation of Mingle before installing the new version.
OS X
- Note the location of the Mingle data directory and the port on which Mingle is currently running. Typically, the Mingle data directory is in your home directory (C:\Documents and Settings\[username]\Mingle) and the port is 8080. These are both visible from the Mingle launcher application window.
- Stop Mingle and quit the Mingle launcher application.
- Drag the new copy of the Mingle application (Mingle_3_0_xxxxx.app) into your Applications directory (overwriting the old Mingle).
- Start Mingle
- Specify the same data directory and port as the previous installer.
- Specify a config directory. Unless you specifically need to use another location we recommend using a sub-directory inside the Mingle data directory (such as /dataDir/config) as your config directory. Mingle will automatically move the existing mingle.properties file from the specified data directory to the config directory. The installer will automatically start the new Mingle service when it completes.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Linux/Unix (except Solaris)
- Note the location of the Mingle data directory on which Mingle is currently running. This is contained in the mingle.properties file in the 'mingle' application directory.
- Copy the mingle.properties file that is in the 'mingle' application directory.
- If the Mingle server is currently running, stop it using the './MingleServer stop' command inside the 'mingle' application directory.
- Untar the newly downloaded archive.
- Using the mingle.properties.example file in your Mingle installation folder as an example of the latest mingle.properties format, reformat your existing mingle.properties file and move this into your data directory. Any missing entries will be set to their default values.
- Start Mingle, using './MingleServer --mingle.dataDir=/path/to/your/data start' where /path/to/your/data is the location of your data directory.
- Open your browser to any Mingle page. You will be walked through the upgrade steps. All existing project data will be upgraded for continued use.
Solaris
The steps to install on Solaris are very similar to that on any other UNIX except
- You would use the UNIX zip installer rather than the tar.gz installer due to the fact that the default Solaris tar command is incompatible with the format with GNU tar.
- You will have to ensure that the MingleServer script in the application directory has execute permissions.
After installation is complete...
Configuring Mingle's authentication
The authentication settings for Mingle are controlled through the [mingle_data_directory]/config/auth_config.yml file. This file is created by default on all brand new installations. For a detailed explanation of how to change Mingle's authentication please see here.
Advanced configuration
For further information on configuring Mingle see here.
What's new in Release 2.3
This page also includes information about performance improvements available in Mingle 2.3.1.
Mingle 2.3 has, in addition to many usability enhancements and bug fixes, the following new features:
Introducing card ranking
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.
Click here to read about the card ranking.
Enhanced card printing
You can now print a single Mingle card including the entire Mingle description, all properties and comments.
Click here to learn more about printing cards in Mingle.
Increased avaliability of project variables
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.
Click here to find out where you can use project variables in Mingle.
Enhanced reporting features
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.
Click here to learn about cross project reporting in Mingle.
In Mingle 2.3 we have extended the Mingle Macro Development Toolkit by allowing custom macros to output JavaScript.
Click here to learn more about building a customized macro.
Transitions & Workflow
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.
Click here to read about the transition filters.
Mingle 2.3 introduces the ability to 'Generate a transition workflow'. This helps users to generate transitions according to their specific workflow.
Click here to read about the transition workflow generator.
Database support
Mingle now supports Oracle 10g.
Click here to learn about using Mingle with Oracle.
Easier upgrades and enhanced configuration
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.
Click here to learn about configuring Mingle.
Click here to learn more about Mingle's advanced configuration options.
Automatic user management
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.
Click here to read about adding all users as team members.
Performance improvements
Mingle 2.3.1 includes a variety of performance improvements especially with regard to grid and tree view card loading.
Click here to read about configuring performance settings in the grid view.
Additions to the tree view
Mingle 2.3.1 now includes the ability to expand and collapse children cards in the tree view.
Click here to read about the ability expand and collapse sub trees in the tree view.
What's new in Release 2.2
Mingle 2.2 has, in addition to many usability enhancements and bug fixes, the following new features:
New reporting features and enhancements
The Mingle Macro Development Toolkit provides users the ability to write custom reports and visualizations against Mingle project data.
Click here to read about building your own macros.
All charts now support sizing parameters, ensuring that all labels, legends and axes can be seen.
Click here to read about charting syntax.
Card quick add enhancements
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.
Click here to read about the card quick add enhancements.
New API features
The REST API now includes the ability to add, update, or remove attachments.
Click here to read about the attachments API.
The REST API now includes the ability to create and update wiki pages.
Click here to read about the wiki API.
Ability to delete a card that is a member of a tree
A card's membership in one or more trees will no longer prevent its deletion.
Click here to read about deleting cards from a tree.
User and project team management enhancements
The user and project team pages now have pagination and search capabilities to ease user management.
Click here to read about managing users in Mingle.
Click here to read about managing project team members.
Enhanced Subversion source integration
Mingle 2.2 now supports source integration with Subversion 1.5.
Click here to read more about Mingle source repository integration.
What's new in Release 2.1
Mingle 2.1 has, in addition to many usability enhancements and bug fixes, the following new features.
New transition features
Moving cards on the card wall can now trigger transitions that you have set up 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.
Click here to read more about automated transitions in the grid view.
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.
Click here to read more about transitions in Mingle.
Support for read-only and anonymous users
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.
Click here to read more about the different user roles in Mingle.
Mingle 2.1 supports Anonymous Access, but this is a premium feature that is not part of the general access release. Please contact ThoughtWorks Studios for additional details about this feature, and pricing details for the same.
New reporting features
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.
Click here to read more about these MQL features in 2.1.
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.
Click here to read more about pivot tables in Mingle.
MQL based filtering
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.
Click here to read more about filtering by MQL.
Enhanced hierarchy views
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.
Click here to read more about the hierarchy view.
A brand new tree view
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.
Click here to read more about the tree view.
New API features
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.
Click here to read about the cards API and enhancements.
Full Card Property Support
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.
Click here to read about card relationship properties.
Help! Everyone is read only
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.
Click here to read more about Mingle licensing and resolving any licensing issues.
If you aren't familiar with the Release 2.0.1 of Mingle, check out the section below.
What's new in Release 2.0.1
The following, in addition to many enhancements across the board, are the new features in Release 2.0.1 of Mingle.
Support for Perforce integration
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.
Click here to read more about configuring Perforce integration for your project.
Single sign on support for JA-SIG Central Authentication Service
Support for Single Sign On is provided through a plugin. This authentication plugin supports the JA-SIG Central Authentication Service.
Click here to read more about configuring single sign on.
Get a list of all projects through the API
The REST API can now be used to query a Mingle instance for all projects on it.
Click here to read more about the Mingle REST API.
Mingle now comes with all the help documentation packaged
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.
Please note though, that the online help will be updated on a fairly regular basis, and so will be more up-to-date than the packaged help. But you can still use the packaged help as a fallback mechanism for when internet access is not available.
You can access your local help at http://your.mingle.instance:port/help/index.html
If you aren't familiar with the Release 2.0 of Mingle, check out the section below.
What's new in Release 2.0
These are the great new features and other improvements delivered in Release 2.0 of Mingle
Card trees - a new way of working with cards in Mingle
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.
Click here to read more about working with card trees.
Aggregate properties
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.
Click here to read more about working with aggregate properties.
RESTful API
Mingle now provides a RESTful API which allows you to integrate it with other systems.
Click here to read more about the Mingle API.
Project level variables
Set project level variables that can be used in MQL, transitions and filters
Click here to read more about working with project level variables.
Formula properties
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.
Click here to read more about working with formula properties.
Cross project reporting
You can now create consolidated reports across a set of projects.
Click here to read more about cross project reporting.
Customizing card types
- Card Defaults for individual Card types
- Reordering of display properties on cards by Card type
Click here to read more about changes to card types.
Charts and tables in Card descriptions
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
Favorites and tabs
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 features
- 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)
Click here to read more about using the new wiki features.
Standard Mingle templates
You can see how the new features of Mingle 2.0 have been incorporated and used in the standard Mingle templates.
Click here to read more about standard Mingle templates.
Enhanced Subversion integration
- Easier integration with multi-project Subversion repositories
- Support of certificate based login for Subversion
Click here to read more about configuring Subversion integration.
Authentication
- Support for group authentication in the LDAP plugin
SMTP
- SMTP TLS encryption
- SMTP Configuration Console
Click here to read more about configuring Mingle's connection to your SMTP server.
If you aren't familiar with the Release 2.0 of Mingle, check out the section below.
What's new in Release 2.0
These are the great new features and other improvements delivered in Release 2.0 of Mingle
Card trees - a new way of working with cards in Mingle
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.
Click here to read more about working with card trees.
Aggregate properties
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.
Click here to read more about working with aggregate properties.
RESTful API
Mingle now provides a RESTful API which allows you to integrate it with other systems.
Click here to read more about the Mingle API.
Project level variables
Set project level variables that can be used in MQL, transitions and filters
Click here to read more about working with project level variables.
Formula properties
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.
Click here to read more about working with formula properties.
Cross project reporting
You can now create consolidated reports across a set of projects.
Click here to read more about cross project reporting.
Customizing card types
- Card Defaults for individual Card types
- Reordering of display properties on cards by Card type
Click here to read more about changes to card types.
Charts and tables in Card descriptions
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
Favorites and tabs
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 features
- 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)
Click here to read more about using the new wiki features.
Standard Mingle templates
You can see how the new features of Mingle 2.0 have been incorporated and used in the standard Mingle templates.
Click here to read more about standard Mingle templates.
Enhanced Subversion integration
- Easier integration with multi-project Subversion repositories
- Support of certificate based login for Subversion
Click here to read more about configuring Subversion integration.
Authentication
- Support for group authentication in the LDAP plugin
SMTP
- SMTP TLS encryption
- SMTP Configuration Console
Click here to read more about configuring Mingle's connection to your SMTP server.
What's new in Release 2.0.1
The following, in addition to many enhancements across the board, are the new features in Release 2.0.1 of Mingle.
Support for Perforce integration
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.
Click here to read more about configuring Perforce integration for your project.
Single sign on support for JA-SIG Central Authentication Service
Support for Single Sign On is provided through a plugin. This authentication plugin supports the JA-SIG Central Authentication Service.
Click here to read more about configuring single sign on.
Get a list of all projects through the API
The REST API can now be used to query a Mingle instance for all projects on it.
Click here to read more about the Mingle REST API.
Mingle now comes with all the help documentation packaged
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.
Please note though, that the online help will be updated on a fairly regular basis, and so will be more up-to-date than the packaged help. But you can still use the packaged help as a fallback mechanism for when internet access is not available.
You can access your local help at http://your.mingle.instance:port/help/index.html
If you aren't familiar with the Release 2.0 of Mingle, check out the section below.
What's new in Release 2.0
These are the great new features and other improvements delivered in Release 2.0 of Mingle
Card trees - a new way of working with cards in Mingle
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.
Click here to read more about working with card trees.
Aggregate properties
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.
Click here to read more about working with aggregate properties.
RESTful API
Mingle now provides a RESTful API which allows you to integrate it with other systems.
Click here to read more about the Mingle API.
Project level variables
Set project level variables that can be used in MQL, transitions and filters
Click here to read more about working with project level variables.
Formula properties
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.
Click here to read more about working with formula properties.
Cross project reporting
You can now create consolidated reports across a set of projects.
Click here to read more about cross project reporting.
Customizing card types
- Card Defaults for individual Card types
- Reordering of display properties on cards by Card type
Click here to read more about changes to card types.
Charts and tables in Card descriptions
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
Favorites and tabs
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 features
- 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)
Click here to read more about using the new wiki features.
Standard Mingle templates
You can see how the new features of Mingle 2.0 have been incorporated and used in the standard Mingle templates.
Click here to read more about standard Mingle templates.
Enhanced Subversion integration
- Easier integration with multi-project Subversion repositories
- Support of certificate based login for Subversion
Click here to read more about configuring Subversion integration.
Authentication
- Support for group authentication in the LDAP plugin
SMTP
- SMTP TLS encryption
- SMTP Configuration Console
Click here to read more about configuring Mingle's connection to your SMTP server.
What's new in Release 2.0
These are the great new features and other improvements delivered in Release 2.0 of Mingle
Card trees - a new way of working with cards in Mingle
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.
Click here to read more about working with card trees.
Aggregate properties
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.
Click here to read more about working with aggregate properties.
RESTful API
Mingle now provides a RESTful API which allows you to integrate it with other systems.
Click here to read more about the Mingle API.
Project level variables
Set project level variables that can be used in MQL, transitions and filters
Click here to read more about working with project level variables.
Formula properties
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.
Click here to read more about working with formula properties.
Cross project reporting
You can now create consolidated reports across a set of projects.
Click here to read more about cross project reporting.
Customizing card types
- Card Defaults for individual Card types
- Reordering of display properties on cards by Card type
Click here to read more about changes to card types.
Charts and tables in Card descriptions
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
Favorites and tabs
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 features
- 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)
Click here to read more about using the new wiki features.
Standard Mingle templates
You can see how the new features of Mingle 2.0 have been incorporated and used in the standard Mingle templates.
Click here to read more about standard Mingle templates.
Enhanced Subversion integration
- Easier integration with multi-project Subversion repositories
- Support of certificate based login for Subversion
Click here to read more about configuring Subversion integration.
Authentication
- Support for group authentication in the LDAP plugin
SMTP
- SMTP TLS encryption
- SMTP Configuration Console
Click here to read more about configuring Mingle's connection to your SMTP server.