Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • CiviCRM Core CiviCRM Core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 1.1k
    • Issues 1.1k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • DevelopmentDevelopment
  • CiviCRM CoreCiviCRM Core
  • Issues
  • #186
Closed
Open
Issue created Jun 15, 2018 by totten@tottenOwner

Consider phasing out various custom-searches

There are several custom-searches. I'm sometimes confused by the behavior with them -- and generally feel suspicious because (a) they don't have much test coverage and (b) they involve lots of edge-cases/combinations and (c) they're not very visible to users (ie not much foot-traffic), (d) I sort think they were written quickly a long time ago, and (e) there's overlap with reporting.

It would be useful to re-evaluate each of them and perhaps phase-out some. For example, a phase-out might look like this:

  1. Create a new extension
  2. Move the search(es) to the extension
  3. Bundle the extension with the main tarball
  4. Disable by default
  5. Add an upgrade message telling people how to get them back
  6. Test the upgrade/transition process to ensure it works

NOTE: Take care when disabling/re-enabling. There might be references to the searches in various places (e.g. smart-group definition; custom navigation), and you want the old IDs/URLs to continue work.

Edited Jun 15, 2018 by totten
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking