Skip to content
GitLab
Projects Groups 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
  • Issues 1,252
    • Issues 1,252
    • 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
  • #3334
Closed
Open
Issue created Nov 15, 2019 by Michael McAndrew@michaelmcandrewDeveloper

Option to update expired memberships as part of the job.process_membership

It looks like expired memberships are excluded from job.process_membership for performance reasons.

There are (edge) cases where this is problematic. For example, lets say that I increased the grace membership period from 3 to 6 months. People whose membership ended 4 months ago will not have their membership status updated from expired to grace.

The other three membership statuses that are excluded from membership updates are 'Deceased', 'Pending' and 'Cancelled'.

Not sure if there is a use case for also re-calculating these but interested in people's thoughts.

Proposed solution: add an option to process normally excluded membership statuses (maybe just expired) from job.process_membership.

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