-
Bug
-
Resolution: Obsolete
-
High
-
None
-
No-Version
-
Replicated in OnDemand Fireball 221, Team Calendars Plugin Version: 3.1.4
-
Severity 3 - Minor
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? 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
-
CONFSERVER-51292 Eliminate lag time between setting date in JIRA field and seeing changes reflected on JIRA calendar
- Gathering Interest
- relates to
-
-
- Closed
-
[CONFSERVER-49684] JIRA Team calendars are not synchronizing properly.
Joseph Boulos
added a comment - I am seeing the same behavior. I created a Release Calendar to report an "real-time" view of all our Production changes per the JIRA schedule. However, the calendar being projected on the TV for all to see is stale. It is showing with a user that is read-only on the calendar (to prevent anyone from walking up and messing around with the calendar).
I see the calendar on my screen with my user and the info is accurate. I look on the TV and the calendar is wrong.
If I manually refresh the calendar as that user it will get the correct information, but that defeats the purpose of a real-time automated release calendar.
Joseph Boulos
added a comment - I am seeing the same behavior. I created a Release Calendar to report an "real-time" view of all our Production changes per the JIRA schedule. However, the calendar being projected on the TV for all to see is stale. It is showing with a user that is read-only on the calendar (to prevent anyone from walking up and messing around with the calendar).
I see the calendar on my screen with my user and the info is accurate. I look on the TV and the calendar is wrong.
If I manually refresh the calendar as that user it will get the correct information, but that defeats the purpose of a real-time automated release calendar. 
Igor Belagorudsky
added a comment - Actually, while the above is certainly a bug, the other issue which is unmentioned is that issues on a calendar that are resolved are not showing up grayed out for other users. I don't believe it has anything to do with lag or caching as a week later and having refreshed both the page and the calendar specifically (through the dropdown arrow next to the calendar name), other users besides the calendar owner (which could be a coincidence) are not seeing resolved cases as grayed out. See case JST-65256 for details.
Igor Belagorudsky
added a comment - Actually, while the above is certainly a bug, the other issue which is unmentioned is that issues on a calendar that are resolved are not showing up grayed out for other users. I don't believe it has anything to do with lag or caching as a week later and having refreshed both the page and the calendar specifically (through the dropdown arrow next to the calendar name), other users besides the calendar owner (which could be a coincidence) are not seeing resolved cases as grayed out. See case JST-65256 for details.
jboulos Jira issues in the calendar should refresh automatically, but it isn't 'real time'. There's a cache that is refreshed periodically (or manually with the refresh button), so you should see changes throughout the day. I'm going to close this issue as there haven't been any recent reports, but feel free to comment if you have more details.