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 984
    • Issues 984
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • Core
  • Issues
  • #1226

Closed
Open
Opened Aug 30, 2019 by Pradeep Nayak@pradeepDeveloper

Smart groups: Relative date filters saved incorrectly

(Original title: "Regression: Smart group with Change log criteria is not saved.")

If you create a smart group which uses a relative date filter (e.g. "Last 60 days" or "This calendar current year"), the relative date filter is not saved correctly.

This issue entails two aspects:

  1. (Code update in 5.16.4) Fix the code so that smart groups are properly saved
  2. (Data cleanup; case-by-case) Identify any smart-groups which were created or edited in the past month (5.16.x). Determine if they should be updated to use a relative date filter.

The following fields are believed to affected:

  • log_date_relative
  • pledge_payment_date_relative
  • pledge_start_date_relative
  • pledge_end_date_relative
  • pledge_create_date_relative
  • member_join_date_relative
  • member_start_date_relative
  • member_end_date_relative
  • birth_date_relative
  • deceased_date_relative
  • mailing_date_relative
  • relation_date_relative
  • relation_start_date_relative
  • relation_end_date_relative
  • relation_action_date_relative
  • contribution_recur_start_date_relative
  • contribution_recur_next_sched_contribution_date_relative
  • contribution_recur_cancel_date_relative
  • contribution_recur_end_date_relative
  • contribution_recur_create_date_relative
  • contribution_recur_modified_date_relative
  • contribution_recur_failure_retry_date_relative
Edited Sep 03, 2019 by totten
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
5.17.0
Milestone
5.17.0 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1226