nus-pe-bot
commented
4 years ago Team's Response
Hi tester,
Thanks for testing our product. This behaviour is intended.
The modules listed under this message; 'Some modules have already been assigned...', are actually the modules which the user tries to 'reassign' to that requirement, using the requirement assign command. (They are not a list of all modules which are already under that requirement.)
In the case where the user tries to 'reassign' modules to a requirement, the requirement assign command will stop those modules that have already been assigned to the requirement, and reflect it under that message; 'Some modules have already been assigned'.
In the example you have illustrated, there are no such modules, which the user tries to 'reassign', in the requirement assign command, hence no module(s) are reflected under that list.
Since, the behaviour is intended, I'm rejecting this issue as a bug.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I do not agree with this statement. I do feel that the modules that are already assigned should reflect all the modules already assigned to the requirement column, as it is clearly stated in the description. It does not make any sense if the module is reassigned and will be the only module showing up in the description.
Instead you could change the description to better reflect what it actually does, instead of leaving it to be quite ambiguous.
By adding a new requirement, the modules assigned under SS0 in the description box does not show the other modules assigned to this requirement