Anyone else have any comments on this? -------------------------------------------- Quinton McCombs NequalsOne - HealthCare marketing tools mailto:[EMAIL PROTECTED] http://www.NequalsOne.com
> -----Original Message----- > From: Quinton McCombs > Sent: Friday, March 14, 2003 8:09 PM > To: [EMAIL PROTECTED] > Subject: Proposed Scarab chnages > > > Okay. As promised here is my list of propsed changes to > Scarab for the Turbine modules. Please let me know what you > think. If we all agree on this, I will lobby the scarab > admin(s) lurking on the list to implement the changes for us. > > Issue types: > > Remove the Feature, Task, and Patch issue types. All issues > can be classified as a Defect or an Enhancement. Patches > should always be attached to a Defect or an Enhancement issue. > > Defects: > > Group 1: Summary > > Attributes: > > - Summary: long-string: This should be a brief summary of the issue. > > Group 2: Details > > Attributes: > > - Description: long-string: This should describe in as much > detail as possible exactly what the problem is. Information > on how to recreate would be greatly appreciated > > - Functional Area: drop down: This is the area of turbine in > which the problem is occuring. Areas would include unknown, > Intake, Scheduler, core, unlisted service, etc... This will > help record what area of Turbine are having the most > problems. The user might not really know what to pick but > the developer who addresses the problem will. > > - Reported Version: drop down: This is a list of the various > versions of Turbine. It would include 2.1, 2.2, 2.2.1-dev, > 2.3-dev, other. This is intended to be the version of > Turbine that the user is reporting the problem against. > > - Operating system: drop down: The operating system on which > the user is running Turbine > > - Java version: drop down: The version of java on which the > user is running Turbine > > - Priority: drop down: The current list is fine. This is the > priority or ugency of the defect as seen by the user. > > Group 3: Status > > Attributes: > > - Status: drop-down: This is the current status of the issue. > It would include only the following values: New, Assigned, > Reopened, and closed > > - Resolution: drop down: This indicated the final resultion > of the issue if it is closed. It should include the > following values: Fixed, wontfix, invalid, duplicate, worksforme. > > Group 4: Resolution > > - Resolution Details: long-string: This will describe how the > problem was fixed. > > - Resolved In Version: drop-down: This is the version of > turbine in which the defect was fixed. This will be the same > list of values found in the Reported Version attribute. > > Enhancements: > > This issue type will be exactly like the defect issue without > the operating systen or java version attributes. > > > Also - Add a user attribute type called "voter". This will > show up on the personnel tab. People who wish to vote for a > particula issue to be worked on, can add themselves as a > voter. They will also get an email notification when the > issue is updated. > > -------------------------------------------- > Quinton McCombs > NequalsOne - HealthCare marketing tools > mailto:[EMAIL PROTECTED] > http://www.NequalsOne.com > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
