I had some some nice views setup with a filter for ‘type is any’

when we then added a new card type to the project, those views broke. I’m not sure this is so much of a bug as it is an annoyance. What’d be nice is if mingle would figoure out how to maintain these views by altering the filters so that ‘type is any’ becomes type in (‘story’ ‘defect’ ‘overhead’) or something along those lines…

Ben

When you say the views broke you mean that they continued to return ‘any’ card type when in fact you wanted them to return only the card types that ‘any’ was before you added the new card type. Is that correct?

If this is the case, this is behaving as designed. Although I can understand the behaviour you expected this a tricky one as it is equally likely that someone else may have created a view where they did want all cards types to be returned regardless of the card types newly created in the project.

• currently – you can create filters that add OR conditions between values of the same property e.g. Type is Story OR Type is Defect. These conditions will remain the same when a new card type is added to the project or even if an existing card type name is updated
• coming soon – Mingle will allow card views to be filtered by MQL. This will improve card filtering and allow you to more easily filter the view to specific criteria. For example, if you want to create a view for some cards types but not other card types you will be able to use MQL in a number of different ways to achieve this:
  • order the card types and use MQL such as Type > Story where this will select all card types that are ordered below card type of ‘Story’
  • use MQL such as Type != Defect when you want all card types but Defects
  • use MQL without specifying card types such as ‘status is new’ which will return any card types that have a status = new

I hope this helps. If I have misunderstood the issue then please let us know and we will investigate the defect.

Thanks Suzie