Page MenuHome
Paste P841

Changes to the bug submit form
ActivePublic

Authored by Inês Almeida (brita_) on Wed, Nov 28, 9:48 AM.
1c1,5
- Please read [[ https://wiki.blender.org/wiki/Process/Bug_Reports | these tips about bug reports ]], and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, **small and simple** .blend and/or other files to do so if needed, etc.
---
+ **Blender's Bug Tracker is for bug reports only.**
+
+ Proposals and Feedback -> [[ https://devtalk.blender.org/ | devtalk ]], [[ https://blender.community/c/rightclickselect/ | rightclickselect ]]
+ Questions -> [[ https://blender.stackexchange.com/ | blender stackexchange ]], [[ https://blender.chat/channel/support | blender.chat#support ]]
+ Compile or build issues -> IRC freenode channel #blendercoders or mail [[ http://lists.blender.org/mailman/listinfo/bf-committers | bf-committers ]]
5,7c9,10
- Always test with latest official releases from [[ http://www.blender.org/ | blender.org ]].
- Always test with latest test build from [[ http://builder.blender.org/ | builder.blender.org ]].
- For own builds or builds from [[ http://builder.blender.org/ | builder.blender.org ]], include full version information from the splash screen (Date, Hash, and Branch).
---
+ Always test with the latest official release from [[ http://www.blender.org/ | blender.org ]] or daily build from [[ http://builder.blender.org/ | builder.blender.org ]].
+ For local builds or daily builds, include the "Date", "Hash" and "Branch" from the splash screen.
10,16c13,14
- Sometimes driver or software upgrades cause problems. On Windows, try a clean install of graphics drivers from the manufacturer website.
-
- **What not to report here**
-
- For **Blender 2.8, please only report crashes**. The bug tracker will be open for more general reports later.
- Feature requests, see the [[ http://wiki.blender.org/index.php/Dev:Doc/Contact#Requesting_Features | developer contact page ]].
- Compile or build issues, ask on #blendercoders or mail [[ http://lists.blender.org/mailman/listinfo/bf-committers | bf-committers ]].
---
+ Please read [[ https://wiki.blender.org/wiki/Process/Bug_Reports | these tips ]] to make a complete, valid bug report.
+ Sometimes, driver or software upgrades cause problems. On Windows, try a clean install of the graphics drivers.
20c18,19
- Bug fixing is important, the developers will handle a report swiftly. For that reason we need your help to carefully construct a case others can redo. You do your half of the work, then we do our half!
---
+ Bug fixing is important, the developers will handle a report swiftly. For that reason, we need your help to carefully provide instructions that others can follow quickly.
+ You do your half of the work, then we do our half!

Event Timeline

I couldn't make a proper diff out of this :(
Here's an online viewer -> https://www.jstoolset.com/diff/42d2fe4f63978f0d

I made a few changes to try and make less wall of text, to help people skim through it. I put short information first, instead of the "tips".

I removed "For Blender 2.8, please only report crashes", but it could be added back at the very end of the form, if this is not the time.
I changed the link for feature requests because the contact page on the wiki was not copied yet and is not up to date.

Here's how it looks:

It's still not that small :(
Maybe "For local builds or daily builds, include the "Date", "Hash" and "Branch" from the splash screen." could go inside the description default text.

We could also go with:

Not sure which one looks more approachable.

The main issue we have is people not making quality bug reports, with good steps to reproduce and particularly a .blend file. They also often do not specify the Blender version in enough detail. Emphasizing those things is most important I think, so the order seems wrong to me.

People using the bug tracker for the wrong purpose is much less of an issue, so it does not need to be at the top or take up much space at all.

Alrighty, V2:


First time bug reporting?
Read these tips to make a complete, valid bug report.

Please verify:
Always test with the latest official release from blender.org or daily build from builder.blender.org.
For local builds or daily builds, include the "Date", "Hash" and "Branch" from the splash screen.
Find steps to redo the bug consistently.
If there are multiple bugs, make multiple bug reports.
Sometimes, driver or software upgrades cause problems. On Windows, try a clean install of the graphics drivers.

What not to report here!
For feature requests, feedback, questions or issues building Blender, see communication channels.

Help the developers ❤
Bug fixing is important, the developers will handle a report swiftly. For that reason, we need your help to carefully provide instructions that others can follow quickly.
You do your half of the work, then we do our half!


**System Information**
Operating system:
Graphics card:

**Blender Version**
Broken: (example 1) 2.79b official release
        (example 2) 2.80, edbf15d3c044, blender2.8, 2018-11-28.  (note: the date, branch and hash can be found on the splash screen.)
Worked: (optional)

**Short description of error**


**Exact steps for others to reproduce the error**
Based on the default .blend file or a very minimal attached file.

I've now updated the forms based on this, but with some changes.

ooooooooh no ❤❤❤!! :((

For the text in "Help the developers", I put in a line break, because it's a long line in a full screen browser:


But it looks good on a smaller window... so!

I hope this increases the quality of the bug reports :)


Another minor and totally unrelated nitpick:
There's a loose <b> on this form: https://developer.blender.org/transactions/editengine/maniphest.task/view/4/
The create diff form has the line bold from there on.

@Brecht Van Lommel (brecht) how do you feel about the results of the form?
I saw many bug reports that had the hash information, but still many people did not seem to understand that they were supposed to replace some of the information on the default text and just typed "Blender closes" or something similar.
Is this still a significant issue? We can try to put actual fields in the form for 'System Info' and 'Blender Version'.
We can also add "Type of problem": [Crash on Start | Crash | Blender is unresponsive or stuck | Bug | Can't open file | Other].

I see quite a few bugs being closed by inactivity. After the author created a bug, he/she didn't reply even once. Could it be that they aren't getting email notifications?

I don't think changes to the form make that much of a difference either way. We have been through many iterations on the old bug tracker and on Phabricator. We had fields in the old tracker, and some people would put wrong information just to fill things in. They're just a significant amount of users who don't follow instructions no matter what you do.

People not following up on bug reports can have many reasons, maybe they didn't use their real email address when signing up, or just don't want to make the effort to complete the bug report. I don't think there's a problem with people receiving emails when they used the right address.

There's a few things we could do, like making Help > Bug Report in Blender pre-fill information, warning users if they don't attach a .blend file, finish crashpad support, etc. I think all those things are code changes, and not so much changes to the form layout.

@Brecht Van Lommel (brecht), ity shouldn't be possible to have any activity in the dev.b.o for until you verify your email. So that part i didn't quite understand.

One thing which seems to be missing is a note that we don't accept compilation error as bug reports. Not sure there was a decision made to allow those things? But that thing is more efficient in the instant messaging, like IRC.

People could use a throwaway email address.

"issues building Blender" is mentioned under what not to report. If there is an actual problem that needs to be fixed, I don't mind handling it as a bug report though.