[WEB-584] fix: draft issue management with workspace specific local storage #3822
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sriramveeraghanta
approved these changes
Feb 28, 2024
vamsikrishnamathala
pushed a commit
that referenced
this pull request
Aug 7, 2025
* chore: use description json to render content * chore: update base page instance
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses the issue encountered when attempting to create an issue within a workspace but encountering unexpected behavior, such as the loss of data when the issue modal is closed without saving. To mitigate this issue, we implemented a solution that involves storing draft issues in local storage. However, a subsequent problem arose where draft issues created in one workspace appeared in another workspace upon switching between them.
To resolve this issue, we have updated the state management system to ensure that draft issues are workspace-specific. Now, when saving a draft issue, it will be associated with the current workspace, preventing cross-workspace interference and providing a more seamless user experience. This enhancement ensures that draft issues are retained and accessible only within their respective workspaces.