Remove use_role requirement to existing JT.project to make changes to JT #14278
Conversation
This file contains 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
gamuniz
approved these changes
Jul 25, 2023
AlanCoding
changed the title
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
SUMMARY
This is an adjustment to #13818
Unfortunately, I don't see any easy choices here. The "sensitive" change requirements are still suffocating.
This accomplishes the main stated goal of the prior PR and issue - which is to change the project while lacking
use_roleto the existing project. This is accomplished by the subtleobj=Nonein the call tocheck_related. It might be apparent, but I'm very opposed to the solution method in the PR 13818 because it adds more logic to an already out-of-control collection of business logic.ISSUE TYPE
COMPONENT NAME