Definitions of default incident fields.

[wbmore]

I have been asked to explain reporting based on how to best determine what field to use. Reports seemed very straight forward to me so I was unsure what she needed. After looking at the wiki and further discussion I found what she was really looking for is definitions of each of the fields on the incident form. In the future I am sure this will be for all forms, but incident is our bread and butter currently. What enlightened me to her need was the active field. She said this field is perfect now that she knows it indicates the status of the incident, (open or closed) but she had no clue what that field was for. I found a comments section on the table but it is empty. As I don't want to recreate the wheel what I am looking for is a layman's dictionary of the defaults fields from the incident table.

Thanks

[Mark Stanger]

There's no global dictionary other than the system dictionary for fields that I know of. I think one reason for this is that many of the fields can mean very different things to different companies depending on how they are used in the system.
Also, you'll want to remember that many of the fields on the incident form are shared across all tasks. In some cases, the same field may have different meanings depending on whether it shows up on Incident, Problem, Change, etc.
In addition to the dictionary, you might look at the labels for fields for some sort of definition. The labels themselves -- and more often the hints on those field labels -- can give insight as to what the field is used for.

[wbmore]

I agree that task would have been a better table to start with. I have looked at the dictionary and the labels for Business Duration: and Business Resolve Time: and the amount of intuition is based on the user's experience of the software and their level access to open up and dig. Very few people have the access to make educated decisions about the fields without a lot of trial and error. I disagree that an out of the box vocabulary is not possible. It could even be as simple as putting in the comments what the field's initial intention is. That could be modified if the field is modified. The comments could list the different uses for the different tables. You could even prompt the person changing the fields function to update the comment so they keep their documentation updated and accurate or make a choice not to, poor choice in my opinion. No I don't practice this in everything I have done, but I have started to focus a great deal more on making what I do usable for those who follow me without guessing or spending hours trying to ferret out how it all ties together.

A vocabulary list of element types would be helpful as well. Point in case business_stc. What is it, how is it best put to use. Two hits from a search on the wiki, one is a private page and the other is just some code referencing it.

[CapaJC]

"I have started to focus a great deal more on making what I do usable!"

From your mouth...etc.

That is exactly the zeitgeist we're embracing this release cycle and every one going forward. In the past it's been "get the functionality out there". Now it's "make it not even need documentation".

Case in point, these duration fields on the task table are getting "tooltip" titles to explain what they are this release. Yeah, probably no one is going to go through the entire list of fields to do this for each and every one, but as we work through things I think we'll be putting titles on more and more field lables.

You'll notice not too much whiz-bang new capabilities this release. Sure, Workflow and its ilk are cool, but the primary focus this cycle has absolutely been usability, stability, resource economy, and something else I forget. Stuff under the hood.

Know that your point is very well taken! There won't be an instantaneous night-'n-day improvement, but it'll come.

--J

[#5]

Part of your question was around defining what the feild was used for, this is a place you could use the 'hint' functionalty to give the user a better understanding/definition.