Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A apertis-issues
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • infrastructure
  • apertis-issues
  • Issues
  • #272
Closed
Open
Issue created Feb 09, 2023 by Walter Lozano@wlozanoMaintainer

QA Report App does not handle task-per-release when using Phabricator

Background

QA Report App has the ability to automatically create tasks when tests fail on LAVA using either Gitlab issues or Phabricator as bug tracking system.

By default failures on different releases are treated under the same task, however, for components under development, it is worth to create tasks release specific since they could be to different root causes.

This feature works well when using Gitlab as bug tracking system, but does not when using Phabricator.

Root cause

describe in one line what caused the issue to give a hint to product teams whether they may be impacted or not

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @andrunko @em @sagar @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T9571

Edited Feb 09, 2023 by Apertis CI robot
Assignee
Assign to
Time tracking
Apertis Website Terms of Use Privacy Policy