Re: Re: Bugs module, file issues

Tim Lebedkov wrote:

> It was also my first idea. But
> 1. there are too many attributes that are special to bug lists:
>  version,
>  component/subcomponent,
>  status,
>  platform,
>  os,
>  target version,
>  resolution

Add attribures tab to task UI, a table with key value pairs. Add
filter support.

> 2. Most of the attributes must be choosed from predefined lists of values.

A key definition customizer can contain key name and possible
values and freeform allowed checkbox.

>  AFAIK there is no way to store these lists of values in an .ics file.

There is already a NB specifics field stored AFAIK.

> 3. Bugs have IDs. I don't want to enter an ID myself each time I create 
> a bug.

Usertask has an internal ID. However I'm not sure if introducing
user level simple ID matches to generic usertasks requirements.

> 4. There must be no way to delete a bug. A bug must be just marked as 
> resolved.

Also probably does not match to generic usertasks requirements.

> There are also some disadvantages. Computing the spent time is now only 
> for usertasks possible
> and I would like to reuse some code from the usertasks.
> 
> Let me know if you have a good idea how to integrate these 2 concepts

I'd would ignore 3 and 4 requirements, you talk about small
team so you can enforce them by external policy.

   Cc.