Log a bug against a release
Lesson 2 of 4
A deployment failed when a failure points at it. A failure is a work item of a failure type, a Bug by default, that names the release under Affects versions, or that links to a work item of the release. This lesson logs one against Checkout 1.6 and records the release that fixes it.
Log the bug
-
Create the bug in your space, CHK. Press Create, pick the work type Bug, and give it a summary, here “Checkout times out on card retry”.
-
In Details, set Affects versions to the release it was found in, here Checkout 1.6. The bug now points at that release.
-
Or link it instead. Press the plus button under the title, pick Link work item, and search for a work item of the release by its key, here CHK-31. Any link type counts, so relates to works. Changeline reads the link either way.
Record the fix
-
When the fix ships, set the bug’s Fix versions to the release that ships it, here Checkout 1.7. Changeline reads that release as the recovery: the failure’s creation to the release that ships its fix.
-
A bug with no fix version recovers when it reaches Done.
If you don’t see it
If Affects versions is not in Details, the space’s screen does not hold the field. A space admin adds it under the space’s settings. Without it, use the link.
If the work type is not Bug, Changeline counts it only when a Jira admin names it as a failure type in Settings. Every work type whose name contains Incident counts by default.
What you have now
A bug that points at Checkout 1.6, and a fix that ships in 1.7. Changeline counts Checkout 1.6 as a failed deployment, and the bug’s time to recovery on the Recovery tab. Next you make lead time start at the branch.