Skip to main content

Qa bugs not related to branch

Often times QA will find a bug, report it to the engineer, and after some research it is determined that the bug is not related to the fix that the engineer was working on. We still want to keep track of these testing finds, so instead of invalidating the sub-task we will now move it to become a Fix.

  1. On the subtask, add the labels testing_find and prod_bug (if verified it is a production issue) Note: If this is in regards to a specific plugin, please add that as well under App Type (Form, Galleries, Pop-Up, etc.)
  2. In the top right-hand corner click the Actions icon (...) and select 'Convert to Issue'
  3. In the drop-down menu, choose 'Fixes' and click 'Next'
  4. Add any additional notes to the task (not required) then select 'Next'
  5. Verify that the old value was 'Sub-Task' and the new value is 'Fixes', if correct select 'Finish'
  6. Once you have converted this to a Fix, please then add it to the 'To Discuss/ Prioritized Bug' sprint for further review

keyword stuffing: invalidated, invalidation, production bug, prod bug, prod issue