Minglepublic

Tips and Tricks

Mingle Tips and Tricks

This is a public Custom Hive  publicRSS

Mingle Tip

    Matt Quagliana
    Migrating Projects from Mingle 2.3 to Mingle 3.0
    Mingle Tip posted December 22, 2009 by Matt Quagliana
    1238 Views, 1 Comment
    Tip Name:
    Migrating Projects from Mingle 2.3 to Mingle 3.0
    Tip Description:

    For the most part, migrating a Mingle 2.3 project to Mingle 3.0 is simple and automatic. You can export the project from the Mingle 2.3 server and import it to a Mingle 3 server. Or you can upgrade your Mingle 2.3 server to Mingle 3 (after you back up per the instructions, of course.) Either way, Mingle will convert your Mingle 2.3 structure to Mingle 3.0 automatically.

    I have discovered a few small exceptions that must be fixed by hand. They are:

    (1) New Reserved words

    Mingle 3 adds new reserved words/phrases, namely 'Created On', 'Modified On' and 'Project". Essentially, these are new built-in properties on every card. If your projects have any properties (including tree properties) that conflicts with one of these, that property name will be changed. If you have a property called 'Created On' it will be renamed 'Created On_1'.

    Note that while the property name will change any MQL queries in your reports are not automatically changed to reflect the new name.

    (2) Stricter behavior of some charting properties

    The data-series chart has many properties, including x-labels-start and x-labels-end. In previous versions of Mingle it was possible to also use x-label-start and x-label-end. This behavior was not documented and should have caused an error. So if you used x-label-start/end you data series chart probably won't look correct in Mingle 3. Add an 's' to each property name and you should be good to go.

    (3) The Mingle API

    If you have developed any integrations that use Mingle's RESTful API you will have to make at least one small change for your code to work with Mingle 3.0. That change is documented here.

    --Matt Quagliana | ThoughtWorks Studios

    Comment

    • Suzie Prince
      posted December 23, 2009 by Suzie Prince

      Further to point 1., we call these properties "standard predefined properties". All predefined properties are documented here (http://www.thoughtworks-studios.com/mingle/3.0/help/card_properties.html). Property name change effects caused by a migration should be the same as a manual property name change as documented here (http://www.thoughtworks-studios.com/mingle/3.0/help/modifying_or_deleting_card_properties.html).

      With regard to point 2., this applies to data series charts only. Using x-labels (with the s) will not work on a stack chart. The documented behaviour has not changed in Mingle 3.0 and all the correct macro syntax can be found by using the Macro Editor or by referring to our help here (http://www.thoughtworks-studios.com/mingle/3.0/help/macro_reference.html).

      Also a note on expected behaviour, any incorrectly spelled macro parameters will be ignored by the macro. This applies to all macros. For example, if you use "x-label-start" instead of the expected "x-labels-start" the start point will not be honoured as the parameter "x-label-start" is not appropriate. This is the expected behaviour for all incorrect parameters. Only recognised, correctly named and placed parameters will be applied.