infrastructure
/
blender-org
4
3
Fork 1
Code Issues 6 Pull Requests Projects Releases Wiki Activity

Maniphest could provide better information on task reject #50155

New Issue
Closed
opened 2016-12-02 01:56:52 +01:00 by Lee A. Butler · 12 comments
Lee A. Butler commented 2016-12-02 01:56:52 +01:00
Copy Link

When a bug report is rejected as "invalid", a part of the message indicates that the submitter should "Please follow our submission template and guidelines". This is vague. If the message is going to reference the document, it should provide the document or at least a valid link to it. If Maniphest were to pre-populate a bug report at the time of creation it would further improve communication.

When a bug report is rejected as "invalid", a part of the message indicates that the submitter should "Please follow our submission template and guidelines". This is vague. If the message is going to reference the document, it should provide the document or at least a valid link to it. If Maniphest were to pre-populate a bug report at the time of creation it would further improve communication.
Lee A. Butler commented 2016-12-02 01:56:52 +01:00
Author
Copy Link

Changed status to: 'Open'

Changed status to: 'Open'
Lee A. Butler commented 2016-12-02 01:56:52 +01:00
Author
Copy Link

Added subscriber: @butler

Added subscriber: @butler
Joshua Leung commented 2016-12-02 02:27:46 +01:00
Copy Link

Added subscriber: @JoshuaLeung

Added subscriber: @JoshuaLeung
Joshua Leung commented 2016-12-02 02:27:46 +01:00
Copy Link

I've had a look at what's going on here:

  • If you create a task via Maniphest (i.e. via the '+' in the top-right corner -> Create Task) the description box is left empty (since the task could be for anything). That page is simply titled "Create Task"
  • If you create the task via the "Report Bug" button on the homepage, you'll instead see a page title "BF Blender Bug Report", complete with instructions on what to include in the bug report, as well as a pre-populated description box with a basic template.

I think it was expected that most people would just click the "Report Bug" button rather than using the "Create Task" provided natively by Maniphest. I'll let the web-team decide what to do here :)

I've had a look at what's going on here: * If you create a task via Maniphest (i.e. via the '+' in the top-right corner -> Create Task) the description box is left empty (since the task could be for anything). That page is simply titled "Create Task" * If you create the task via the "Report Bug" button on the homepage, you'll instead see a page title "BF Blender Bug Report", complete with instructions on what to include in the bug report, as well as a pre-populated description box with a basic template. I think it was expected that most people would just click the "Report Bug" button rather than using the "Create Task" provided natively by Maniphest. I'll let the web-team decide what to do here :)
Lee A. Butler commented 2016-12-02 02:39:11 +01:00
Author
Copy Link

Observation: In the following screenshot Capture.PNG, it is not apparent to me where "Report Bug" is located.

Observation: In the following screenshot ![Capture.PNG](https://archive.blender.org/developer/F412881/Capture.PNG), it is not apparent to me where "Report Bug" is located.
Joshua Leung commented 2016-12-02 02:44:50 +01:00
Copy Link

Ah, I was referring to https:*developer.blender.org and not https:*developer.blender.org/maniphest/project/2/type/Bug/

#50155.png

Ah, I was referring to https:*developer.blender.org and not https:*developer.blender.org/maniphest/project/2/type/Bug/ ![#50155.png](https://archive.blender.org/developer/F412884/T50155.png)
Lee A. Butler commented 2016-12-02 02:50:36 +01:00
Author
Copy Link

Ah, yes. On one of my visits I navigated from http:*archive.blender.org/development/report-a-bug/ via the link on Blender Bug Tracker which in turn took me to https:*developer.blender.org/maniphest/ which is why I have that experience. I got to the same page via a google search for Blender bug template for which the 2nd most common hit was https://developer.blender.org/maniphest/project/2/type/Bug/ , so I believe there are multiple paths to a less than ideal interface.

Ah, yes. On one of my visits I navigated from http:*archive.blender.org/development/report-a-bug/ via the link on **Blender Bug Tracker** which in turn took me to https:*developer.blender.org/maniphest/ which is why I have that experience. I got to the same page via a google search for **Blender bug template** for which the 2nd most common hit was https://developer.blender.org/maniphest/project/2/type/Bug/ , so I believe there are multiple paths to a less than ideal interface.
Aaron Carlisle commented 2016-12-02 03:29:19 +01:00
Copy Link

Added subscriber: @Sergey

Added subscriber: @Sergey
Bastien Montagne commented 2016-12-02 08:13:51 +01:00
Copy Link

Added subscriber: @mont29

Added subscriber: @mont29
Bastien Montagne commented 2016-12-02 08:13:51 +01:00
Copy Link

Big 'report bug' button of main page leads to the correct form, will add that link to my canned answer.

As for why the 'report bug' link in the taks page itself links to a different form… maybe this is configurable, (@Sergey would know), maybe this is a quirk from phabricator itself?

Big 'report bug' button of [main page](https:*developer.blender.org) leads to the [correct form](https:*developer.blender.org/maniphest/task/edit/form/1/), will add that link to my canned answer. As for why the 'report bug' link in [the taks page itself](https://developer.blender.org/maniphest/project/2/) links to a different form… maybe this is configurable, (@Sergey would know), maybe this is a quirk from phabricator itself?
Sergey Sharybin commented 2016-12-02 09:49:52 +01:00
Owner
Copy Link

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sergey Sharybin self-assigned this 2016-12-02 09:49:52 +01:00
Sergey Sharybin commented 2016-12-02 09:49:52 +01:00
Owner
Copy Link

Fixed and deployed. Surely there's lots of other possible tweaks, but should be fine for now.

Fixed and deployed. Surely there's lots of other possible tweaks, but should be fine for now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
features_favicon
download-redesign
features
Labels
Clear labels   
legacy module
Rendering & Cycles

  
legacy module
User Interface

  
legacy project
Cycles

  
legacy project
Documentation

  
legacy project
Infrastructure: blender.org

  
legacy project
Infrastructure: Blender Web Assets

  
legacy project
Infrastructure: Websites

  
legacy project
User Interface

  
Priority
High

  
Priority
Low

  
Priority
Normal

  
Priority
Unbreak Now!

  
Status
Archived

  
Status
Confirmed

  
Status
Duplicate

  
Status
Needs Triage

  
Status
Resolved

  
Type
Bug

  
Type
Design

  
Type
Known Issue

  
Type
Report

  
Type
To Do

No Label
legacy module
Rendering & Cycles
legacy module
User Interface
legacy project
Cycles
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Blender Web Assets
legacy project
Infrastructure: Websites
legacy project
User Interface
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Report
Type
To Do
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Sergey Sharybin
5 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: infrastructure/blender-org#50155
No description provided.
Delete Branch "%!s(<nil>)"

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?