Skip to content

Commit 5bdf6cb

Browse files
committed
Temporarily remove setting of target end in triaging
As discussed in packit#83
1 parent 0260507 commit 5bdf6cb

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

beeai/agents/triage_agent.py

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -203,15 +203,14 @@ def render_prompt(input: InputSchema) -> str:
203203
204204
**Final Step: Set JIRA Fields (for Rebase and Backport decisions only)**
205205
206-
If your decision is rebase or backport, use set_jira_fields tool to update JIRA fields (Severity, Fix Version, Target End):
206+
If your decision is rebase or backport, use set_jira_fields tool to update JIRA fields (Severity, Fix Version):
207207
1. Check all of the mentioned fields in the JIRA issue and don't modify those that are already set
208208
2. Extract the affected RHEL major version from the JIRA issue (look in Affects Version/s field or issue description)
209209
3. Determine if this is a very critical issue requiring Z-stream (only for: privilege escalation, remote code execution, data loss/corruption, or system compromise)
210210
4. Use map_version tool with the major version and criticality to get the appropriate Fix Version and branch
211211
5. Set JIRA fields:
212212
* Severity: default to 'moderate', for important issues use 'important', for most critical use 'critical' (privilege escalation, RCE, data loss)
213213
* Fix Version: use the fix_version from map_version tool result
214-
* Target End: today + 14 days
215214
6. Use the branch from map_version tool result for your output
216215
217216
**Output Format**

0 commit comments

Comments
 (0)