On Mon, Nov 15, 2010 at 1:00 PM, Tai Lee wrote:
> I like the idea of needmoreinfo as a resolution, which makes it clear
> to the reporter that they need to take the next step to re-open the
> ticket with more info. I don't think that closed with "invalid" and a
> comment makes this as clear.
>
> H
I like the idea of needmoreinfo as a resolution, which makes it clear
to the reporter that they need to take the next step to re-open the
ticket with more info. I don't think that closed with "invalid" and a
comment makes this as clear.
However, I think there's another problem area where we need t
On Sun, Nov 14, 2010 at 5:22 PM, Andrew Godwin wrote:
> On 13/11/10 16:52, Daniel Moisset wrote:
>>
>> Hi,
>> while working on the sprint today doing triaging we noticed that a
>> lot of tickets were in the "Unreviewed" state because actually there's
>> not enough information to move it to any
Hi, while working on a project requiring the definition of a custom
model field I realized there was no way to provide definition
validation nor override subclass validation. For example, there's no
way of subclassing a field and overriding the way a certain parameter
(lets say max_length or choice
On 13/11/10 16:52, Daniel Moisset wrote:
Hi,
while working on the sprint today doing triaging we noticed that a
lot of tickets were in the "Unreviewed" state because actually there's
not enough information to move it to any other state (they can not be
neither accepted/DDNd nor closed). In mo
