Please help me with following questionaire
Thanks

#

Does it support the concept of a "ticket" or the equivalent -- that is, some request or issue entry?
#

Does it support custom data fields? Lots of custom data fields? (As opposed to just a few)
#

Can one customize the interfaces so the layout is tailored? How customizable is it?
#

Can one include logic of some sort to prepopulate and update the fields? If so, how is this logic written -- just through a few options that are available through their interface; or through a macro language; or through .NET or other code that can access their API?
#

Can one add special custom buttons to an interface that progress the person through the workflow -- for example, automatically saving and changing the status?
#

Is there an audit history that lets you see who changed what, when? If yes but just partial, which aspects?
#

Can multiple tickets (i.e. request parts that may be assigned to different people) be associated with a single problem? If so, can one ticket (or equivalent) be configured to prevent a parent ticket from being marked as Complete?
#

Can we access data stored in this system through an API?
#

Can the system support multiple types of requests, each through its own customized interface, and each with its own custom fields? For example, one for each type of department
#

What are the system's capabilities with regard to notifying people about comments added to the ticket/request? What flexibility is available to remember, add and remove, possibly automatically, different recipients?
#

Can the ticket/request support the concept of different status codes?
#

If so, can ownership of the ticket be transferred to different groups (and then assigned or checked out by an individual within that group) as status codes change?
#

Can the system read email message replies from individuals, to attach automatically to a ticket/request?
#

Are notifications saved in the database?
#

Can a custom field be designated to hold an uploaded file, for example an Excel document?
#

Is there a concept of a queue that will show an individual all the tickets they have available to check out, that are currently associated with their department?
#

If an individual checks out a ticket/request, will the department queue (for others in their department) still show that ticket/request as needing to be checked out?
#

Can the queues be ordered according to custom criteria?
#

Can the queues be ordered according to external criteria?