#12140: Clarify Trac menus for new reporters -------------------------------------+------------------------------------- Reporter: goldfire | Owner: hvr Type: bug | Status: new Priority: normal | Milestone: Component: Trac & Git | Version: 8.0.1 Keywords: | Operating System: Unknown/Multiple Architecture: | Type of failure: None/Unknown Unknown/Multiple | Test Case: | Blocked By: Blocking: | Related Tickets: Differential Rev(s): | Wiki Page: -------------------------------------+------------------------------------- An officemate of mine rarely posts bugs here. He finds the interface to posting a bug confusing. I have to say I agree, if I consider the perspective of an infrequent reporter. (The reason he rarely posts bugs is that he rarely has bugs to post, not because of the confusing interface.) Specifically, there are many fields to fill out when posting a bug. Some of these are important to us (`Version` probably being the most). Some are better for developers to set (`Milestone`, `Test case`). Some are less important (`Operating System` for a bug in the type-checker). Some are essentially ignored (`Type of failure`, in my experience). Yet a new reporter doesn't know any of this and will diligently try to fill out them all. Can we label the fields as to importance somehow? Mark some as advanced/dev only? Make some available only after posting the ticket (`Test case`, `Differential`)? I don't suppose there are masses of people out there trying to post bugs and stymied by this problem, but I do think we can clean this up a bit. -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/12140 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler