Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S syncevolution
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 168
    • Issues 168
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SyncEvolution
  • syncevolution
  • Issues
  • #88
Closed
Open
Issue created Nov 10, 2014 by Bugzilla Migration User@bugzilla-migration

Activesyncd creates wrong RRULE for nth recurrence

Submitted by Graham Cobb

Assigned to SyncEvolution Community

Link to original bug (#86102)

Description

See also bug #70693

Activesyncd is losing the "nth" attribute for monthly repeating BYDAY events.

The following EAS data:

        <Recurrence xmlns="Calendar:">
          `<Recurrence_Type>`3`</Recurrence_Type>`
          `<Recurrence_Interval>`1`</Recurrence_Interval>`
          `<Recurrence_WeekOfMonth>`1`</Recurrence_WeekOfMonth>`
          `<Recurrence_DayOfWeek>`16`</Recurrence_DayOfWeek>`
        `</Recurrence>`

is turned into the following RRULE:

RRULE:FREQ=MONTHLY;BYDAY=TH

which should be:

RRULE:FREQ=MONTHLY;BYDAY=1TH

This is obviously related to bug #70693. Until I investigate further, I don't know if this is caused by the same underlying problem as that bug, is a deliberate attempt to avoid triggering that bug or is a separate bug. Even if this is separate, bug #70693 may still prevent the corrected event from being synchronised.

As events with recurrence like "first Monday of the month" are very common, it would be nice to fix this.

Depends on

  • Bug 70693
Assignee
Assign to
Time tracking