Triaging Playbook Adjustments #70658

Closed
opened 2019-10-09 01:36:21 +02:00 by Dalai Felinto · 7 comments
  • Review the text of bug triaging playbook
  • Copy to buffer button
  • Create anchors

Bug Triaging Playbook:
https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook

- [ ] Review the text of bug triaging playbook - [ ] Copy to buffer button - [ ] Create anchors Bug Triaging Playbook: https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook
Francesco Siddi was assigned by Dalai Felinto 2019-10-09 01:36:21 +02:00
Author
Owner

Added subscriber: @dfelinto

Added subscriber: @dfelinto

Regarding the additional features for the wiki, I don't have capacity to implement them at the moment.
I moved the skin over here https:*github.com/blender/mediawiki-bootstrap (can be officially hosted on developer.blender.org later), with a README.md calling for help. Would be nice to have a volunteer contribution on this.

Here are a couple of suggestions that could set the tone for the canned responses.
I would recommend a native speaker to take a look at them and make them as friendly and clear as possible. Perhaps it's a good idea to make a call for volunteers for this?

Low quality report

This report is being closed because it does not contain all the information needed by the development team in order to investigate the issue.
Please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, and a .blend file with exact steps to reproduce the problem.

Too complex file report, where user could not simplify enough

Thanks for the report. Unfortunately the scenario described is too complex to troubleshoot. Please help narrowing down the problem description.
Normally .blend files can be simplified by removing unnecessary objects and settings, until the problem reveals itself more clearly.
If there are many steps to reproduce the problem, please attach a .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug.

Feature request

This report is being closed because it is not considered a bug.
Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Regarding the additional features for the wiki, I don't have capacity to implement them at the moment. I moved the skin over here https:*github.com/blender/mediawiki-bootstrap (can be officially hosted on developer.blender.org later), with a [README.md](https:*github.com/blender/mediawiki-bootstrap#get-involved) calling for help. Would be nice to have a volunteer contribution on this. Here are a couple of suggestions that could set the tone for the canned responses. I would recommend a native speaker to take a look at them and make them as friendly and clear as possible. Perhaps it's a good idea to make a call for volunteers for this? ### Low quality report This report is being closed because it does not contain all the information needed by the development team in order to investigate the issue. Please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, and a .blend file with exact steps to reproduce the problem. ### Too complex file report, where user could not simplify enough Thanks for the report. Unfortunately the scenario described is too complex to troubleshoot. Please help narrowing down the problem description. Normally .blend files can be simplified by removing unnecessary objects and settings, until the problem reveals itself more clearly. If there are many steps to reproduce the problem, please attach a .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug. ### Feature request This report is being closed because it is not considered a bug. Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Added subscriber: @ChristopherAnderssarian

Added subscriber: @ChristopherAnderssarian

What about Account deletion requests? (at the moment users can't delete it themselves)
Not only for the triage team, but documentation for uses explaining the process and the ramifications...

Also for duplicate reports.
I've seen developers discriminate based upon:

  • Creation time

  • Quality of the report; Tags, .blend file, ect..

  • Where discussion is happening

Would be nice to be absolutely clear on this.

What about Account deletion requests? (at the moment users can't delete it themselves) Not only for the triage team, but documentation for uses explaining the process and the ramifications... Also for duplicate reports. I've seen developers discriminate based upon: - Creation time - Quality of the report; Tags, .blend file, ect.. - Where discussion is happening Would be nice to be absolutely clear on this.
Author
Owner

re: account deletion request

There are too few of these to be an issue, really. I would rather keep the playbook as lean as possible, and help us with the decision process of the issues we actually don't know how to handle right away.

re: duplicate

Agree that we could have an entry for "closing as duplicate" that explains the process (make sure the remaining one has all the info needed, ...). Could you please write this and I add to the wiki?

re: account deletion request There are too few of these to be an issue, really. I would rather keep the playbook as lean as possible, and help us with the decision process of the issues we actually don't know how to handle right away. re: duplicate Agree that we could have an entry for "closing as duplicate" that explains the process (make sure the remaining one has all the info needed, ...). Could you please write this and I add to the wiki?
Author
Owner

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Author
Owner

Closing this for now. Still welcoming feedbacks. Also note that we now have canned responses

Closing this for now. Still welcoming feedbacks. Also note that we now have canned responses
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#70658
No description provided.