Keep IT bug subtasks and custom fields up to date

IT engineers get bug webhooks that leave subtask statuses stale, causing poor triage and risky releases. Updates set statuses and key custom fields so product and engineering trust backlog records.

Overview

Stale subtask statuses leave triage blind and put release decisions at risk for IT and product teams. This workflow keeps subtask statuses and critical custom fields current so engineers stop reconciling records and rely on the backlog for sprint and release planning.

Notable Features

Set subtask status from incoming bug report
Populate custom fields with critical metadata
Skip updates for completed subtasks