Skip to content

Fix #608 - Leads Listview Quick Charts Leads By Status shows back end… #609

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
abuzarfaris wants to merge 1 commit into
base: hotfix
Choose a base branch
from
Open

Fix #608 - Leads Listview Quick Charts Leads By Status shows back end… #609

abuzarfaris wants to merge 1 commit into from

Conversation

@abuzarfaris
Copy link
Contributor

@abuzarfaris abuzarfaris commented Feb 10, 2025 •
edited
Loading

… value instead of label of status

Description

Motivation and Context

How To Test This

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Final checklist

  • My code follows the code style of this project found here.
  • My change requires a change to the documentation.
  • I have read the How to Contribute guidelines.

@abuzarfaris
Fix SuiteCRM#608 - Leads Listview Quick Charts Leads By Status shows …
349f134 
…back end value instead of label of status
@mattlorimer mattlorimer added Status:Assessed PRs that have been tested and confirmed to resolve an issue by a core team member PR 4-8 Complexity Score given to PRs once assessed labels Jun 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

PR 4-8 Complexity Score given to PRs once assessed Status:Assessed PRs that have been tested and confirmed to resolve an issue by a core team member

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@abuzarfaris @mattlorimer