[haiku-bugs] Re: [Haiku] #5102: Add "Not applicable" selection to Milestone, Version and Platform fields in Trac

  • From: "nielx" <trac@xxxxxxxxxxxx>
  • Date: Sun, 13 Dec 2009 13:19:28 -0000

#5102: Add "Not applicable" selection to Milestone, Version and Platform fields 
in
Trac
--------------------------+-------------------------------------------------
 Reporter:  koki          |       Owner:  nielx   
     Type:  enhancement   |      Status:  assigned
 Priority:  normal        |   Milestone:          
Component:  Website/Trac  |     Version:          
 Keywords:                |   Blockedby:          
 Platform:  All           |    Blocking:          
--------------------------+-------------------------------------------------

Comment(by nielx):

 Replying to [comment:7 koki]:
 > Replying to [comment:6 nielx]:
 > > I will try another approach:
 > >
 > > I am going to write a short script that changes the Version, Milestone
 and Platform field to an empty one, and that disables the fields when the
 component Website is selected. I think that would most effectively solve
 the problem. Any thoughts?
 >
 > That sounds like the ideal solution, but there may be situations where a
 change/enhancement for the Website subcomponent could be tied to a
 milestone, such as when preparing the website for a release (as was the
 case for alpha 1).

 I agree.

 > Perhaps the script can automatically select "N/A" as the default for the
 Website components, but not disable the controls in case they need to be
 overridden?

 Okay, I have a version 1 of the script that can be found at:
 http://hg.haiku-os.org/trac-customizations/rev/0f0b9d549af5

 What it does: when the 'Website' component is selected, it will clear the
 Version, Milestone and Platform fields and it will disable them.

 This only applies to the new ticket page (at /newtickets). This enables it
 for developers that handle the ticket to set them anyway they like (for
 maximum flexibility). So if they think a version applies, or a milestone
 they can do so.

 This change makes the assumption that these fields are filled in wrongly
 because the reporter does not take the time to set them to None. That's
 why I think it is not necessary to add an N/A field.

 Opinions?

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/5102#comment:8>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts:

  1. Home
  2. haiku-bugs
  3. Archive
  4. 12-2009