Versions Compared

Version Old Version 37 New Version 38
Changes made by

spg bot

spg bot

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

With Agile Cards you can move backlog ordering sessions to the next level by using physical issue cards to prioritize your JIRA backlog. 

...

Either upload a photo or scan displayed QR code using your mobile device to go to the mobile view.

Info

Uploaded photo is analyzed by your browser. This is a time and memory consuming task so if you are using a mobile device for scanning, a strong device with modern browser is needed for this feature to work.
Currently supported mobile browsers are Chrome for Android and Safari for iPhone in their newest versions.

...

 

 is built with safety and security in mind. Here are a few facts which will help you understand its architecture and that using Agile Cards should no impact on your security whatsoever.

No impact on data and configuration

Agile Cards make no changes to the data and to the underlying configuration of your JIRA server. Agile Cards connect to the officially exposed APIs and plugin points available within JIRA, but operate in read-only mode. 

Analytics

Agile Cards come with in-built analytics. The data collected by Agile Cards is anonymous and pertains only to the statistical usage of the add-on. It helps the team at Spartez optimise the solution and implement even better future versions. 

If you do not wish to have the anonymous usage data collected from your instance, you can disable the analytics. Agile Cards depends on the global JIRA setting for analytics collection.

Data read and stored by Agile Cards

Agile Cards stores only the data related to the templates configured for its usage. This data contains all the elements of the Agile Cards configuration:

  • names of the templates
  • templates' layouts
  • page layouts
  • colours of printed bars
  • and other settings configurable through the Agile Cards interface

All the data pertaining to the content of the actual issues are read by JavaScript code launched within your browser window. None of the elements of this data is saved nor processed outside of your browser windows and JIRA. That means that the team at Spartez has no physical means of seeing and accessing your data (even if you asked us to do so during the support call). This pertains to both the backlog, boards, search queries, issues as well as all the attachments stored in JIRA.

Where is the data stored?

If you are using JIRA Server (on-premises) all the configuration data of Agile Cards is stored on JIRA and never leaves them.

If you are using JIRA Cloud (on-demand) then the configuration of Agile Cards is stored securely on Spartez server and is provided to the add-on per request.

The code of Agile Cards is downloaded from Atlassian Marketplace directly to JIRA and is never served from any third party servers. This means that all the fundamental safety mechanisms applied by Atlassian to your JIRA code and data are also applied to Agile Cards code and data.

How does the scanner process the photo?

Agile Cards scanner is written in JavaScript. This means that the photo is processed entirely within the browser, and no part of the photo is sent outside of the device you have used to access the Agile Cards. In particular no part of the photo is processed on your JIRA server and no data about the content of the photo is sent over to Spartez server.

All of these informations are part of our End-User License Agreement which you can see on the Atlassian Marketplace listing for Agile Cards.