To track the source and resolution of a bugs or a feature request, associate its
tracker artifact with the file release in which it was discovered and fixed.
Tracker artifacts associated with file releases are also displayed separately,
providing a simple way to track all issues that were discovered in or fixed in a
specific file release.
Tip: You can also add associations from the tracker
artifact's Artifact Details page.
-
On the Project Administration page, enable both the
Reported in Release and Fixed in
Release fields.
-
Reported in Release - When submitting a new
artifact, the user can choose from a drop-down list of all releases in
the project to identify the release in which the issue was
discovered.
-
Fixed in Release - After the issue is fixed, the
user can choose from a drop-down list of all releases in the project to
identify the release in which the issue was fixed.
Tip: If either of these fields says Unknown, the
artifact you are working on may be associated with a file release that you
don't have permission to view. You can leave that as it is or change it to a
file release that you do have permission to view.
-
When submitting a new artifact, choose the release in which the issue was
discovered from the Reported in Release drop-down
list.
The drop-down list shows all releases in the project, except those that are in
pending status.
-
After the issue is fixed, update the artifact by choosing the release in which
the issue was resolved from the Fixed in Release
drop-down list.
The drop-down list shows all releases in the project, except those that are in
pending status.
The associated tracker artifacts are displayed on the
Release
Details page, in the
Reported Tracker Artifacts
and
Fixed Tracker Artifacts sections.
Note: To remind yourself of
the details of the association later, look in the Change Log
tab of the associated Artifact Details page.
