Project variables
Introduction
Project variables allow you to specify in one place a value which can then be referenced in many places within your Mingle project. Using a project variable instead of hard-coding a specific value means that value can be changed in one place and immediately the new value will be reflected throughout the project.
Any time you find yourself entering a constant into a MQL query, it's worth considering if it might be better to use a project variable instead. This is especially likely if you find yourself using the same constant in several places.
You can use project variables to store values that can be used in
- card transitions - project variables can be assigned to card properties in transitions, e.g. Transition "Set Current Iteration" might update a card's iteration number property to equal the project variable called "Current Iteration".
- MQL statements - project variables can be referenced as constants from within MQL queries, e.g.
'Iteration Number' = (Current Iteration)
. - Filter conditions - project variables can be used in filter conditions, this also applies to tree filters.
You can create the following types of project variable
- Text - any text value of up to 255 characters in length.
- Numeric - any numeric value.
- Selected from team list - any project team member.
- Date - any date.
- Card - a reference to a card.
If you created a new project based on a template, the project may include some project variables by default. You can update or remove any extra project variables as required.
If templates that contain project variables are imported without cards, then any project variable references a specific card, then it will be changed to be (not set).