Skip to content

Bug: Unable to Add New Comments Without Changing Rescoring Status #466

@tanweersalah

Description

@tanweersalah

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):

  1. Open an issue in the Rescoring UI.
  2. Set the rescoring status to Not Exploitable and save.
  3. Reopen the rescoring entry.
  4. Add new the comment field without changing the rescoring status.
  5. Save the changes. (Button will be enable if there is another issue selected and rescored)
  6. Observe that the comment is not persisted.

Workaround:

  1. Change the status from Not Exploitable to another status.
  2. Add the comment.
  3. Change the status back to Not Exploitable.
  4. Save the changes.
  5. 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    🔦 Needs Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions