/
Security information for Usage Statistics for Jira

Security information for Usage Statistics for Jira

Here you find information on how this app works with data.

How is the data collected?

  • The usage statistics app will run whenever an issue is loaded and is basically a static HTML page. 

  • The App itself is delivered by a web server that just provides static HTML, CSS and JavaScript.

  • The web server holds no session information.

What data is collected?

  • Every successful app load (the small usage statistic panel in the issue) will load the already stored data from your Jira.

    • We store the app data as Entity Properties.

    • This data is only stored in your Jira.

  • The data structure is a JSON and looks like this:

{"views": 0,{"views": 0, "year": year, "month": month, "day": day, "hour": hour, "views-y": 0, "views-yh": [0,0,0,0], "views-m": 0, "views-mh": [0,0,0,0,0,0,0,0,0,0,0], "views-d": 0,  "views-dh": [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],  "views-h": 0, "views-hh": [0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0] }

  • So we track the number of page/issue views and increase a counter in the data structure.

    • There are basic counters for the year, day, hour and so on. 

    • And there are historical counter arrays needed to provide a historical view of the counts (past month or years).

    • The important fact is that no user data is stored.

How is this data protected if collected and stored?

  • The data is stored as Jira entity property.

  • Jira entity properties are readable/writable by every logged-in user.

  • The data is loaded and stored via REST on your Jira system.

    • It is triggered in the current user's browser.

Because the app executes entirely in the browser, you can inspect the delivered HTML, CSS, and JavaScript using your browser’s developer tools (F12). The app is rendered in an iframe and its resources are visible there. These resources are delivered as readable source files and are not minified or obfuscated.