Do you know what the “cookie directive” is?
The “cookie directive,” also known as Directive 2009/136/EC, defines consent requirements for cookies across the European Union (EU). Specifically, paragraph 26 says:
“Member states shall ensure that the storing of information, or the gaining of access to information already stored, in the terminal equipment of a subscriber or user is only allowed on condition that the subscriber or user concerned has given his or her consent, having been provided with clear and comprehensive information, in accordance with Directive 95/46/EC, inter alia, about the purposes of the processing. This shall not prevent any technical storage or access for the sole purpose of carrying out the transmission of a communication over an electronic communications network, or as strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service.”
In simple language: Before somebody can store or retrieve any information from a computer, the user must give informed consent to do so.
What does this mean in practice?
What does this have to do with Jira?
If you host Jira yourself, and it is publicly available to customers, the Directive applies also to you. The Directive affects the laws of each EU member state differently, but if you don’t want to break the law in your country, you should inform your Jira users about the cookies appropriately – and Angry Cookies helps you do that.
What is Angry Cookies?
How does it work?
When a user accesses your application for the first time, he or she will see a message banner at the top of the page. After reading and accepting the warning about cookies, the message banner will disappear. For anonymous (not-logged-in) users, the message banner may reappear if Jira cookies expire, or the user clears the browser’s cache. For logged-in users, the choice will be remembered, so they only need to accept the cookies policy once.