UI for custom fields

There is a page for editing these fields now. The UI could be ebter though. How about listing all fields on one page for a give column like 'priority'. The current UI is tedious to make many changes.

to be more clear, just present a column of textboxes with the text of each priority is the #default_value. when the form submits update all form fields.

sime, I think you're looking for your own custom fields beyond Type/Status/Priority. Right now, those are set, with their values being editable. I agree that it would be great to have the ability to create whatever amount of custom fields, but this would have to be done in a clean, intuitive way like the survey.module/forms.module lets you create a form, or CCK... I'd love it if you really looked at this area and proposed a solution/patch. There's plenty code already out there...

Yes, I don't see why we need 3 different tables.

Maybe an "Other information" fieldset, and administrator ability to order the fields (weights).

Yes. certain fields should be required (Type/Status/Priority), and certain values too -- for example, if we make it so that end-users can open a case and its status is automatically "open" (see the relevant other issue for more on this), "open" needs to be a required value.

More thought needs to be put into this, but yes... this stuff could be a lot more flexible. Proposals?

As a first step will merge the three tables.

@killes ...
Well this was a good merge :P rappid one .. how about everything else .. ??
- all admin screens are now broken
- adding new cases impossible
- overall, current functionality state .. Damaged .. although intentions where good to make all fields in one table, though it requires a lot of work to finish

Started to fix some cardinal buggs .. then it was a way overhead .. to many things seam's to be broken, considering reverting to the previous stable.. please mark "Work In Progress" for your future releases .. otherwise nobody will know that this is half backed

Greetz,
T.

tomsys: casetracker is an onoing project and cannot be expected to be fully usable at all times. We are working on the issue.

Things are broken in the version offered for download as well (cvs 12.5. module version 1.49). What can we download who want to try out a functional version?

Best
.r.

just get the most recent version (1.50). Most problem should be fixed there.

Fixed & committed to CVS.Available in version 1.52.

Hi Folks,

Database prefix wrapper was used on field name and though it was not working for me .. here is a small patch .. what will fix it.

Greetz,
T.

thanks, applied