getsentry / getsentry/sentry

"Restore organisation" message preventing user from accessing account settings

Open
#122,258 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Product Area: Settings - General Waiting for: Product Owner
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 23m
Merged PRs (30d)
607

Description

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Have a user that is owner of only one organisation and follow the steps:

  1. Delete the organisation
  2. Try to access account settings such as security page to add 2FA:
Expected Result

The use is able to access the personal account settings before the organisation is fully deleted as these settings are not related to any specific organisation.

Actual Result

The following message is presented preventing the user from continuing:
Image

In this use case, the user wants to configure 2FA to join another organisation that requires 2FA.

The current workarounds are:

  • Restoring the organisation to immediately regain access
  • Waiting for the organisation deletion to complete.

Possible solutions are:

  • Allow user to close the warning and access the personal settings page
  • Only show the message when accessing organisation specific pages ORG_SLUG.sentry.io
Product Area

Settings - General

Link

No response

DSN

No response

Version

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue at /settings/account/security/ and /settings/account/details/ after deleting the user's only organisation. Trace the settings-page warning and organisation-deletion state handling, then verify that personal settings remain accessible while deletion is pending and that organisation-specific pages still show the warning when appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.