NikoNiko Calendar 3.0: on Forge, with a team trend row
NikoNiko Calendar
Version 3.0
Version 3.0 of CloudScript.io NikoNiko Calendar is now live on the Atlassian Marketplace. The app first shipped in mid-2020 on Atlassian Connect; version 3 rebuilds it on Atlassian Forge, so entries are now stored in Forge storage inside Atlassian’s infrastructure rather than on a server we operate. The rebuild also carries the first functional changes to the calendar in some years, each of them a response to how teams actually use a niko-niko calendar rather than a new idea about what one is.
Team trend row
A line beneath the grid plots the team’s average entry for each day of the window. Each point is sized by the share of the team that responded that day, so a high average from two people out of nine reads differently from the same average from all nine, and the line breaks on days with no responses rather than interpolating across them. The trend row is on by default and can be switched off in the macro’s configuration.
User can now contribute to multiple calendars
Entries are now isolated to the calendar in which they were recorded. This means that a user can be added to two or more calendars and record a different value on each calendar for the same day. An new optional label above each calendar can be user to specify a topic that the calendar refers to, for example a team can now publish two calendars on the same page, the first asking “How is the merge going?”, and the second asking “How is the sprint in general?” and team members provide a different answer on each calendar. Likewise user working across multiple teams are able to provide different responses in a team calendar for each team.
Deleting entries for better data management
All users can now delete their own entries from the entry picker. They can do this either for a single day on one calendar, or for their entire history across every calendar. Additionally, Confluence site administrators gain a Niko Niko data management screen listing every account for which the app holds entries, with the option to delete all entries for a person or all entries older than a chosen date. The accounts on the data management screen are drawn from the app’s own storage, rather than the site directory, so that administrators are able to delete data for users who have left the organisation or no longer have a Confluence account.
What has not changed
Pages that already contain the macro keep rendering without reconfiguration. The calendar remains sized for a single team, with the same three-or-five-point scale and the same smiley, square and cat themes. Because the app now runs on Forge and requests granular Confluence scopes, administrators will be asked to approve the new version when it replaces the Connect app on their site; the app’s privacy policy describes exactly what is stored.
Read more in our updated User guide.