Repository navigation
Show project and billing history in Sales opportunity modal -> dev - #2437
Merged
Merged
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
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.
Related JIRA Ticket
Not provided.
What's in this PR?
The Sales opportunity modal now shows the current billing account ID/name, an environment-specific Work link to
/projects/{projectId}/challenges, and a list of past billing account IDs/names supplied by the Projects API.All new fields are hidden when the opportunity has no billing account. The current account is omitted from the past-account list, an empty history has an explicit empty state, and unresolved names retain their IDs. A missing project does not produce a Work link. Includes URL validation, modal regression tests, and documentation.
Validation
yarn lintpassed.NODE_OPTIONS=--max-old-space-size=8192 yarn run buildpassed with existing warnings. The clean build exceeded Node's default 4 GB heap limit, so validation used an 8 GB limit.Dependencies and deployment
Deploy in this order: