In previous discussions with AMD and in MUG, we have decided to move from using project types (added in the project summary view) to focusing on component work types with the goal of reducing redundant capture of similar project data.
This work includes implementing a column that aggregates all of the work types of all project components into a de-duplicated list. This list can then be added to the project summary view and the project list view. It also includes making this field advanced searchable and exportable from the list view.
Once this new field is added to the UI, we can remove the project types input in the project summary.
In previous discussions with AMD and in MUG, we have decided to move from using project types (added in the project summary view) to focusing on component work types with the goal of reducing redundant capture of similar project data.
This work includes implementing a column that aggregates all of the work types of all project components into a de-duplicated list. This list can then be added to the project summary view and the project list view. It also includes making this field advanced searchable and exportable from the list view.
Once this new field is added to the UI, we can remove the project types input in the project summary.