What happened:
After a rescoring status has been set (e.g. Not Exploitable), users cannot add new comments while keeping the same status. The comment is not persisted when saving the rescoring entry if no status change is made.
What you expected to happen:
Users should be able to add new comments independently of the rescoring status. Comment-only updates should be saved even when the rescoring status remains unchanged.
How to reproduce it (as minimally and precisely as possible):
- Open an issue in the Rescoring UI.
- Set the rescoring status to Not Exploitable and save.
- Reopen the rescoring entry.
- Add new the comment field without changing the rescoring status.
- Save the changes. (Button will be enable if there is another issue selected and rescored)
- Observe that the comment is not persisted.
Workaround:
- Change the status from Not Exploitable to another status.
- Add the comment.
- Change the status back to Not Exploitable.
- Save the changes.
- Observe that the comment is now persisted.
Anything else we need to know:
This appears to be a frontend issue where comment-only changes are not detected as modifications. The save operation seems to require a status change before updates are persisted.
Environment:
- Open Delivery Gear Dashboard: Build: 0.430.0
- Browser: chrome
- OS: mac
What happened:
After a rescoring status has been set (e.g. Not Exploitable), users cannot add new comments while keeping the same status. The comment is not persisted when saving the rescoring entry if no status change is made.
What you expected to happen:
Users should be able to add new comments independently of the rescoring status. Comment-only updates should be saved even when the rescoring status remains unchanged.
How to reproduce it (as minimally and precisely as possible):
Workaround:
Anything else we need to know:
This appears to be a frontend issue where comment-only changes are not detected as modifications. The save operation seems to require a status change before updates are persisted.
Environment: