Card properties are custom attributes that you can define and then apply to a card type, they are analogous to custom fields. Card properties can be applied to one or more card types, and can have their allowable set of values restricted in a number of ways. You can choose whether or not to show or hide properties (so they're visible/invisible on cards), and lock or unlock properties (so that only project administrators can add or change property values).

Types of card property

• Managed List property - restricted to an enumerated list, of either text or numeric values. Unless the Managed List property is also locked, team members can dynamically add new allowed values while editing cards. Managed list properties can be used in filter conditions and card transitions. Managed number list properties are affected by the project numeric precision.
• Any Number property - allows a user the freedom to enter any number for this property. The decimal precision of the value will be determined by the project numeric precision. Mingle will not manage these values.
• Any Text property - allows a user the freedom to enter any text for this property. Mingle will not manage these values
• Date property - restricted to any date.
• Formula property - derived from other numeric or date card properties (see formula properties for more details)
• Team member property - restricted to the list of the current team members.
• Standard properties - special properties which are automatically assigned to any card, these are Type, Name, Number and Description. Type is restricted to the set of defined Card Types; Number is an automatically incrementing unique integer; the other two are text fields.
• Aggregate properties - defined as part of a Card tree, aggregate properties display the Sum, Average, Min, Max or Count of properties of cards lower in a card tree
• Relationship properties - created and named as part of creating a card tree, relationship properties are references in a child card that link it to its ancestors in the tree.

Attributes of card properties

• Name - every property must have a unique name, the following characters may not be used inside a property name:
• Property Values - the set of values that a card property can be assigned can be restricted to either an enumerated list (Managed Lists, Team members), or a data type (such as Any Date, or Any Number)

• Show / Hide - properties can be hidden if they are not required for data entry - for example calculated values used in reporting. Hidden card properties are not displayed in the card view, the value can only be set by declaring a default value, or via a transition, or calculated if it's a formula property.

  You can also hide a property instead of deleting it, which will retain historical data about changes to that property.

• Lock / Unlock - any Managed List property can be locked, this restricts the set of allowed values to only those predefined by the Project Administrator. Team members will not be able to dynamically add new values, however project admins can still add new values dynamically.
• Transition only? - indicates that the property can only have its value set via a transition, it will not be directly editable by team members.

• Create card properties
• Modify or Delete card properties