But of course! I have the necessary Scarab admin rights, but I would prefer that John McNally review the change before it is made (John is way more intimate with the workings of Scarab than I will ever be).
Here is what I believe needs to be done: 1. Create a new global attribute: Version (input type is string) 2. Edit the five issue types, adding a new attribute group that will be defined to include the new Version attribute. That seems about it. Note that I am suggesting the input type of string as this makes a nice generic field that can be applied across the board. We could define something like "Turbine version" and provide a selection list, but this wouldn't be appropriate for all modules (I don't see an obvious way to indicate that an attribute group should only apply to a specific set of modules or alternatively how to alter the list of available values depending on the selected module). John: Is this all that needs to be done to make this happen? Thanks, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com On 4/01/2003 3:26 PM, "Quinton McCombs" <[EMAIL PROTECTED]> wrote: > I was really just asking for the field to be added to our installation. > Who ever has admin right to Scarab can do it. Scarab already supports > it. > >> -----Original Message----- >> From: Scott Eade [mailto:[EMAIL PROTECTED]] >> Sent: Friday, January 03, 2003 10:02 PM >> To: turbine-dev >> Subject: Re: Request for change on Scarab >> >> >> Quinton, >> >> If you visit scarab.tigris.org you should find a link to the >> issue tracking system for scarab (a different scarab install >> to the one we use) where you can raise an enhancement request. >> >> Scott >> -- >> Scott Eade >> Backstage Technologies Pty. Ltd. >> http://www.backstagetech.com.au .Mac Chat/AIM: > seade at mac dot com >> >> >> On 4/01/2003 8:59 AM, "Quinton McCombs" >> <[EMAIL PROTECTED]> wrote: >> >>> Can we get a new field added for the various issue types to >> track the >>> current version the user was running when the issue was discovered? >>> >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:turbine-dev-> [EMAIL PROTECTED]> >> For >> additional commands, >> e-mail: <mailto:[EMAIL PROTECTED]> >> >> > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
