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 926
    • Issues 926
    • 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
  • #317

Closed
Open
Opened Aug 10, 2018 by sarah.farrellgraham@sarah.farrellgraham

Fixed membership type - start date incorrect

I have found an issue in (CiviCRM 4.6.38 and the dmaster 5.6.alpha) when a membership type is 'Fixed' the start date is incorrectly populated.

For example- Your membership runs from 1st September 2018 to 31st August 2019- the fixed period start date is the 1st of September, the fixed period roll over date is 1st August- If I added a new membership today I would expect the start date to be 1st September 2018 (and finish on 31st August 2019) with join date being today's date- but it is setting the start date as 1st September 2017.

The end date of the membership is still being populated correctly as 31st August 2019 (for a 1 year membership).

thanks, Sarah

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#317