Edit Issues in Excel for Jira
Security
Last updated:
Edit Issues in Excel for Jira is provided by druidori s.r.o. This page describes the app's data flow, access permissions, update safeguards, and how to report a security concern.
Access to Jira
The app works through Atlassian's Forge platform with the signed-in user's Jira permissions. It can only export issues the user can browse and only change fields the user can edit. Uploading a workbook never grants extra access: Jira checks every change against the permissions of the person applying it, whoever exported the file.
The app requests read:jira-work to read issues and field settings, write:jira-work to update the fields you confirm, and read:jira-user to match names typed in user columns. It does not create, delete, or transition issues, and it never asks for your Atlassian password or API token.
Where issue data goes
Workbooks, the review, and result reports are created in the user's browser. The app has no vendor backend, app data store, or connection to an external service. It does not send issue data or workbooks to druidori, collect usage analytics, or write issue data to application logs.
Atlassian hosts the app interface and handles the Jira requests. A downloaded workbook is an ordinary file: it holds the exported values and a hidden snapshot sheet with the original values, issue IDs and the account IDs of people in user fields. Treat it like any other export of Jira data. Your device, spreadsheet application, and any file-sync or sharing service you use determine who can access it.
Update safeguards
- Nothing changes in Jira until the user reviews every change and chooses Apply.
- Each cell is compared with the export snapshot and with the current value in Jira. A value someone changed in Jira after the export is shown as a conflict and is skipped unless the user explicitly chooses to overwrite it.
- Only changed cells are sent. Columns that are read-only for the user, unsupported field types, and descriptions with rich formatting stay locked and are ignored if edited.
- Rows for issues that were not part of the export, duplicate rows, and new rows are reported and skipped. Deleting a row never deletes an issue.
- Changes appear in each issue's history under the user's name. A result report records what was applied and what failed.
- Exported text is stored as literal strings, so values that look like formulas are not evaluated.
Report a security concern
Email info@druidori.com with the subject Edit Issues in Excel security report. Describe the suspected issue, its impact, the steps to reproduce it, and your browser and app version if known. Use a small synthetic example where possible.
Do not send passwords, API tokens, or real Jira exports. Start with a description if the evidence contains personal or sensitive information. Test only content and systems you are authorised to access.
Security reports are reviewed for impact and reproducibility. Confirmed app vulnerabilities are handled under the applicable Atlassian security bug-fix policy. Ordinary support availability does not replace applicable security or incident-notification duties.
Support and privacy
Information you choose to send by email is separate from normal use of the app. The privacy notice explains how support correspondence and other business information are handled. See support for ordinary questions.