-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathconfig.yaml.example
More file actions
137 lines (130 loc) · 5.06 KB
/
Copy pathconfig.yaml.example
File metadata and controls
137 lines (130 loc) · 5.06 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
# ── Jira connection ──────────────────────────────────────────────
jira:
url: "https://your-instance.atlassian.net"
# Custom field IDs (run jira.fields() to discover for your instance)
qa_contact_field: "customfield_XXXXX"
sprint_field: "customfield_XXXXX"
# ── Bug query filters (all configurable) ─────────────────────────
filters:
project: "Your Project"
component: "Your Component"
issue_types: [Bug, Vulnerability, Weakness]
excluded_statuses: [Closed, Verified]
# Additional JQL clauses appended to the base query (optional).
# Useful for testing or narrowing scope.
extra_jql: "" # e.g. "AND labels = 'my-label'" or "AND created >= -7d"
# ── Triage rules ─────────────────────────────────────────────────
triage:
# Account ID treated as "empty" for assignee/QA Contact checks.
# Find this by inspecting the assignee field of an unassigned bug.
placeholder_user_id: ""
# Cooldown: don't re-comment on a bug if the agent already
# commented within this many days
comment_cooldown_days: 7
# Prefix for agent comments (used to detect previous comments)
comment_prefix: "[Bug Triage Agent]"
# ── LLM configuration ───────────────────────────────────────────
llm:
default_model: "gpt-4o"
temperature: 0.0
# Toggle individual LLM features on/off
features:
suggest_priority: true
suggest_assignee: true
suggest_qa_contact: true
suggest_sprint: true
suggest_fix_version: true
suggest_backport: true
detect_duplicates: true
# ── Team expertise map (for assignee/QA suggestions) ─────────────
team:
members:
- account_id: "atlassian-account-id-1"
name: "Alice Dev"
role: dev # dev | qe | both
areas: [component-a, feature-x, upgrade]
- account_id: "atlassian-account-id-2"
name: "Bob Dev"
role: dev
areas: [component-b, storage, import]
- account_id: "atlassian-account-id-3"
name: "Carol QE"
role: qe
areas: [component-a, upgrade, install]
- account_id: "atlassian-account-id-4"
name: "David QE"
role: qe
areas: [component-b, storage, snapshot]
# ── Sprint/version options (context for LLM suggestions) ─────────
planning:
# Available sprints the LLM can suggest. List active + future ones.
sprints:
- id: 12345
name: "Sprint 42"
state: active # active | future
goal: "v1.2 GA stabilization"
- id: 12346
name: "Sprint 43"
state: future
goal: "v1.3 feature work"
# Available fix versions the LLM can suggest.
fix_versions:
- "v1.2.0"
- "v1.2.z"
- "v1.3.0"
# Guidance for the LLM on how to choose sprint/version
sprint_guidance: >-
Assign critical/blocker bugs to the current active sprint.
Major bugs go to the current sprint if capacity allows,
otherwise the next future sprint. Normal/Minor bugs go to
the next future sprint.
fix_version_guidance: >-
Critical bugs blocking GA go to the current GA version.
Bugs that can wait go to the z-stream. Feature-related
bugs go to the next major version.
# ── Release Calendar (for backport analysis) ─────────────────────
# The LLM uses this to determine which versions are still supported,
# which are approaching EOL, and how far back a fix needs backporting.
releases:
current_dev: "1.3"
versions:
- version: "1.3"
status: dev
ga_date: ""
eol_date: ""
branch: "release-1.3"
- version: "1.2"
status: ga
ga_date: "2026-03-15"
eol_date: "2027-03-15"
branch: "release-1.2"
latest_z: "1.2.1"
- version: "1.1"
status: maintenance
ga_date: "2025-10-01"
eol_date: "2026-10-01"
branch: "release-1.1"
latest_z: "1.1.4"
- version: "1.0"
status: eol
ga_date: "2024-12-01"
eol_date: "2025-12-01"
branch: "release-1.0"
latest_z: "1.0.8"
# Backport policy guidance for the LLM
backport_policy: >-
Backport policy:
- Critical/Security bugs: backport to ALL supported versions
(ga + maintenance, not eol).
- Major bugs: backport to the previous GA version (N-1) if
the bug is a regression or affects a core workflow.
- Normal bugs: backport only if the fix is low-risk and the
version is still in GA phase (not maintenance-only).
- Minor/Trivial: no backport — fix only in current dev.
- Never backport to EOL versions.
- Consider the EOL date: if a version goes EOL within 30 days,
skip the backport unless it's Critical/Security.
# ── Duplicate detection ─────────────────────────────────────────
duplicates:
max_candidates: 50
threshold: 0.8