ref(jira-server): Remove legacy pipeline setup views#117311
Merged
evanpurkhiser merged 1 commit intoJun 10, 2026
Merged
Conversation
Now that the API-driven pipeline is in place, drop the legacy InstallationConfigView, OAuthLoginView, and OAuthCallbackView classes (and the InstallationForm they used), the associated Django template, and the legacy-flow tests. get_pipeline_views() now returns an empty list; get_pipeline_api_steps() is the only setup path.
github-actions
Bot
added
the
Scope: Backend
JoshFerge
approved these changes
Jun 10, 2026
evanpurkhiser
deleted the
evanpurkhiser/ref-jira-server-remove-legacy-pipeline-setup-views
branch
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
2 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.
Now that the API-driven pipeline is in place (#117181 backend, #117185 frontend, both merged), drop the legacy
InstallationConfigView,OAuthLoginView, andOAuthCallbackViewclasses (and theInstallationFormthey used), the associated Django template, and the legacy-flow tests.get_pipeline_views()now returns an empty list;get_pipeline_api_steps()is the only setup path.This removes the server-rendered fallback that completes any in-flight installs, so it should not merge until the API flow has been validated in production.
Part of VDY-104.