Targetprocess can automagically set properties based on selected view filters.
Let's consider a situation where you have a view that shows User Stories and Bugs from the current Release. You click the Add button and create a new User Story. Targetprocess is smart enough to assign this User Story to the current Release.
The algorithm understands filters like this:
| View filter | Quick Add action results |
|---|---|
| ?Iteration is Current | Assign card to the current Iteration |
| ?AssignedUser.Where(it is me) and Iteration.IsCurrent == True | Assign card to logged-in user and current Iteration |
| ?Release is Current | Assign card to the current release |
| EntityState is 'Open' | Put card into Open state |
| ?Project.Name is 'Green planet' | Put card into 'Green planet' Project |
| ?Feature is 'Save the whales' | Put User Story into 'Save the whales' Feature |
If you mix several filters with an AND condition, several rules will be applied.
If you use an OR condition in the filter, automatic assignments will NOT work (in this case, there is ambiguity that can't be resolved).
Setting values for the Custom Fields used in filters is not supported.
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.