Minglepublic

Announcements

Announcements from the Mingle Team

This is a public Discussion Area  publicRSS

Announcement

    Jay Mitchell
    Bugs fixes available in Mingle 3.2
    Announcement posted August 17, 2010 by Jay Mitchell, last edited February 9, 2012
    1455 Views, 3 Comments
    Title:
    Bugs fixes available in Mingle 3.2
    Announcement:

    Hi all

    As well as a variety of new features, Mingle 3.2 includes the following bug fixes.

    Bugs related to source repositories

    • Failed to import project due to Hg password problem.[Hg plugin]
    • If P4 client is not installed, provide error message when user go to "Source" tab.

    Bugs related to LDAP

    • Prevent user login on Mingle if user does not belongs to specific ldap group.

    Bugs related to Mingle instance management

    • Mingle admins do not receive e-mails for subscriptions (unless they are also a project member)
    • "Manage Users" link causes 500 error on instance hosting more than 200 projects
    • Improve time to create project from template when Mingle has many users and many auto-enroll enabled projects

    Bugs related to MQL

    • Using NUMBER = THIS CARD.'relationship property name' in a WHERE clause should work
    • Making chart with MQL that uses DISTINCT and ORDER BY will cause SQL error.[Oracle] 

    Others bugs

    • Cross project card link will be broken if attachment's name in inline image ends with digit
    • URLs with special hyphens (en dashes and em dashes) are not rendering correctly in our wiki pages
    • Transitions on grid view are creating card version but not changing card when ranking is on
    • Provide user friendly error message when user tries to update a property which is not available to the type via the API

    Thanks

    - The Mingle Team

    Comment

     

    • Show/Hide Replies
      Olivier Grandjean
      posted August 20, 2010 by Olivier Grandjean

      Can you please explain this "NUMBER = THIS CARD.'relationship property name' in a WHERE clause should work"? I would appreciate an example.

      Thanks

      • Jay Mitchell
        posted August 20, 2010 by Jay Mitchell

        Hi Olivier,

        Suppose you have a have a property of type "Card", named "Depends On". Before Mingle 3.2, you could use the following MQL query:

        SELECT number, name WHERE NUMBER IN (THIS CARD."Depends On")

        to get all of the cards that depend on the same card that the current card depends on. However, if you used the following query:

        SELECT number, name WHERE NUMBER = THIS CARD."Depends On"

        you would get a validation error, even though the queries are semantically the same. In Mingle 3.2, we fixed MQL to allow the second query as well.

        Cheers,

        Jay

        • Olivier Grandjean
          posted August 20, 2010 by Olivier Grandjean

          Thanks Jay.

          I didn't know you could do use THIS CARD.'relationship property name' in a query. Very nice!