Skip to content

docs(#9004): ADR 0157, require a jira authorization entry for jira-poll - #9026

Merged
jwm4 merged 7 commits into
mainfrom
adr-jira-entry-required
Nov 12, 2026
Merged

jwm4 merged 7 commits into
mainfrom
adr-jira-entry-required

Conversation

@jwm4

@jwm4 jwm4 commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Until recently, Fullsend had exactly one way to decide who may use the Jira poller to run agents: the actor's Jira project role, read from a roster that only project administrators can see, and matched by role name. #8892 (ADR 0153) added better alternatives, config-owned lists of Jira groups and accounts and Jira's own Edit Issues permission for labels, but to stay non-breaking it left the old way as the default. So Fullsend now has a bad default, and a silent one: a repository cannot tell "I chose project roles" from "I configured nothing". This ADR deprecates and removes that default. It does not put a different default in its place: a repository that runs the poller must say which way it uses, and the old way stays available as an explicit two-line choice.

Summary

ADR 0157 records the decision proposed in #9004: running the jira-poll input driver with no jira entry under authorization: is deprecated, and a later release requires the entry. The two-line entry (provider: jira with labels: project_roles) keeps today's project-role behaviour exactly.

No implementation is in this PR; #9005 and #9006 carry it.

Opened as a draft so the proposal can be discussed before anything is treated as decided. Objections and alternatives are welcome here or on #9004.

Closes #9004

🤖 Generated with Claude Code

Record the decision proposed in #9004: running the jira-poll input
driver with no jira entry under authorization: is deprecated, and a
later release requires the entry. The two-line entry (provider: jira,
labels: project_roles) keeps today's project-role behaviour. The
warning is logged by the poller, not reported by fullsend lint, because
lint cannot tell whether a repository polls Jira. Rollout tracked in
#9005 (warning) and #9006 (removal).

Annotate ADR 0153 (its opt-in rule is superseded; lists, labels rules
and roster loading stand) and update the Jira poll bullet in
docs/architecture.md.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Bill Murdock <bmurdock@redhat.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 6:05 PM UTC · Completed 6:16 PM UTC

Commit: ce17c86 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.68

@github-actions

github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Site preview

Preview: https://b3fea1a6-site.fullsend-ai.workers.dev

Commit: 8f3739e219b5a4c9a04601b4de0c596987756ce0

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Nov 2, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Risk Assessment: moderate (2/5)

Details

Documentation-only ADR change with medium blast radius and zero protected paths, elevated to moderate by high commit churn and multi-author contention on docs/architecture.md.

Previous run

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Documentation-only PR introducing ADR 0157 with well-aligned linked issue scope, scored moderate due to high commit frequency and author contention on architecture.md.

Previous run (2)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Documentation-only PR introducing ADR 0157 with well-aligned linked issue scope, scored moderate due to high commit frequency and author contention on architecture.md.

Previous run (3)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Documentation-only PR introducing ADR 0156 with well-aligned linked issue scope, scored moderate due to high commit frequency and author contention on architecture.md.

Previous run (4)

<!-- fullsend:risk-assessment -->
Risk Assessment: moderate (2/5)

Details

Documentation-only PR introducing ADR 0156 and cross-referencing ADR 0153 with low blast radius, well-aligned linked issue scope, and additive documentation changes, despite historical churn on architecture.md.

@fullsend-ai-review

fullsend-ai-review Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Looks good to me

Previous run

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOlt7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl8xNjRhMjYwZWQxNDNhNDA5IiwibGluZSI6NzgsImFjdGlvbmFibGUiOnRydWUsImRpbWVuc2lvbiI6InN0eWxlLWNvbnZlbnRpb25zIn0seyJzZXZlcml0eSI6ImxvdyIsImNhdGVnb3J5IjoiZG9jLXN0eWxlIiwiZmlsZSI6ImRvY3MvQURScy8wMTU2LXJlcXVpcmUtamlyYS1hdXRob3JpemF0aW9uLWVudHJ5LWZvci1qaXJhLXBvbGwubWQiLCJpZCI6ImZfMjNlZjYzYTZmMjg0YWU2OSIsImxpbmUiOjEyMiwiYWN0aW9uYWJsZSI6dHJ1ZSwiZGltZW5zaW9uIjoic3R5bGUtY29udmVudGlvbnMifSx7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl9kZTk1NWIxOTJhMmZmMzVmIiwibGluZSI6MTMxLCJhY3Rpb25hYmxlIjp0cnVlLCJkaW1lbnNpb24iOiJzdHlsZS1jb252ZW50aW9ucyJ9XSwiZGlzcG9zaXRpb25zIjpbeyJpZCI6ImZfMTY0YTI2MGVkMTQzYTQwOSIsInN0YXR1cyI6InJlc29sdmVkX2J5X2NoYW5nZSJ9LHsiaWQiOiJmXzIzZWY2M2E2ZjI4NGFlNjkiLCJzdGF0dXMiOiJyZXNvbHZlZF9ieV9jaGFuZ2UifSx7ImlkIjoiZl9kZTk1NWIxOTJhMmZmMzVmIiwic3RhdHVzIjoicmVzb2x2ZWRfYnlfY2hhbmdlIn1dfQ== -->

Looks good to me

Previous run (2)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOlt7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl8xNjRhMjYwZWQxNDNhNDA5IiwibGluZSI6NzgsImFjdGlvbmFibGUiOnRydWUsImRpbWVuc2lvbiI6InN0eWxlLWNvbnZlbnRpb25zIn0seyJzZXZlcml0eSI6ImxvdyIsImNhdGVnb3J5IjoiZG9jLXN0eWxlIiwiZmlsZSI6ImRvY3MvQURScy8wMTU2LXJlcXVpcmUtamlyYS1hdXRob3JpemF0aW9uLWVudHJ5LWZvci1qaXJhLXBvbGwubWQiLCJpZCI6ImZfMjNlZjYzYTZmMjg0YWU2OSIsImxpbmUiOjEyMiwiYWN0aW9uYWJsZSI6dHJ1ZSwiZGltZW5zaW9uIjoic3R5bGUtY29udmVudGlvbnMifSx7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl9kZTk1NWIxOTJhMmZmMzVmIiwibGluZSI6MTMxLCJhY3Rpb25hYmxlIjp0cnVlLCJkaW1lbnNpb24iOiJzdHlsZS1jb252ZW50aW9ucyJ9XSwiZGlzcG9zaXRpb25zIjpbeyJpZCI6ImZfMTY0YTI2MGVkMTQzYTQwOSIsInN0YXR1cyI6InJlc29sdmVkX2J5X2NoYW5nZSJ9LHsiaWQiOiJmXzIzZWY2M2E2ZjI4NGFlNjkiLCJzdGF0dXMiOiJyZXNvbHZlZF9ieV9jaGFuZ2UifSx7ImlkIjoiZl9kZTk1NWIxOTJhMmZmMzVmIiwic3RhdHVzIjoicmVzb2x2ZWRfYnlfY2hhbmdlIn1dfQ== -->

Looks good to me

Previous run (3)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJhcHByb3ZlIiwiZmluZGluZ3MiOlt7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl8xNjRhMjYwZWQxNDNhNDA5IiwibGluZSI6NzgsImFjdGlvbmFibGUiOnRydWUsImRpbWVuc2lvbiI6InN0eWxlLWNvbnZlbnRpb25zIn0seyJzZXZlcml0eSI6ImxvdyIsImNhdGVnb3J5IjoiZG9jLXN0eWxlIiwiZmlsZSI6ImRvY3MvQURScy8wMTU2LXJlcXVpcmUtamlyYS1hdXRob3JpemF0aW9uLWVudHJ5LWZvci1qaXJhLXBvbGwubWQiLCJpZCI6ImZfMjNlZjYzYTZmMjg0YWU2OSIsImxpbmUiOjEyMiwiYWN0aW9uYWJsZSI6dHJ1ZSwiZGltZW5zaW9uIjoic3R5bGUtY29udmVudGlvbnMifSx7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl9kZTk1NWIxOTJhMmZmMzVmIiwibGluZSI6MTMxLCJhY3Rpb25hYmxlIjp0cnVlLCJkaW1lbnNpb24iOiJzdHlsZS1jb252ZW50aW9ucyJ9XSwiZGlzcG9zaXRpb25zIjpbeyJpZCI6ImZfMTY0YTI2MGVkMTQzYTQwOSIsInN0YXR1cyI6InJlc29sdmVkX2J5X2NoYW5nZSJ9LHsiaWQiOiJmXzIzZWY2M2E2ZjI4NGFlNjkiLCJzdGF0dXMiOiJyZXNvbHZlZF9ieV9jaGFuZ2UifSx7ImlkIjoiZl9kZTk1NWIxOTJhMmZmMzVmIiwic3RhdHVzIjoicmVzb2x2ZWRfYnlfY2hhbmdlIn1dfQ== -->

Looks good to me

Earlier findings

  • docs/ADRs/0156-require-jira-authorization-entry-for-jira-poll.md (lines 78, 122, 131), doc-style, resolved_by_change: the three long lines carrying inline ADR 0153 links were rewrapped in the latest push (now lines 77-79, 122-125, 133-137), each under about 80 columns.
Previous run (4)

<!-- fullsend:review-findings-v2:eyJ2ZXJzaW9uIjoyLCJhY3Rpb24iOiJyZXF1ZXN0LWNoYW5nZXMiLCJmaW5kaW5ncyI6W3sic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6ImRvYy1zdHlsZSIsImZpbGUiOiJkb2NzL0FEUnMvMDE1Ni1yZXF1aXJlLWppcmEtYXV0aG9yaXphdGlvbi1lbnRyeS1mb3ItamlyYS1wb2xsLm1kIiwiaWQiOiJmXzE2NGEyNjBlZDE0M2E0MDkiLCJsaW5lIjo3OCwiYWN0aW9uYWJsZSI6dHJ1ZSwiZGltZW5zaW9uIjoic3R5bGUtY29udmVudGlvbnMifSx7InNldmVyaXR5IjoibG93IiwiY2F0ZWdvcnkiOiJkb2Mtc3R5bGUiLCJmaWxlIjoiZG9jcy9BRFJzLzAxNTYtcmVxdWlyZS1qaXJhLWF1dGhvcml6YXRpb24tZW50cnktZm9yLWppcmEtcG9sbC5tZCIsImlkIjoiZl8yM2VmNjNhNmYyODRhZTY5IiwibGluZSI6MTIyLCJhY3Rpb25hYmxlIjp0cnVlLCJkaW1lbnNpb24iOiJzdHlsZS1jb252ZW50aW9ucyJ9LHsic2V2ZXJpdHkiOiJsb3ciLCJjYXRlZ29yeSI6ImRvYy1zdHlsZSIsImZpbGUiOiJkb2NzL0FEUnMvMDE1Ni1yZXF1aXJlLWppcmEtYXV0aG9yaXphdGlvbi1lbnRyeS1mb3ItamlyYS1wb2xsLm1kIiwiaWQiOiJmX2RlOTU1YjE5MmEyZmYzNWYiLCJsaW5lIjoxMzEsImFjdGlvbmFibGUiOnRydWUsImRpbWVuc2lvbiI6InN0eWxlLWNvbnZlbnRpb25zIn1dfQ== -->

Review

Findings

Low

  • [doc-style] docs/ADRs/0156-require-jira-authorization-entry-for-jira-poll.md:78 — Line is 135 columns: the ADR 0153 link shares a line with prose, so the long-link-target exception in docs/contributing/documentation.md (Line wrapping) does not apply (the link alone fits in about 78 columns).

    Remediation: Put the ADR 0153 link on its own line and wrap the surrounding prose at word boundaries.

  • [doc-style] docs/ADRs/0156-require-jira-authorization-entry-for-jira-poll.md:122 — Line is 101 columns: [ADR 0153](...) already defines for it: keeps trailing prose after the link.

    Remediation: Move already defines for it: to the next line.

  • [doc-style] docs/ADRs/0156-require-jira-authorization-entry-for-jira-poll.md:131 — Line is 145 columns: loading stay as [ADR 0153](...) decided them, and the two-line entry resolves every.
    Remediation: Put the ADR 0153 link on its own line and wrap the clauses before and after it.


Labels: PR adds an ADR and updates architecture docs


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added type/adr component/docs User-facing documentation labels Nov 2, 2026
@codecov

codecov Bot commented Nov 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Add an opening paragraph to Context that says what teams are trying to do
with Jira-driven agents and why an explicit authorization choice matters,
before any component is named. Shorten the Status note and fold the
driver description into the technical paragraph so it no longer repeats
the opening.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Bill Murdock <bmurdock@redhat.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ⚠️ Cancelled · Started 6:49 PM UTC · Completed 6:55 PM UTC

Commit: 8562568 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.74

This review was superseded by a newer commit. Check the current pull request HEAD's review status before merging.

Open Context with the executive story: one authorization source before
#8892, bad on two counts; alternatives added non-breaking; the old way
left as a silent default; this ADR removes the default without
installing another. Technical restatement and code citation follow.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Bill Murdock <bmurdock@redhat.com>
Put each ADR 0153 link on its own line so the surrounding prose stays
within the 80-column guide (review findings on ce17c86).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Bill Murdock <bmurdock@redhat.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ⚠️ Cancelled · Started 6:57 PM UTC · Completed 7:02 PM UTC

Commit: 36842db · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.66

This review was superseded by a newer commit. Check the current pull request HEAD's review status before merging.

@fullsend-ai-review

fullsend-ai-review Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 7:04 PM UTC · Completed 7:15 PM UTC

Commit: 999b6b5 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.20

fullsend-ai-review[bot]

This comment was marked as outdated.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

ADR 0157: Require explicit Jira authorization for jira-poll

📝 Documentation 🕐 10-20 Minutes

Grey Divider

AI Description

• Records a decision to require explicit Jira authorization when a repository runs jira-poll.
• Defines a warning release, a later startup requirement, and a configuration entry that preserves
 project-role behavior.
• Marks ADR 0153’s opt-in rule as superseded and updates the architecture summary.
Diagram

graph TD
  A["Jira poll starts"] --> B{"Jira entry?"}
  B -->|present| C["Selected role source"] --> F["Authorize events"]
  B -->|missing, warning release| D["Warn; use roles"] --> F
  B -->|missing, removal release| E["Reject startup"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Keep Jira authorization opt-in
  • ➕ No migration or startup compatibility change.
  • ➖ Leaves the admin-requiring project-role fallback implicit and easy to overlook.
2. Default to Jira Edit Issues permission
  • ➕ Removes the implicit project-role fallback without requiring a config edit.
  • ➖ Could silently broaden who can trigger agents in repositories that have not chosen that policy.

Recommendation: Keep the ADR’s explicit-entry approach. Its staged warning and failure make the choice visible while allowing repositories to preserve existing behavior with labels: project_roles; the alternatives either retain an unsafe implicit default or risk silently changing authorization. Implementation remains tracked separately in #9005 and #9006.

Files changed (3) +182 / -1

Documentation (3) +182 / -1
0153-authorize-jira-poll-actors-without-project-administration.mdMark ADR 0153’s opt-in rule as superseded +7/-0

Mark ADR 0153’s opt-in rule as superseded

• Adds a status note linking to ADR 0157. It clarifies that the opt-in rule is superseded while the existing lists, label rules, and roster-loading decisions remain.

docs/ADRs/0153-authorize-jira-poll-actors-without-project-administration.md

0157-require-jira-authorization-entry-for-jira-poll.mdRecord the explicit Jira authorization decision and rollout +168/-0

Record the explicit Jira authorization decision and rollout

• Documents why an implicit project-role fallback is undesirable and chooses a required Jira entry for 'jira-poll'. Specifies a poller warning followed by a breaking startup check, the behavior-preserving migration entry, forge scope, and follow-up documentation obligations.

docs/ADRs/0157-require-jira-authorization-entry-for-jira-poll.md

architecture.mdSummarize the planned Jira authorization requirement +7/-1

Summarize the planned Jira authorization requirement

• Updates the Jira polling architecture summary to link ADR 0157 and its rollout issues. Identifies the explicit 'labels: project_roles' entry as the migration for repositories retaining current behavior.

docs/architecture.md

@fullsend-ai-review

fullsend-ai-review Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 4:26 PM UTC · Completed 4:31 PM UTC

Commit: 6603b45 · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $0.82

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review November 3, 2026 16:31

Superseded by updated review

@fullsend-ai-review fullsend-ai-review Bot added ready-for-merge All reviewers approved — ready to merge and removed requires-manual-review Review requires human judgment labels Nov 3, 2026
@ralphbean

Copy link
Copy Markdown
Member

Good stuff - thank you for hacking on it.

The Context paragraph said a repository lists Jira groups and accounts
"in its own config" without saying which file. Name the file so a reader
who stops at the story does not have to guess.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Bill Murdock <bmurdock@redhat.com>

@ifireball ifireball left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved.

I think there is one aspect of ADR 153 that is mentioned here as well that we should change: When labels is set to jira_editors, the ADRs claim that the poller needs to ignore label events made by its own account. This renders the primary use case of labels as a bot work hand-off mechanism non functional. Not sure it its in this ADR's scope to deal with that, but we should deal with it never the less.

Resolve the docs/architecture.md conflict by keeping both additions:
the ADR 0157 deprecation sentence on the Jira poll bullet and main's
new bullet for ADR 0156.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: Bill Murdock <bmurdock@redhat.com>
@fullsend-ai-review

fullsend-ai-review Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 2:17 PM UTC · Completed 2:25 PM UTC

Commit: 8f3739e · View workflow run →

Runtime: pi · Model: sonnet → claude-sonnet-5-5 · Effort: high · Cost: $1.56

@fullsend-ai-review fullsend-ai-review Bot removed the ready-for-merge All reviewers approved — ready to merge label Nov 11, 2026
@fullsend-ai-review
fullsend-ai-review Bot dismissed their stale review November 11, 2026 14:25

Superseded by updated review

@jwm4

jwm4 commented Nov 12, 2026

Copy link
Copy Markdown
Contributor Author

Thanks for the review, and you are right about the behavior. I checked the code: the poller drops every event it classifies as bot-authored before authorization runs, and its own account always counts as a bot. Two details beyond what you wrote: the filter applies in every labels: mode, not only jira_editors, and a second automation account gets through or not depending on its Jira account type and display name.

I agree it should be dealt with, and I think it is a separate decision from this one. This ADR only makes the jira entry required and leaves the meaning of an entry as ADR 0153 set it. The self-account filter was also added on purpose in #6835 to stop an agent from re-triggering itself, so changing it needs its own decision record. I filed #9389, which proposes an ADR that lets a bot-added label start agents on Jira, as ADR 0107 already allows on GitHub.

Bill Murdock with assistance from Claude Code

@jwm4
jwm4 added this pull request to the merge queue Nov 12, 2026
Merged via the queue into main with commit 1dc30e8 Nov 12, 2026
53 checks passed
@jwm4
jwm4 deleted the adr-jira-entry-required branch November 12, 2026 21:24

This branch was successfully deployed

1 active and 1 inactive deployments
site-preview — 8f3739e2 Deployed Nov 11, 2026 by github-actions[bot]
dev — 8f3739e2 Deployed Nov 11, 2026 by jwm4 via behaviour #19688
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/docs User-facing documentation ready-for-merge All reviewers approved — ready to merge risk/moderate PR risk: moderate type/adr

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ADR: deprecate running the jira-poll driver with no jira authorization entry

3 participants