This repository was archived by the owner on Sep 3, 2025. It is now read-only.
feat(ui): allow project to have a display name separate from its key #5616
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
wssheldon
reviewed
Dec 13, 2024
wssheldon
approved these changes
Dec 13, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 allows admins to select a display name for projects and renames the current
namefield in the UI as the "key". In the database migration, thedisplay_namefor all projects is set to the existingnamefield value. Fixes DISDEV-242.We also fix an error in the Slack command
\dispatch-update-incidentmodal that threw an error when the user tried to change the project by making the project field read-only.