Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 916
    • Issues 916
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #445

Closed
Open
Opened Oct 15, 2018 by justinfreeman (Agileware)@justinfreeman🚴🏿Developer

Proposal - Custom Fields, Is this Field Searchable? option should be enabled by default, currently it is disabled by default

When creating Custom Fields the option Is this Field Searchable? is disabled by default and as a result any new Custom Field is not searchable. This is frustrating since there is rarely a case when you would not want a field to be available in search. For end users the experience of adding a Custom Field in CiviCRM is like this:

  1. Add the Custom Field
  2. Add some data to CiviCRM using the new Custom Field
  3. Open Search and try to search using the new Custom Field, it is not shown
  4. Confusion about why it is not shown in Search
  5. Finally, navigate back to the Custom Field and enable the option, Is this Field Searchable?
  6. Return to Search and bingo! There it is.
  7. Repeat steps for every Custom Field created.

Proposed Change

The Is this Field Searchable? option should be enabled by default, making new Custom Fields available in Search when created - reducing potential confusion as noted above. The user would then have to explicitly disable this option to remove from search.

Agileware Ref: CIVICRM-964

Edited Oct 15, 2018 by justinfreeman (Agileware)
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#445