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

Re-order Contact fields in table,DAO #26014

Merged
merged 2 commits into from
Apr 8, 2023

Conversation

eileenmcnaughton
Copy link
Contributor

Overview

Re-order Contact fields in table,DAO

This simply affects the order of the fields in the civicrm_contact table on new builds

Before

image

After

image

Technical Details

For those of us who look into the database on a regular basis, especially using a graphical interface, it can be a bit of a pain that the prime real estate is taken up by low-interest fields.

While I don't think there is any one most convenient way to order the fields this at least gets some name fields 'above the fold' and putting organization name early on means it will show for both orgs & individuals with employers

Comments

@civibot
Copy link

civibot bot commented Apr 6, 2023

(Standard links)

@civibot civibot bot added the master label Apr 6, 2023
@eileenmcnaughton
Copy link
Contributor Author

tests need adjusting to reflect - will just wait to see if anyone has order preferences

@totten
Copy link
Member

totten commented Apr 6, 2023

My bikeshed vote would be like: "id, contact_type, display_name" and then everything else. For "everything else", there are different/valid ways to do it, eg:

  • Alphabetize everything else
  • Figure rough groups of related fields (first_name/middle_name/last_name/nick_name/etc; then do_not_mail/do_not_phone/etc.)

@eileenmcnaughton
Copy link
Contributor Author

Yeah - I think madness lies in trying to do them all - I did try not to make anything existing less sane :-)

@colemanw colemanw merged commit 3303463 into civicrm:master Apr 8, 2023
@colemanw colemanw deleted the contact_order branch April 8, 2023 17:36
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