Work Item Tags - quality-manager/onboarding GitHub Wiki

Work Item Tags

Tags commonly used on work items.

All Work Items

  • ua-edit-draft-<version>: Work items that need UA reviews for articles, technotes, and readme files. Added when the developer adds the UA review request.

  • ua-edit-final-<version>: Work items that have gone through UA reviews for articles, technotes, and readme files. Added after the final content review request is approved.

  • msg-draft-<version>: Work items that need UA reviews for error messages. Added when the developer adds the UA review request.

  • msg-final-<version>: Work items that have gone through UA reviews for error messages. Added after the final content review request for the message is approved.

  • no_nn: Work items (typically feature tasks or enhancements) that do not require a new & noteworthy task and entry at the end of the sprint/release.

  • no_pii: Work items (typically defects, tasks, or enhancements) that do not introduce translated string changes (added/updated/deleted). All fixed work items must contain either the no_pii, tvt<version>, tvt<version>_complete, or tvt_exclude tag. Note: As of ETM 7.0.2, use the Translation work item property (required when resolving a work item).

  • tvt<version>: Work items (typically defects, tasks, or enhancements) that introduce translated string changes (added/updated/deleted) and require creating/updating TVT case(s). For example, tvt70. All fixed work items must contain either the no_pii, tvt<version>, tvt<version>_complete, or tvt_exclude tag. Note: As of ETM 7.0.2, use the Translation work item property (required when resolving a work item).

  • tvt<version>_complete: Work items (typically defects, tasks, or enhancements) that introduce translated string changes (added/updated/deleted) and required new/updated TVT case(s) are complete. For example, tvt70_complete. All fixed work items must contain either the no_pii, tvt<version>, tvt<version>_complete, or tvt_exclude tag. Note: As of ETM 7.0.2, use the Translation work item property (required when resolving a work item).

  • tvt_exclude: Work items (typically defects, tasks, or enhancements) that introduce translated string changes (added/updated/deleted) and do not require creating/updating TVT case(s). For example, non-UI changes. All fixed work items must contain either the no_pii, tvt<version>, tvt<version>_complete, or tvt_exclude tag. Note: As of ETM 7.0.2, use the Translation work item property (required when resolving a work item).

  • no_fvt: Work items that do not require FVT cases (e.g. OSLC Cleaner Utility changes).

  • extra_fvt: Work items that require extra FVTing during the milestone where the change/fix was delivered (see query).

  • relnote_<version>: For marking the work item as release notes (Workaround or Limitation).

Plan Items

  • epic: An epic plan item.

  • epic_plan: A plan item is a child of a parent epic plan item.

  • needinfo.om: A plan item that requires more information from Offering Management (OM) to finish scoping capability and requirements.

  • needinfo.dev: A plan item that requires more information from development to finish scoping capability and requirements.

  • needinfo.design: A plan item that requires more information from design before starting work.

  • non-dev: A plan item that is owned and lead by a non-development team.

  • non-dev+: A plan item that is owned and lead by a non-development team but may require work by a development team.

  • xcut: A plan item that is cross-cutting, likely to involve significant cross-application team coordination and may need a feature team (alone or with other related cross-cutting items).

  • elm: A plan item that is associated and contributes to an ELM plan item.

  • elm.qos: A plan item that is associated and contributes to an ELM plan item related to quality of service.

  • elm.feature: A plan item that is associated and contributes to an ELM plan item requiring a cross-application feature team.

  • elm.ux.transformation: A plan item that is associated and contributes to an ELM plan item related to User eXperience (UX) transformation.

  • jaf_req: A plan item with a Jazz Application Framework (JAF) dependency.

  • committed: A plan item that represents a customer commitment.

Tasks

  • debug_patch: Tasks used by the L3 Team to create debug patches (generally debug/trace-level logging) for investigating support cases in customer environments.

  • fvt_<version>: New test automation tasks for a release. For example, fvt_70.

  • scrub_task: For product tasks (quality, development, and project tasks) that have been scrubbed (or reviewed for a valid symptom and correct priority, severity, regression, owner, component, etc.). For example, scrub_task.

Enhancements

  • qm_enh: Enhancements that improve the usability, functionality, and usefulness of the product. Note, do not use any qm_enh<version>_ tags.

  • qm_enh_cust: Enhancements that improve the usability, functionality, and usefulness of the product and requested by active users/customers. Note, do not use any qm_enh<version>cust tags.

  • qm_enh_debt: Enhancements that improve the usability, functionality, and usefulness of the product and remaining technical debt from feature work completed in a previous release. Note, do not use any qm_enh<version>debt tags.

  • qm_enh_sup: Enhancements that improve the usability, functionality, and usefulness of the product and requested by support (L2/SWAT/L3) related to support cases/collaborations. Note, do not use any qm_enh<version>sup tags.

Defects

  • Skipped Resources

  • nis_<version>: Defects not in scope for the release. For example, nis_701.

  • L3BP: Non-customer found defects that need to be backported and customer found defects that are serious enough to not wait for a Test Fix request.

  • l3bp_done: Defects that have their backport(s) complete.

  • ifix_<version>: Defects that need to be backported to a specific release. For example, ifix_701.

  • qm_regression: Test automation coverage for regression defects.

  • rqm-testscript-issue-pipeline: CSPF test script defects found in the test automation pipeline.

  • cdp_product_issue: Product defects found in the test automation pipeline.

  • fvt_dev_qm_<version>: Product defects found during test automation development. For example, fvt_dev_qm_70.

  • qm_pipeline: For product defects found by the CSPF pipeline.

  • qmi_defect: For product defects found by the QMI pipeline (ETM Reportable REST API JUnits and OSLC QM API JUnits).

  • <version>_scrub: For product defects that have been scrubbed (or reviewed for a valid symptom and correct priority, severity, regression, owner, component, etc.), often near the end of the sprint/release. For example, 701_scrub_defer. Note, previous releases used scrub_<version>. For example, scrub_70.

  • <version>_scrub_defer: For product defects that have been confirmed to be proposed for deferral but do not require the formal deferral process. For example, 701_scrub_defer

  • defer_<version>: For product defects that undergo the formal deferral process. The criteria for these defects is found at Jazz Collaborative ALM dashboard >> <version> Defect Deferrals >> Defect Deferral Process Explanation. Reserved at the ELM level for tracking and reporting the defects for QCERT computation. For example, defer_701

  • cdp_infra_issue: For product defects found by the pipeline (due to issues pertaining to Pipeline/Infrastructure).

  • cdp_product_issue: For product defects found by the pipeline (due to development product(regression) changes).

  • cd_test_issue: For product defects found by the pipeline (due to CSPF test Script issues).

  • Skipped Resources: https://jazz.net/wiki/bin/view/Main/TypesOfSkippedResourcesForQM

  • df_stand_by: For product defects where its defect verification (marking defect as closed) is put on hold for some reasons for example a defect's verification is directly or indirectly dependent on verification/resolution of another defect.