Frequently Asked Questions

How to Use Just Blame

  1. Install the App

    Install Just Blame from the Atlassian Marketplace. No configuration required—it works immediately after installation.

  2. Open Any Confluence Page / Jira Issue

    Navigate to any Confluence page / Jira Issue you want to analyze. Just Blame works with all existing pages and respects your permission settings.

  3. Activate Blame View

    Click the "Blame" button in the Confluence actions toolbar(...) under Apps section. The page will display with color-coded sections showing authorship.

  4. Explore Authorship Details

    Click any section to see who wrote it and when.

  5. Toggle Views

    Switch between "block" and "inline" views, or turn off blame view to return to normal page display.

General Questions

What does Just Blame do?

Just Blame adds inline author attribution to Confluence pages or Jira Issue. It shows you who wrote each section of a page without having to click through version history. Like "git blame" for developers, but for your Confluence wiki and issues.

How does Just Blame work?

Just Blame analyzes history and displays color-coded sections showing who created each paragraph, table, heading, or section. Each author gets a unique color, making it easy to see contributions at a glance.

Do I need to configure anything?

No. Just Blame works immediately after installation. There's no setup, no API keys, and no configuration required. Just install and start using it.

Does it work with existing pages?

Yes! Just Blame works with all your existing Confluence pages. It uses the built-in page history, so it can show authorship for pages created before you installed the app.

What does "block" vs "inline" view mean?

Block view shows the version history sidebar with a list of all contributors and timestamps. Inline view displays the authorship information directly within the content flow. You can toggle between both views.

Features & Functionality

Can I see who wrote a specific paragraph?

Yes! Click any paragraph, table, heading, or section to see the author name and timestamp.

Does it show edit history or just the original author?

Just Blame shows the original author of each section by default.

How far back does the history go?

Just Blame uses Confluence's native version history, so it goes back as far as your page history exists. There's no limit on how old the content can be.

Privacy & Security

Does Just Blame respect Confluence permissions?

Yes. Users only see authorship information for pages they already have access to. Just Blame respects all Confluence security settings and permissions.

Is any data sent outside of Confluence?

No. All processing happens within your Confluence instance using standard Atlassian APIs. No data is transmitted to external servers.

Can I hide authorship information from certain users?

Authorship visibility follows Confluence page permissions. If a user can view a page, they can see its authorship information. This ensures transparency and accountability.

Does it track anonymous edits?

Just Blame displays whatever user information is recorded in Confluence's version history. If edits were made anonymously or by deleted users, this will be indicated.

Performance & Compatibility

Does it slow down my pages?

No. Just Blame is lightweight and only processes data when you activate it. Your normal Confluence browsing experience is unaffected.

Will it work on large pages with lots of history?

Yes. Just Blame is optimized to handle pages with extensive edit history. Loading times may vary based on page complexity, but performance remains smooth.

Is it available for Confluence Data Center?

Currently, Just Blame is available for Confluence Cloud. Data Center support is on our roadmap. Contact us if you're interested in Data Center availability.

Does it work on mobile devices?

Just Blame is optimized for desktop use where detailed version history is most useful. Mobile support is limited but functional for basic viewing.

Use Cases & Best Practices

How do compliance teams use Just Blame?

Compliance teams use Just Blame to quickly audit who created or modified sensitive documentation.

How does it help with onboarding?

New team members can use Just Blame to identify subject matter experts. Instead of asking "who knows about this?", they can see immediately who wrote each section and reach out directly.

Can I use it for content reviews?

Yes! Content reviewers use Just Blame to understand who wrote what before making editorial changes. This helps maintain consistency with the original author's intent and makes it easier to discuss changes.

How do documentation teams benefit?

Documentation teams use Just Blame to maintain clear ownership of content sections. When updates are needed, they know exactly who to consult without searching through history or asking the whole team.

Last updated: November 2025