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

[bug]: Issues accepted from inbox with no state set become inaccessible #5768

Open
1 task done
PolarisWasInDenial opened this issue Oct 7, 2024 · 2 comments
Open
1 task done
Assignees
Labels
🐛bug Something isn't working

Comments

@PolarisWasInDenial
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Currently, when an issue is accepted from Inbox with no state set, it becomes entirely inaccessible - being set to a state of 'triage'. Issues in this state cannot have a new state set, cannot be accessed via direct links to the issue, and only can be read from the 'Accepted' tab of the inbox.

Steps to reproduce

  1. Submit a test issue to a project inbox
  2. Open inbox while logged in
  3. Accept issue without assigning a status.
  4. Attempt to navigate to issue.
  5. Issue is not visible as an issue - only showing in user activity logs and inbox logs.

Environment

Production

Browser

Mozilla Firefox

Variant

Self-hosted

Version

Plane One v1.3.1

@PolarisWasInDenial PolarisWasInDenial added the 🐛bug Something isn't working label Oct 7, 2024
@pushya22
Copy link
Collaborator

pushya22 commented Oct 8, 2024

Hi @PolarisWasInDenial thanks for bringing this to our notice. Default state will be always applied when accepting an issue from inbox. Not sure in what scenario there is an empty state while accepting an, it will be helpful if you could share more details on how to reproduce the issue.

@PolarisWasInDenial
Copy link
Author

Hi @PolarisWasInDenial thanks for bringing this to our notice. Default state will be always applied when accepting an issue from inbox. Not sure in what scenario there is an empty state while accepting an, it will be helpful if you could share more details on how to reproduce the issue.

I'll try to get a more direct replication scenario after I get home later today; for now, here's an example of one of the issues that led to us encountering this issue:

Screenshot_20241009_095011_Chrome.png

In short, upon acceptance, the issues are assigned a non-existent default state of triage, resulting in them more or less falling into this limbo state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants