On 2013-10-06, at 17:36, [email protected] wrote: > Camillo Bruni wrote: >> seems like it works, >> >> so by default the pharo-internal projects will have the Area "1. Pharo >> Image" set. >> >> Why the "1."? Well I cannot order the Areas, and the first one is selected >> by default :P >> >> The filter "review" and "integration" now only look at issues that have the >> proper Area set. >> >> > > Looks good. The "1." looks fine, but in case it is useful I happened to find > a Fogbugz script "Set Hard Default for Project and Area in New Cases" at [1] > that seems related.
ah ok, I didn't see the script and went for the silly solution fogbugz proposed already for other things (wiki names ...). > I'm curious now whether 'External' projects are then free to use > Milestone=Pharo3.0 if they want to target certain issues of their own to > align with that release date? Yes, this is possible now, as long as the Area is not "1. Pharo Image" everything can be used freely.
signature.asc
Description: Message signed with OpenPGP using GPGMail
