Create "Report Blender-Studio Issue" Operator #17
Labels
No Label
Kind
Breaking
Kind
Bug
Kind: Community
Kind
Documentation
Kind
Easy
Kind
Enhancement
Kind
Feature
Kind
Proposal
Kind
Security
Kind
Studio Request
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/blender-studio-tools#17
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Problems users find have to be manually reported to either @TinyNick for addon issues or @ZedDB
There is no automatic process for collecting information to create a report, and no automatic process to store reports. This means only urgent issues are resolved, and often without documentation
Current Workaround
@TinyNick is currently manually creating issues on behalf of users that detail issues they send me in blender chat.
For example I made this issue after Rik made a request:
TinyNick/blender-studio-tools#25
Another example of Andy making a request:TinyNick/blender-studio-tools#31
In some cases I am not quick enough to keep up with all the chats and occasionally, while balancing my other work I miss some details like TinyNick/blender-studio-tools#22
Solution
Using the exisitng Report Issue Opertator as a tempate and