Editing and Managing Office Attachments with ikuTeam Office for Jira

Editing and Managing Office Attachments with ikuTeam Office for Jira

 

Application

  • Atlassian Platform: Jira

  • Product: ikuTeam Office for Jira

  • Environment: Jira Cloud (questions also referenced Jira Data Center, but solution applies to Jira Cloud)

Problem Statement:
Users want to understand about the ability to edit existing Microsoft Office files (.docx, .xlsx, .doc, .xls) already attached to Jira issues using the "ikuTeam Office for Jira" app. Additional concerns included whether file conversion is required, if files remain compatible with Microsoft Office, how change tracking works, and how to prevent accidental or untraceable overwrites of attachments. The user also asked about setting attachments to "ReadOnly" in bulk and the availability of versioning or audit trails for edited files.

 

Solution

  1. Editing Existing Attachments

    • The ikuTeam Office for Jira app supports direct editing of Microsoft Office file formats (.docx, .xlsx, .doc, .xls) and OpenOffice formats (ODS, OTD) attached to Jira issues.

    • No file conversion is required; edits are saved in the original file format.

    • Files can still be downloaded and edited with Microsoft Office applications.

  2. Change Tracking

    • Change tracking can be activated for any document at any time, similar to Microsoft Word.

    • To enable track changes:

      1. Open the document for editing via ikuTeam Office.

      2. Activate "track changes" for all users.

      3. Save and close the document.

    • The next time the file is opened, it will be in "track change" mode.

  3. Versioning and Audit Trail

    • Jira does not support attachment versioning. When a file is edited, the previous version is overwritten and cannot be restored.

    • Editing actions are auditable via the Jira Work Item history, which records who edited attachments and when.

    • To achieve file versioning and recovery, consider using the ikuTeam Files app, which stores attachments on external cloud services (e.g., SharePoint, OneDrive, Google Drive, Box, Dropbox) and supports versioning.

  4. Preventing Accidental Overwrites and Restricting Edits

    • Jira permissions can be configured to control which users or groups can edit or delete attachments.

    • To restrict editing:

      1. Go to Jira Settings.

      2. Set attachment permissions to define which users/groups can delete (and thus edit) attachments.

      3. Groups without "delete" permissions cannot edit attachments using the ikuTeam Office app.

    • Reference: Atlassian documentation on configuring file attachments: Configure file attachments | Atlassian Support

  5. Setting Attachments to "ReadOnly"

    • There is no bulk operation to set all attachments to "ReadOnly" directly.

    • Use Jira permissions to restrict editing as described above.

  6. Best Practice Recommendation

    • For organizations with strict audit or compliance requirements, use external file storage with versioning (via ikuTeam Files app or similar) to ensure recoverability and traceability of document changes.

If further assistance is needed, users are encouraged to contact support or book a demo for more advanced configuration.