App: Organization Notes for Jira Atlassian Forge Cloud

Shared Customer Context, Right on Your Tickets.

Centralize organization-wide knowledge. Embed persistent, markdown-powered notes directly into the Jira issue sidebar. When you write a note on one ticket, it automatically syncs across all tickets belonging to that organization.

📝 Organization Notes
Synced
Acme Corp TechCorp
# VIP SLA & Architecture Saved

• Primary Contact: alice@acme.com
• Staging: https://staging.acme.internal

Dedicated Slack channel active
Q3 Infrastructure audit pending
Last saved: 2m ago by Admin Ctrl+S
01 • Overview

What is Organization Notes?

In Jira and Jira Service Management (JSM), customers open multiple tickets over time. Usually, vital account context, contact preferences, and technical caveats get lost in closed tickets or external wikis.

🏢

Organization-Scoped Notes

Notes belong to the Organization, not the individual ticket. Edit a note once on Ticket A, and agents handling Ticket B or Ticket C for that same organization instantly see the exact same note.

✍️

Rich Markdown Support

Full GitHub Flavored Markdown (GFM). Add headings, interactive checklists, code blocks, tables, bold text, blockquotes, and links with a dedicated formatting toolbar.

📌

Right Sidebar Integration

Seamlessly embedded into Jira's right-side issue context sidebar. Agents don't have to leave the ticket or open another browser tab to view critical client context.

🔒

Role-Based Access Control

Control who can View and who can Edit notes based on Jira Project Roles and User Groups. Non-editors get a clean read-only interface.

⚙️

Admin Hub & Pre-Creation

Manage all notes globally via Jira Settings. Create notes for new clients in advance before any tickets are even opened, search notes, and audit timestamps.

🛡️

100% Forge-Hosted Cloud

No developer servers. All note storage and serverless computation execute exclusively inside Atlassian's secure cloud infrastructure.

02 • Architecture

How Does It Work?

Organization Notes utilizes native Atlassian Forge extension points and key-value cloud storage.

Step 1

Ticket Opened

An agent opens any Jira or JSM ticket. The app checks for linked organizations (JSM Customer Organization or custom fields).

Step 2

Storage Query

The Forge resolver securely retrieves the shared note from native Atlassian storage using the organization ID as key.

Step 3

RBAC Evaluation

The app verifies the active user's Jira Project Roles and User Groups against admin settings to display edit or read-only controls.

Step 4

Real-Time Sync

When saved, the note updates instantly for all team members across every ticket associated with that client.

🔒

Zero Third-Party Egress: No customer data, note contents, or Jira metadata is ever sent to or processed by developer-owned servers. All data stays strictly in Atlassian Forge Hosted Storage.

03 • Step-by-Step Guide

How to Use Organization Notes

Everything you need to know about creating notes, formatting markdown, managing organizations, and configuring access control.

1

Viewing & Writing Notes on Tickets

1. Open any ticket in Jira or Jira Service Management that has an Organization assigned (e.g. Acme Corp).
2. Look at the right-side details context panel. You will see the Organization Notes panel.
3. Click the text area to start typing. Use the toolbar buttons for instant markdown formatting.

Quick Shortcut: Press Ctrl + S (or Cmd + S on macOS) to save instantly.

One-Click Copy: Click the clipboard icon to copy the entire note content to your clipboard.

2

Handling Multi-Organization Tickets

If a ticket involves multiple organizations, the app automatically generates tabs at the top of the note panel. Click any tab to instantly switch notes without reloading the page.

3

Managing Notes in Jira Settings (Admin Hub)

Jira Administrators can access the central management console by navigating to:
Jira Settings (Cog icon) > Apps > Organization Notes

  • Pre-create notes: Click "+ Create Organization Note" to author notes for a client before any tickets are submitted.
  • Search & Filter: Find any organization note across your entire Jira instance.
  • Global Edit & Delete: Update or clear notes directly from the administrative overview.
  • Audit Trail: See who last updated a note and when.
4

Configuring Permissions & RBAC

In Jira Settings > Apps > Organization Notes > Permissions Tab:

View Permissions

Select which Jira Project Roles or Groups can see the note box. Users without view permission won't see the panel at all.

Edit Permissions

Specify which roles or groups can edit and save notes. Non-editors get a clean read-only view.

04 • Frequently Asked Questions

FAQ

Does this work on Jira Software and JSM?

Yes! It automatically detects Jira Service Management Customer Organizations as well as custom organization fields in Jira Software or Jira Work Management projects.

Where is my data stored?

100% in Atlassian Forge Hosted Storage within your Atlassian Cloud site boundaries. boot.dk does not operate any external databases.

What happens if a ticket has no organization?

If a ticket does not have an organization assigned, the panel displays a friendly prompt to assign an organization to activate shared notes.

How can I reach support?

You can submit tickets, report bugs, or request features via our official Atlassian Customer Support Portal.

Ready to streamline customer context in Jira?

Install Organization Notes for Jira from the Atlassian Marketplace and start sharing persistent client notes across your team today.