Re: Re: Bugs module, file issues

Petr Kuzel wrote:

>>an .issues file could be used in small projects/projects with a small
>>amount of users to track the issues.
>>    
>>
>
>If "users" equals "developers" it makes some sense.
>
The number of users (not developers) should be also small so they
could send their bugs by email and the developer could add them to the
bug list himself. 

>I do not expect
>that end users would be willing to create XML files and send
>them to developers. Even for developers I think that they can
>share 'internally known' bugs as e.g. usertasks. There is already
>category field in user task. You just need to add dependency
>relationship and keywords to usertasks and you are almost done.
>
>Are not you addressing here very specifics use case that is covered
>by more generic use case?
>
>In other words I prefer usertasks improvements over creating
>almost parallel structures in bugs module that is primarily
>focused on integration with existing server based issue tracking
>systems.
>  
>
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
2. Most of the attributes must be choosed from predefined lists of values.
  AFAIK there is no way to store these lists of values in an .ics file.
3. Bugs have IDs. I don't want to enter an ID myself each time I create 
a bug.
4. There must be no way to delete a bug. A bug must be just marked as 
resolved.

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

--Tim.