Skip to content

Use deployedProduct label/version in details - #249

Merged
Rashmika998 merged 1 commit into
wso2-open-operations:customer-portal-milestone-1from
dileepapeiris:feat/add-chat-details
Feb 24, 2026
Merged

Rashmika998 merged 1 commit into
wso2-open-operations:customer-portal-milestone-1from
dileepapeiris:feat/add-chat-details

Conversation

@dileepapeiris

@dileepapeiris dileepapeiris commented Feb 24, 2026 •

Copy link
Copy Markdown
Contributor

Prefer deployedProduct fields when rendering product details: Product Name now shows deployedProduct.label with a fallback to data.product, and Product Version displays deployedProduct.version (or null). This surfaces the actual deployed product info in the case details panel.

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter �N/A� plus brief explanation of why there�s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type �Sent� when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type �N/A� and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

  • Unit tests

    Code coverage information

  • Integration tests

    Details about the test cases and coverage

Security checks

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

Summary by CodeRabbit

  • Bug Fixes
    • Improved product name and version display in case details to use more accurate and reliable information sources with better handling of unavailable data.

Prefer deployedProduct fields when rendering product details: Product Name now shows deployedProduct.label with a fallback to data.product, and Product Version displays deployedProduct.version (or null). This surfaces the actual deployed product info in the case details panel.
@coderabbitai

coderabbitai Bot commented Feb 24, 2026 •

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

This PR updates the Product & Environment section in the Case Details panel to retrieve product information from deployedProduct with enhanced fallback patterns. Product Name now prefers deployedProduct.label over data.product, while Product Version uses deployedProduct.version with null fallback for safer data handling.

Changes

Cohort / File(s) Summary
Product Display Enhancement
apps/customer-portal/webapp/src/components/support/case-details/details-tab/CaseDetailsDetailsPanel.tsx
Updated Product Name to prefer deployedProduct.label with fallback to data.product; updated Product Version to use deployedProduct.version with null fallback instead of direct object reference.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Possibly related PRs

Suggested labels

Type/Improvement, App/Customer Portal, Area/Frontend, Type/UX

Suggested reviewers

  • Rashmika998
  • sacheeramesh

Poem

🐰 A product takes shape with a label so bright,
With deployedProduct fallbacks, the version's just right,
No more broken displays when the data's obscure,
Safe nullish defaults make the UI more sure! 🎯

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description includes a clear summary but all template sections beyond the initial description contain only placeholder text with no actual content filled in. Complete the required template sections including Purpose, Goals, Approach, User stories, Release note, Documentation, and other sections with concrete information about this change.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: using deployedProduct label and version fields in the details display instead of previous alternatives.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In
`@apps/customer-portal/webapp/src/components/support/case-details/details-tab/CaseDetailsDetailsPanel.tsx`:
- Around line 219-221: The render currently uses
formatValue(data?.deployedProduct?.label ?? data?.product) which treats an empty
deployedProduct.label as present; change the fallback so empty strings are
treated as missing (e.g., check deployedProduct.label?.trim()?.length > 0) and
fall back to data?.product before calling formatValue in the
CaseDetailsDetailsPanel component (the Typography with valueSx). Update the
expression that reads data?.deployedProduct?.label to perform a truthy/non-empty
check so formatValue receives the correct value.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ae53ff6 and 7928f66.

📒 Files selected for processing (1)
  • apps/customer-portal/webapp/src/components/support/case-details/details-tab/CaseDetailsDetailsPanel.tsx

@Rashmika998
Rashmika998 merged commit 236ebf6 into wso2-open-operations:customer-portal-milestone-1 Feb 24, 2026
1 check passed
@coderabbitai coderabbitai Bot mentioned this pull request Feb 24, 2026
@dileepapeiris dileepapeiris self-assigned this Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants