Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving the header and description edits in quick succession causes changes to revert #1028

Open
seox123 opened this issue Nov 10, 2022 · 4 comments

Comments

@seox123
Copy link

seox123 commented Nov 10, 2022

Describe the bug
Saving the edit for the bug report description, followed by the edit for the bug report header and type, results in the description edit to revert back to the original unedited version.

To Reproduce
Steps to reproduce the behavior:

  1. Go to any bug report
  2. Click on 'Edit' in the top right corner, above the severity level.
  3. Click on 'Edit' in the top right corner of the description box.
  4. Make changes to the bug report header and bug report description.
  5. Click on 'Save' in the bottom right corner of the description box.
  6. Quickly click on 'Save' in the top right corner of the bug report, above the severity level.
  7. The edited result of the bug report header is reflected, but the changes to the bug report description revert back to the original unedited version.

Expected behavior
I would expect both the header and the bug report description to be saved with their edited versions.

Desktop:

  • OS: [Windows 11]
  • Browser [Google Chrome]
  • Version [107.0.5304.87 (Official Build) (64-bit)]
@damithc
Copy link
Contributor

damithc commented Nov 11, 2022

Thanks for reporting this @seox123

CATcher team, perhaps check if a similar thing happens when using the GitHub UI (i.e., is the problem on GitHub side or CATcher side)?

@kkangs0226
Copy link
Contributor

I was unable to reproduce the bug, @CATcher-org/developers please check and let me know if you encounter the same bug

@chunweii
Copy link
Contributor

I believe this bug is related to #865. I attempted to fix it in #860 but it was put on hold. The issue needs some investigation

@vigneshsankariyer1234567890
Copy link
Contributor

I've just made a PR that may resolve this issue by disabling the button until the request was complete in #1172

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants