Open ianyong opened 3 years ago
It is the intended design of our application, which is the current implementation from AB3.
For adding a deliverable after executing a find command, we decided to reset the list because the added deliverable may not fulfil the current find criteria/keywords, hence may not appear in the existing filtered list. This may be a worse off user feedback. (Similar explanation for editing a deliverable after executing a find command).
For done command, on the other hand, the current filtered list will not be affected by the change of completion status, hence displaying the same filtered list is ideal.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your reason]
Team chose [type.FeatureFlaw
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your reason]
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your reason]
Commands input in deliverable mode:
After adding a new deliverable, the displayed list of deliverables is reset to show all deliverables. The same goes for editing. This behaviour is not defined anywhere and is inconsistent with other commands such as
done
which do not reset the displayed list.