Privacy Policy
Last updated: 21 October 2026. Publisher: Webelisys.
Introduction
Quick Issue Import runs in your browser, inside Jira. It has no server of its own and nothing runs on a server for it. Every request it makes goes from your browser to Jira, in your name and with your own Jira permissions.
The app never uploads your file, keeps no storage of its own, and sends no data to Webelisys or to any third party. Atlassian, which hosts Jira, is not a third party here.
What happens to your file
The Excel or CSV file you choose is read in your browser. The file itself is never sent anywhere, and neither are its name and its size. It does not go to Webelisys, to a third party, or to Jira as an attachment.
What is sent to Jira, and when
The text of your rows does leave your browser when the issues are created, because it becomes the issues. When you click a Create button, the values of the columns you mapped (summary, description, issue type, priority, due date, labels, assignee) are sent to Jira, and to Jira only, to create one issue per row.
Before that, to find the rows already created by an earlier import, the app searches Jira with a fingerprint of each row. These searches carry the fingerprints and never the text of the rows.
Jira applies your own permissions to every request. The app cannot do anything in Jira that you could not do yourself.
What the app reads in Jira
With your account, the app reads the issue types and fields of the project, the labels already used on the site, and the people who can be assigned in the project. For these people it reads the display name, and the email address only when Jira shows it to you, so that the Assignee column can be matched. It also reads the issues created by an earlier import, through their hidden mark, and the Use Quick Issue Import permission. To find the issues of an earlier import, it reads the account identifier of the person who created them and uses it in a Jira search. It also reads your own Jira time zone, so that the dates in its searches match Jira's. The app keeps none of this.
The hidden mark on each issue
Each issue created by the app carries a hidden mark, stored as an issue property named qii. It lets the app recognise the rows already imported, so that importing the same file again into the same project does not create them twice.
The mark holds the project key, a fingerprint of the row with a sequence number, a random identifier of the import, and a flag that marks the last batch. The fingerprint is a shortened SHA-256 hash, and the text of the row cannot be read back from it. The mark contains no name, no email address and no text from your rows.
Atlassian stores the mark with the issue. It stays as long as the issue exists, and it is not removed when the app is uninstalled, because it belongs to the issue. It disappears when the issue is deleted, and it can also be removed with the issue properties API of Jira.
What the app keeps
Nothing. Apart from the issues and their hidden mark, the app writes nothing anywhere. It uses no storage in your browser and no app storage at Atlassian. When some rows are not created, the app offers a CSV file of the rows to fix. That file is built in your browser and saved by your browser, and it never goes through a server.
Permissions
The app requests three permissions. The first lets it read Jira data such as fields, issue types and the marks of earlier imports. The second lets it create issues and their mark. The third lets it read user profiles, only to match the Assignee column with the people who can be assigned.
No tracking
The app sets no cookies, uses no analytics, and contains no tracking of any kind. Webelisys receives no information about which files you import, which issues you create or how often you use the app. Atlassian, as the platform operator and as the seller, handles billing and its own operational data according to its own privacy policy.
Contact
Questions about this policy can be sent to contact@webelisys.fr.
Messages sent with the form on our support page go through Web3Forms, a form service, to reach the Webelisys mailbox. They are used only to answer you. Web3Forms keeps a copy for a limited time, then deletes it automatically.
How the app is secured, and how to report a security problem, is described in our security policy.