Hi.
I wish that eventum had been more readily visible as an alternative to
some of the other open source defect trackers. It seems at the outset
that it is much more usable in certain ways for both defect tracking and
tech support than some of the other tools that I've found.
I have a couple of questions that may make or break my use of this tool.
1) Is it possible to define which fields are required on a per project
basis?
2) Is it possible to add custom fields? (I need to have a customer id
associated with every tech support request)
3) Are there comprehensive docs available? (I'd love to read them to
find answers for myself, but I don't see them anywhere.)
This looks like a great project, and while a negative answer to 1 or 2
will probably mean that I can't use Eventum right now, I've book marked
the site and will keep up with developments. I'm really impressed.
Bo
| Thread |
|---|
| • custom fields, required fields, documentation | Bo Gusman | 8 Jun |
| • Re: custom fields, required fields, documentation | Bo Gusman | 8 Jun |
| • Re: custom fields, required fields, documentation | Bryan Alsdorf | 8 Jun |
| • Re: custom fields, required fields, documentation | Bo Gusman | 8 Jun |
| • Status on Close? | Bo Gusman | 8 Jun |
| • Re: Status on Close? | Bryan Alsdorf | 8 Jun |
| • Re: custom fields, required fields, documentation | Bryan Alsdorf | 8 Jun |
| • Configuration Selection? | Bo Gusman | 8 Jun |
| • Integration with customer DB for names/addresses/customer ID | Bo Gusman | 9 Jun |
| • RE: Integration with customer DB for names/addresses/customer ID | Joao Prado Maia | 10 Jun |
| • Re: Configuration Selection? | Bryan Alsdorf | 13 Jun |
| • RE: custom fields, required fields, documentation | Joao Prado Maia | 8 Jun |
| • RE: custom fields, required fields, documentation | Joao Prado Maia | 8 Jun |