Closed Bug 932267 Opened 11 years ago Closed 6 years ago

[User Story] Calendar Active Sync Support

Categories

(Firefox OS Graveyard :: Gaia::Calendar, defect)

x86
macOS
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: arogers, Unassigned)

References

Details

(Whiteboard: [ucid:Productivity78, 1.5:p2, ft:productivity])

User Story:

As a user, I want to configure my calendar to work with my EAS account so the calendar on my phone accuratly reflects my appointments.

Acceptance Criteria:

1. The option exists to use exchange active sync when setting up a new calendar on the device
2. Setting up an EAS calendar account results in the correct content being synced to the device at the specific interval. 
3. Any changes on the device calendar will be reflected on the online calendar and vice versa.
Assignee: nobody → gaye
Whiteboard: [ucid: Productivity78] → [ucid:Productivity78, ft:productivity]
Whiteboard: [ucid:Productivity78, ft:productivity] → [ucid:Productivity78, 1.5:p2 ft:productivity]
Whiteboard: [ucid:Productivity78, 1.5:p2 ft:productivity] → [ucid:Productivity78, 1.5:p2, ft:productivity]
Hi I bought a Alcatel Firefox OS phone to use with my work and I need this, do you have any idea when this can be supported? Have a way to I help on this bug?

Thanks a lot
Assignee: gaye → nobody
blocking-b2g: --- → backlog
I believe this is really important feature for any business Firefox OS use.
This problem force me to have 2 phones, 1 android to get my professional mails and calendar and 1 with FFOS for personnal mails... I want to keep only one. And I want to use FFOS for business. 
This feature is really important.
FOR TRACKING PURPOSES-
Another user is requesting this feature in the SUMO forums: https://support.mozilla.org/en-US/questions/1047408

ENVIRONMENT-
Device:  ZTE Open C
Version: ffos_FR_ZTE_OPENCV1.0.0B03
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.