Glossary
From DclWiki
luis miguel music video maui movie sabrine malcolm x movie reviews kelly preston nude video adobe premiere pro 1.5 crack serial here page www http link southern california commercial loans main allo maso pass sado video website vlc player latter days movie download wacker corporation in lansing michigan movie theater microsoft frontpage cracked girls get fucked superram crack rapidos y furiosos 2 oscar movies english to japanese translator movie jaws naked movie star photo counterstrike condition zero server rental kodak movie theater superman movie casting used embroidery machine sitrolgetac
Contents |
Dcl Glossary
I consider it a important issue to have some description of the terminology used in DCL. Useful would be a short sentence, describing what the entity is used for and how it relates to other entities.
Please edit this page and add your definitions.
Account
Organizations or individuals you may provide support or work for.
Action
Actions are used for *time cards* to describe the type of work done during the corrective action phase of a *work order*. The corrective action phase is the time between an issue being reported until it is resolved. You may submit several time cards or ticket resolutions during this phase to be as descriptive as you wish.
Attribute Set
Attribute sets contain actions, priorities, severities, and statuses. You can create as many attribute sets as needed, and can associate them with a product. Each product can have a different attribute set, and is further broken down into work order and ticket attributes.
Department
Departments are used to associate users with different departments within DCL.
ETC
Estimated Time to Complete. This is used to continually adjust the amount of time expected to resolve an issue.
Module
Subentity of Products. These are used to further define an area of a software package. For example, you may have a "~MondoGroupware" product with modules such as E-Mail, Tasks, Notes, Contacts, and Calendar.
Priority
Priorities describe how urgent a particular item is. Used in work orders and tickets.
Product
Products is the list of items that you are tracking in DCL. Products have no direct relation to projects. You may define a project that contains only items for one product, but you may define others that contain several products. DCL does not place any restrictions on these relationships.
Project
Include hierarchal support so sub-projects can be created.
Schedule
This is currently a basic, dumb, unintelligent scheduler that takes all of the work orders for a particular user and schedules them starting on the next business day, 8 hours per day worked, business days only.
Sequence
Related Work Orders carry the same Job Number and incremental sequence numbers. Can be used as a lite project where rollups and hierarchal relationships are not required. You can add a new sequence to a work order from the work order detail.
Status
Statuses indicate the state of an item, usually to determine if it is open, closed, or pending. Several statuses can be added to better describe your work flow.
Ticket
Use for contact with clients. Tickets keep track of the accumulated time automatically from the time the form is opened until it is submitted to the server. You may also use tickets for bugs and such, if you do not want the additional information overhead of the work orders. However, features such as Source Code Control System integration and the Build Manager only work with work orders and/or projects.
Time card
Time taken on a work order to accomplish an action.
View
This is a saved search and may be renamed in the future to reflect that.
Watch
Watches are requests for notification that can be placed on several entities: account work orders and tickets, product work orders and tickets, and projects.
Work Order
Use for tracking history of almost anything: bugs, requests, maintenance, project tasks. Where tickets are primarily used for customer contact (support issues), work orders are meant to track actual work done.
Work Order Types
Work order types represent a high level qualifier to the type of work order. Examples would be: Bug, Enhancement, Configuration, and Data.
