-
Bug
-
Resolution: Obsolete
-
High
-
Replicated in OnDemand Fireball 221, Team Calendars Plugin Version: 3.1.4
-
Severity 3 - Minor
-
NOTE: This bug report is for Confluence Cloud. Using Confluence Server? See the corresponding bug report.
When a user move issues on a JIRA calendar those changes are not being replicated to other users in a timely manner.
How to replicate:
- Create a JIRA calendar inside a page in Confluence with user1
- Open that same page with user2
- Move issues on that calendar with user1
- Refresh calendar with user2, no changes can be seen.
- Add (or remove) due date to an issue in JIRA, that change does not get replicated to the calendar.
If you move issues with user2, user1 wont see those changes promptly as well, even if on JIRA the due dates are correct. This same behavior applies to issues that had a resolution set and should be grayed out, some users see it, some users don't.
Also, when setting Due Date on an issue that issue doesn't show up on the users calendar as well, but if a new calendar is created the same shows up.
This can lead to serious problems as users can edit calendars at the same time and completely lost track of what is actually happening to the due dates of their JIRA issues.
- is blocked by
-
CONFCLOUD-51292 Eliminate lag time between setting date in JIRA field and seeing changes reflected on JIRA/Team calendar
- Gathering Interest
- is related to
-
CONFSERVER-49684 JIRA Team calendars are not synchronizing properly.
- Closed