docs: Document Jira service-account identity, write permission, and reply behavior by promptless[bot] · Pull Request #1172 · Promptless/promptless.ai

promptless · 2026-10-19T19:23:03Z

Proposed changes

Promptless/promptless#5524 changes how Promptless works in Jira. The Jira and Atlassian pages still describe the earlier behavior, so this updates them:

Account identity: With a service account attached, Promptless does all Jira work as that account: research, comments, remote links, and issue creation. If the service account fails, Promptless does not fall back to the connecting person. Without a service account, Promptless reads Jira as the connecting person, and it writes as that person only when the Knowledge Base or the current request explicitly permits that action. A configured trigger alone does not grant permission.
Replies: Mentions and assignments get an acknowledgement, progress updates, and an answer, and an unanswered ticket is flagged for follow-up. The promptless label and configured Jira triggers comment only with a suggestion result or an actionable blocker, and post nothing on no-change runs.
Issue reporter: The reporter of a created issue is now the service account when one is attached. It was previously always the connecting person.
Updated the Jira trigger page, the Atlassian integration page (including the integration card's new panel labels), the configuration reference, the Jira Automation page, and the Connection health troubleshooting entry. Replaced the do-not-publish label example, because that run would no longer comment on the ticket. Added an October 2026 changelog entry.

Review feedback

Applied @hawkeyexl's suggestion on the Jira Automation page verbatim: the no-service-account bullet now joins the read identity and the attribution of comments and tickets into one sentence.
Applied @hawkeyexl's suggestion on the Jira trigger page verbatim: the permission fallback sentence now says "Without permission for these extra actions" and "skips writing to Jira". Behavior is unchanged.

Checklist

Instructions and examples match the current product behavior.
Links and image references are valid.
Changed pages render correctly.

Merged current main (manni 4.12.2, #1176) and restamped last-updated on the five changed pages for the manni frontmatter check (#1165). npx manni meta validate (manni 4.12.2) passes with 0 errors.

…ehavior

vercel · 2026-10-19T19:23:11Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
promptless-docs	Ready	Preview	Oct 19, 2026 9:13pm UTC

promptless · 2026-10-19T20:57:09Z

I noticed that some CI checks failed for this PR. I'm investigating whether the failures are caused by this suggestion. If they're unrelated or pre-existing, I'll leave this suggestion unchanged and create a separate suggestion if a standalone docs fix is needed.

…-identity-5524

…vior into the restructured Atlassian and Jira pages

…type, and embed integration procedures as partials (#1177) * Lint docs page structure by type with manni lint, and fix five pages * Restamp last-updated on the five edited pages * Restructure and edit the next five worst-failing pages for manni lint structure * Restamp last-updated on the next five edited pages * Restructure five trigger and integration pages as how-to guides Retype github-commits, github-prs, gitlab-merge-requests, slack-messages, and reference/integrations/gitlab as type: how-to, and restructure each to the TGDP how-to template: Overview, Before you start, task sections, and See also. Update inbound links to the renamed section anchors. * Restamp last-updated on pages with updated anchor links * style: remark-lint auto-fix * Embed integration connection procedures as MDX partials Move each integration's connection procedure into src/partials/integrations/ and embed it in the trigger, context-source, and doc-location pages that need it, and in the integration page itself. Remove the Reference > Integrations group from the sidebar; the pages stay published and searchable. Inline partials in the .md endpoint and the MCP index so agent-readable output keeps the procedures. Record the decision in ADR 0007. * Restamp last-updated on pages that embed integration partials * Update ADR 0006 structure-lint counts * Retype pages outside the reference sections from reference to how-to or concept * Remove the Linear Google sign-in screenshot that shows an employee email * Restamp linear.mdx last-updated after merging main * Restore linear.mdx last-updated to 2026-10-19 to match manni's history * Upgrade manni to 4.13.0 and point authors to lint templates show * Restructure the next five pages for manni lint structure: configuration reference, observability, manual Helm reference, account management, connection health * Restamp last-updated on the five restructured pages * Update the structure-lint backlog count in ADR 0006 * docs: Restructure and clarity-edit the remaining 117 docs pages for manni structure lint, and re-assess each page type Every docs page now passes npx manni lint structure (132/132). Types re-assessed against each page's intent, IA placement, and personas/journeys: the eight hidden Reference > Integrations pages move to how-to, reference/integrations moves to reference, source-control and starport/agent-ready move to concept, and plan-your-deployment moves to how-to. Fixes stale facts found while checking edits against the product source. * docs: Restamp last-updated on the restructured pages * docs: Record in ADR 0006 that every page passes the structure lint * style: remark-lint auto-fix * docs: Remove the retired Kubernetes Helm guide, docs-as-code requirement wording, Temporary outage label, and an outdated New Task screenshot * docs: Split a long sentence in the migration guide * docs: Carry #1172's write:jira-work scope wording and Jira reply behavior into the restructured Atlassian and Jira pages * Regenerate the Open Graph image for the docs-as-code page * docs: Drop Bitbucket mentions that this PR reintroduced after #1034 removed Bitbucket from the docs * Show Overview once in On this page when a page opens with an Overview heading * docs: Wrap every reader procedure in <Steps> * docs: Separate Steps items with blank lines and split sentences Vale flags inside Steps * docs: Rename the MCP skill suggestion-triage to triage-suggestions (Promptless/promptless#5530) --------- Co-authored-by: promptless[bot] <promptless[bot]@users.noreply.github.com> Co-authored-by: promptless[bot] <179508745+promptless[bot]@users.noreply.github.com> Co-authored-by: InlinePizza <249805557+InlinePizza@users.noreply.github.com>

Document Jira service-account identity, write permission, and reply b…

7f7bd15

…ehavior

promptless Bot requested review from adit-chandra, frances720, hawkeyexl and mattlink as code owners October 19, 2026 19:23

promptless Bot added the priority:critical label Oct 19, 2026