Edit Excel attachments in Jira — without downloading, with the macros kept.
A spreadsheet attached to an issue is where the work actually is: the estimate, the plan, the register. Jira stores it and previews it — it cannot open it. Our app can: the attachment opens inside the issue, in the browser, and Ctrl+S puts it back on the same issue. The VBA project of an .xlsm workbook travels through that round byte for byte. The same app does it for the attachments of a Confluence page, where a save becomes a new version of that same attachment.
What was measured
| The round | Jira Cloud and Confluence Cloud, 26 September 2026. A macro workbook (three sheets, a Power Query table, a VBA macro) and a Word document with five pictures: attached, opened from the issue and from the page, edited, saved back. |
|---|---|
| The macros | vbaProject.bin came back byte for byte — the SHA-256 of that part is unchanged — with 22 parts of 22 present and the hidden name that binds the Power Query table intact. |
| The pictures | All five byte for byte, 16 parts of 16. |
| Microsoft Excel | What we checked on this host is in the rows above: the package and the VBA project come back byte for byte. That a real Excel then opens an edited workbook without a word is measured on our Nextcloud stand, on the Enron corpus (20.09.2026). |
| Where the save lands | Confluence: a new version of the same attachment. Jira: Jira Cloud keeps no attachment versions at all, so the app attaches the edited file under the same name and removes the one it replaces — the issue keeps one file, not a pile of copies. |
Without downloading
No desktop Office, no Atlassian Companion, no copy in the Downloads folder that someone forgets to attach back. Companion opens the file with whatever application sits on that computer — which is exactly where a macro-enabled workbook starts losing its macro project, or refuses to open under a policy that blocks macros from the internet.
Where the file goes
| The path | Jira or Confluence → the SumOffice service → the SumOffice editors. The file is never written to disk in between: it is read and handed on, and written back the same way. |
|---|---|
| Your rights | Every read and every write happens with the rights of the person who opened the file. The app holds no rights of its own in your site. |
| Your tokens | The Atlassian token never reaches the browser. Every call from the app is signed by Atlassian and checked; the editor talks to the service over signed access tokens with verified proof keys. |
| Setup | None. No server address, no key: install the app and open an issue. |
Where it appears
In a Jira issue: the ••• menu at the top — Edit Office attachments — SumOffice — and a panel on the right, Office attachments, that lists the .xlsx, .xlsm, .xlsb, .docx and .pptx attachments of that issue. Press Edit next to a file; Ctrl+S saves it back. In Confluence: the ••• menu of the page (Confluence guide). Nothing has to be added or configured first.
Getting it
Install it from the Atlassian Marketplace: in Jira, Apps → Explore more apps, search for SumOffice and press Get it now. A site administrator approves the permissions once; after that every user sees the item in the ••• menu of an issue. Nothing else to set up: Apps → Manage apps → Excel, Word & PowerPoint — SumOffice → Configure only shows that the service and the editors are reachable.
Confluence has its own app — see SumOffice for Confluence. How the apps handle data: privacy policy. Problems: support. The other systems we measured →
- Check my Excel file — what your workbooks rely on.
- Cloud or Data Center? — tell us which; this page is Cloud.