cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Minimize the picklist value list in UI and the list should be specific to project doc.

0 Kudos

Minimize the picklist value list in UI and the list should be specific to project doc.

Use Case 1: SMEs and/or other groups (e.g. Project Lead) shall get the possibility to pick  Attribute pick list values from the existing, that should be shown in specific Projects/Documents and with that optimize/minimize the picklist in the UI.

 
Steps:
  1. On project 1, user is on Requirement
  2. Notice Assigned Reviewer dropdown
  3. Actual: notice that the entire Assigned Reviewer is displayed and is very long (according to Alonzo: this is because its directly coming from dynamic group).
  4. Expected: The list of Assigned Reviewer should be only related to that project.
    1. Same with Lead Reviewer.
  5. On the project we need to do What Attribute Configuration we should narrow down.

Use case 2: Multi-edit pick-list values need to follow the Attribute Configuration.

When I go to do the Item-->Edit (multi-edit ability where I can mass-update multiple requirements for the same attribute/values), the drop-down list there needs to reflect the applicable values per the Attribute Configuration that the requirements contained by a document has for that document's Attribute Configuration to help limit the choices I am presented with.  This makes it very difficult to select the ones I need to.  
To solve this problem, I'm suggesting that Multi-edit pick-list values need to follow the Attribute Configuration to present the user with only those values applicable for the requirements that are constrained by the document they are found in...per the attribute configuration of that document.

Steps:

  1. Select a requirement and edit.
  2. Select any attribute and verify the list of picklist values. It is very specific to that Document/Project (narrowed down to the specific list related to that attribute configuration on that document, which is good.
  3. Now, instead of doing single-edit, do multi-edit. So select Multiple requirements within same document, and click edit.
  4. Verify the same attribute to check the listed values (same attribute as in step 2).
  5. Actual: The long list (ALL values from the database listed in this list when we do multi-edit, unlike of specific list as in step 2).
  6. Expected: Even in Multi-edit situation, the picklist values should follow the Configuration Attribute on that document.