Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • P Postorius
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 127
    • Issues 127
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 20
    • Merge requests 20
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNU MailmanGNU Mailman
  • Postorius
  • Issues
  • #54
Closed
Open
Issue created Aug 24, 2015 by Eric Searcy@emsearcy

Subscriptions prefs incorrectly set when saving

Actual behavior:

On a new list subscription (all preferences unset), when changing the digest mode from Regular to Mime Digests, all settings to the right of the digest mode get all changed to "No" (even though the Delivery status stays unset).

Expected behavior: all settings not being changed stay at their current value, even if this is "unset".

Note, my user and address preferences did have settings set to "Yes", which did not effect the actual behavior described here of everything being set to "No".

Issue #30 (closed) is related; my suggestion there is that we we want to keep unset ("inherit"?) as a valid choice for users and better explain in the UI the precedence order for the different preference tabs. This separate bug assumes retaining "unset" as a feature.

Assignee
Assign to
Time tracking