Skip to content
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.

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

dev/core#1262 - Fix case status order in case type settings page #15319

Merged

Conversation

vinuvarshith
Copy link
Contributor

Overview

In the case type settings/config page, where we have a tab for 'Case status' that lists all case statuses from which we can select the ones we want for that case type.
This list of case statuses are not ordered by their weight which would the correct way to list these.

Before

I have added a screenshot of the page when adding a new case type. In this the case status 'first' has the lowest weight and so I expect to see it on the top of the list.
screenshot-localhost-2019 09 18-11_02_06

After

Now the case statuses are sorted by their weight.
screenshot-localhost-2019 09 18-13_22_24

Technical Details

In crmCaseType.js, where case statues are obtained (reqs.caseStatuses), I have added 'sort: 'weight'' to the options array.

@civibot
Copy link

civibot bot commented Sep 18, 2019

(Standard links)

@civibot civibot bot added the master label Sep 18, 2019
@demeritcowboy
Copy link
Contributor

  • General standards
    • [r-explain] PASS
    • [r-user] PASS
    • [r-doc] PASS
    • [r-run] PASS Looks good to me. Basic tasks like creating/editing case types and creating/editing cases still works. It also still sorts properly on the case type edit screen if you uncheck one of the statuses.
  • Developer standards
    • [r-tech] PASS
    • [r-code] PASS
    • [r-maint] N/A
    • [r-test] PASS

@colemanw colemanw merged commit 40cccf4 into civicrm:master Sep 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants