3 messages in com.mysql.lists.eventum-develFields, Views and Required Actions| From | Sent On | Attachments |
|---|---|---|
| Ryan | 15 Oct 2006 10:45 | |
| Bryan Alsdorf | 20 Nov 2006 23:25 | |
| Jostein Martinsen | 21 Nov 2006 01:38 |
| Subject: | Fields, Views and Required Actions![]() |
|---|---|
| From: | Ryan (ry...@rrrangel.com) |
| Date: | 10/15/2006 10:45:49 AM |
| List: | com.mysql.lists.eventum-devel |
I spent the weekend bringing up Eventum to help manage my business's repair projects. I was disappointed with the lack of documentation but overall this is a very solid issue tracking system. While I have setup the system to the point I can start using it, I have some feature requests that are not specific to my use of the package so I wanted to share them with you.
1) There is a fair amount of flexibility for editing which fields show up in the Open screen but there doesn't seem to be any way to change the Close issue screen. For example, when creating a custom field it would be helpful to be able to select that the field should show up in the close screen, just like the checkbox that selects that the field should be shown when opening an issue. But in addition to custom fields, there are some standard fields I'd like in the close field screen as well.
2) Also, in the custom field screen there is a check box stating the field must be filled in order to open the issue. It would be helpful to have the same ability with closing issues. There are fields I want filled in before the issue can be closed. Overall, it would be helpful for Closing issues to get the same treatment (same two check boxes) in the custom field create form as Opening issues gets.
3) There doesn't seem to be any interface to customize the view of the Open issue window. I'd like to be able to change the order of all the fields AND mix custom and standard fields (i.e. first field is standard, second is custom, third standard, etc.)
4) Could you add an interface for the dynamic field backend? There is too much room for error and not enough documentation on how it works in its current form. The interface can just be a front end for generating the php file that is placed in the \customer_field directory. Or, is there a way to get rid of that manual step completely? Maybe save this info in the DB? Either way, it would make the feature much more powerful. I still haven't gotten this working but the Eventum system I setup can still limp without it for now.
Thanks for a great product.
--Ryan




