Subscribe

Author

Peter Koczan

[guest author fields > title]

Originally from Hungary, currently located in Amsterdam. Working in Premier Support at the Atlassian office here, providing support for all of our products including Confluence, JIRA, Crowd, FishEye/Crucible, Bamboo, Stash and HipChat.

Learning as much as possible with the goal of making support- and product experience better for all, since 2012.


Warning: Undefined array key “link” in /srv/users/atlassian/apps/atlassianstaging/public/wp-content/plugins/curator/template-parts/cards/feed-card.php on line 146
Prevention, self-service, and strategic laziness: the recipe for service desk success

Selecting the right tools and software to run your service desk is just part of what makes your customers and engineers successful. Creating a collaborative, self-service environment where people can develop and implement the most effective ways to solve complex challenges – be it from customers or internally – will result in a chamber of innovative teams tackling any issue and adapting to ever-changing business needs.


Warning: Undefined array key “link” in /srv/users/atlassian/apps/atlassianstaging/public/wp-content/plugins/curator/template-parts/cards/feed-card.php on line 146
What Atlassian application administrators need to know about the “leap second” bug lurking in your systems

A leap second is a one-second adjustment that is occasionally applied to UTC (Coordinated Universal Time) in order to keep its time of day close to the mean solar time. The most recent leap second insertion happened on June 30, 2012 at 23:59:60 and caused disruptions in computing systems all around the world.