fix: put support admin behind feature flag#5521
Merged
Merged
Conversation
✅ Deploy Preview for bloom-flagly ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ludtkemorgan
added
the
1 review needed
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-lakeview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
emilyjablonski
left a comment
emilyjablonski
left a comment
Collaborator
There was a problem hiding this comment.
Haven't had a chance to do a full review, but if we don't add the flag with a description to feature-flags-enum.ts, then it doesn't get added when we run the script
millord
reviewed
Nov 4, 2025
millord
approved these changes
Nov 4, 2025
millord
approved these changes
Nov 4, 2025
Collaborator
Author
|
@emilyjablonski The feature flag was added in an earlier PR, including the description in feature-flag-enum.ts, we just accidentally didn't connect the actual feature behind the flag |
mcgarrye
added
ready to merge
ludtkemorgan
force-pushed
the
5503/support-admin
branch
from
83bbf95 to
b74bc2d
Compare
mcgarrye
pushed a commit
to metrotranscom/doorway
that referenced
this pull request
Nov 10, 2025
* fix: put support admin behind feature flag * fix: linting errors
9 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 #5503
Description
The new support admin was accidentally not put behind the feature flag created for it. In other words now in jurisdictions that don't want the new role can create a user with this permission level
How Can This Be Tested/Reviewed?
The new feature flag is enabled by default for Bloomington jurisdiction. The following three scenarios should be tested after a new reseed
Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: