This article explains how to manage the Lookup and Multi Lookup fields.
There are two field types available for creating new fields: Lookup & Multi Lookup. Lookup fields are valuable for creating relationships between plans in the system. If the plan types are set up in a flat hierarchy, use lookup and multi lookup fields to create the parent to child relationships. If the plan types are set up in a hierarchy, lookup fields automatically get created and populated with the parent value for the children plans. Views can be grouped and filtered by the lookup fields. Ex: A plan can have a lookup to the program-type plan(s) to which it's associated. Or, a feature-type plan can have a lookup to the epic-type plan(s) to which it's associated.
Follow the steps to create a new plan-level field. For more information, refer to Create and Edit Plan Fields.
-
Field Type: Select Lookup or Multi Lookup.
-
Lookup Plan Type: Select from which plan type the users will select the lookup field.
Comments
1 comment
I'm not following the idea of this being a general “lookup” type of field.
This is specifically linking plans only - in the configuration of a lookup field in OnePlan, I'm not seeing where you can select a field other than the name of a different plan - that's the lowest level you can go. I would understand calling this a lookup field if I could select a plan and then select a field populated within that plan only.
The way this field currently operates, I would just call this a “Linked Plan” field, not a lookup field. As is, it doesn't deliver the same benefit of a true lookup field.
Please sign in to leave a comment.