Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CONCEPT] Rules/Requirements for New Triage Board #12

Open
sdzhepa opened this issue Jun 8, 2020 · 3 comments
Open

[CONCEPT] Rules/Requirements for New Triage Board #12

sdzhepa opened this issue Jun 8, 2020 · 3 comments
Assignees

Comments

@sdzhepa
Copy link
Owner

sdzhepa commented Jun 8, 2020

Requirements

  • Each new issue(BUG related to M2 based on template) should be added to the board in the "Ready for Confirmation" column

Confirmation process

CASE 1: New by comment
  1. User: puts the comment @magento confirm issue
  2. BOT: "Issue: Confirmed" label is set
  3. BOT: "Reproduced on 2.XX" set automatically based on the latest release line
  4. BOT: Internal Jira is created and the comment appears

NOTE 1:

  • no additional labels or actions required to confirm issue
  • OPTIONAL: User can set additional labels if she/he wants

NOTE 2: Added new column "Needs Update" instead of "Confirmation is progress"
This column contains all card that has labels

  • Cannot reproduce
  • Progress: Need update
CASE 2: Old By labeling Need to discuss.....could be recursy
  1. User: set label "Issue: Confirmed"
  2. BOT: label "Reproduced on 2.XX" set automatically based on the latest release line
  3. BOT: Internal Jira is created and the comment appears

Workflow: Maintainers Confirmation Process.

  1. User takes(assigned) Issue for confirmation
    = IssueCard AUTOMATICALLY moves into "Confirmation in Progress" column
    = If IssueCard does not have an assignee and label "Issue: Confirmed". BOT moves it to the "Ready for Confirmation" column

  2. User confirms Issue by comment or label "Issue: Confirmed"
    = IssueCard AUTOMATICALLY moves into "Confirmed" column
    = IssueCard AUTOMATICALLY removes assignee from Issue

  3. If Label "Issue: Confirmed" was removed,
    = issueCard AUTOMATICALLY added to board/project "Ready for Confirmation" column

  4. If issue was reopened
    = Labels "Issue: Confirmed" and All "Reproduced on 2.XX" AUTOMATICALLY removed
    = Issue AUTOMATICALLY added to board/project "Ready for Confirmation" column

Workflow: Triage process.

Preparation issue for triage

  1. Review Card in "Confirmed" column

  2. If Issue has all required information and can be presented during Triage meeting
    = MANUAL: Move to the "Ready for Triage" column
    = OR automatically move is issue labeled "Triage: Ready for Triage"

  3. After Triage, if no additional questions.(P and S are set)
    = Manual: set label "Triage: Internal Triage Done" (mb need to rename Triage: Done)
    = Manual/Automated: Issue/card is removed from this board
    = Manual/Automated: Issue/card is added to another board into "Ready for dev"/"Ready for Grooming" column
    = Automated: Related Jira ticket is updated according to S and P and has the status "Triaged"

  4. If during Triage meeting appears additional Questions to a reporter or need another Person review/confirmation
    = Manual: IssueCard moves to the "Need additional Information/Approve" column

If issue is not reproducible or requires additional information from a reporter - it should be reflected on board

ADDITIONAL

  1. Logic related to validating issue description "Format is not valid" should be removed. Should be checked all internal tools(apps/engcom-portal)
  2. Documentation on WIKI should be updated
  3. Documentation on DevDoc should be updated
  4. Bot advice comment should be updated
@sdzhepa sdzhepa changed the title Rules for New Triage Board [CONCEPT] Rules/Requirements for New Triage Board Jun 8, 2020
@sdzhepa sdzhepa self-assigned this Jun 8, 2020
@okorshenko
Copy link

okorshenko commented Jun 9, 2020

Proposed command format:
@magento issue is confirmed
@magento issue confirmed
@magento issue is confirmed on 2.4-develop
@magento issue confirmed on 2.3.5-p2

Only Issue Type: Bug should go through this flow
We can update issue template and add [BUG] by default to the title

@sdzhepa
Copy link
Owner Author

sdzhepa commented Jun 15, 2020

Card in column Triage done should have label "Progress: Ready for Dev"

@sdzhepa
Copy link
Owner Author

sdzhepa commented Jun 24, 2020

Added new column "Needs Update"

This column contains all card that has labels

  • Cannot reproduce
  • Progress: Need update

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants