Issue Triage
Issue Triage
Section titled “Issue Triage”Efficiently triage and manage incoming issues.
Prerequisites
Section titled “Prerequisites”- Authenticated profile (
atlcli auth login) - Jira permission: Edit Issues, Assign Issues
Use Case
Section titled “Use Case”Your team receives many issues. You need to:
- Review unassigned issues
- Set priorities
- Assign to team members
- Add labels for categorization
Triage Script
Section titled “Triage Script”#!/bin/bash# triage.sh - Interactive issue triage# Usage: ./triage.sh <project>
PROJECT=$1
echo "Fetching unassigned issues..."ISSUES=$(atlcli jira search --jql "project = $PROJECT AND assignee is EMPTY AND status = Open" --json)
echo "$ISSUES" | jq -r '.issues[] | "\(.key): \(.fields.summary)"'
echo ""echo "Enter issue key to triage (or 'q' to quit):"
while read -r KEY; do [ "$KEY" = "q" ] && break
echo "" atlcli jira issue get --key $KEY
echo "" echo "Actions: [a]ssign, [p]riority, [l]abel, [t]ransition, [s]kip" read -r ACTION
case $ACTION in a) echo "Enter assignee account ID:" read -r ASSIGNEE atlcli jira issue update --key $KEY --assignee "$ASSIGNEE" ;; p) echo "Priority (Highest, High, Medium, Low, Lowest):" read -r PRIORITY atlcli jira issue update --key $KEY --priority "$PRIORITY" ;; l) echo "Labels to add (comma-separated):" read -r LABELS atlcli jira issue update --key $KEY --add-labels "$LABELS" ;; t) echo "Available transitions:" atlcli jira issue transitions --key $KEY echo "Enter status:" read -r STATUS atlcli jira issue transition --key $KEY --to "$STATUS" ;; esac
echo "" echo "Next issue (or 'q' to quit):"doneBulk Triage
Section titled “Bulk Triage”For large batches, use bulk operations:
Label by Type
Section titled “Label by Type”# Label all bugsatlcli jira bulk label add bug --jql "project = PROJ AND type = Bug AND labels is EMPTY"
# Label all storiesatlcli jira bulk label add feature --jql "project = PROJ AND type = Story AND labels is EMPTY"Set Default Priority
Section titled “Set Default Priority”# Set medium priority for issues without priorityatlcli jira bulk edit --jql "project = PROJ AND priority is EMPTY" --set priority=MediumAuto-assign by Component
Section titled “Auto-assign by Component”#!/bin/bash# auto-assign.sh - Assign issues by component
# Backend issues to Aliceatlcli jira bulk edit \ --jql "project = PROJ AND component = Backend AND assignee is EMPTY" \ --set assignee=557058:alice-account-id
# Frontend issues to Bobatlcli jira bulk edit \ --jql "project = PROJ AND component = Frontend AND assignee is EMPTY" \ --set assignee=557058:bob-account-idScheduled Triage
Section titled “Scheduled Triage”Run triage automatically:
#!/bin/bash# daily-triage.sh - Run by cron daily
# Move stale issuesatlcli jira bulk transition \ --jql "project = PROJ AND status = Open AND updated < -30d" \ --to "Needs Review"
# Notify about high-priority unassignedCOUNT=$(atlcli jira search \ --jql "project = PROJ AND priority in (Highest, High) AND assignee is EMPTY" \ --json | jq '.total')
if [ "$COUNT" -gt 0 ]; then echo "$COUNT high-priority issues need assignment" | \ mail -s "Jira Triage Alert" team@company.comfi- Use JQL filters to focus triage
- Create saved filters for common queries
- Set up notifications for high-priority items
- Review triage metrics periodically
Related Topics
Section titled “Related Topics”- Jira Issues - Issue operations
- Bulk Operations - Batch updates
- Filters - Save JQL queries
Jira and Confluence are trademarks of Atlassian Corporation Plc.
atlcli is not affiliated with, endorsed by, or sponsored by Atlassian.