This page describes the various fields that you see on a ticket.

STATUS

RESOLUTION
The Status field indicates the current state of a ticket. Only certain status transitions are allowed. The Resolution field indicates what happened to this ticket.
Open Tickets
UNCONFIRMED
This ticket has recently been added to the database. Nobody has confirmed that this ticket is valid.
In Queue
This ticket is valid and has recently been filed. Tickets in this state become are ready to be picked by processing team.
WIP
This ticket is in work in progress (WIP) and not yet resolved, but is assigned to the proper person who is working on the ticket.
No resolution yet. All tickets which are in one of these "open" states have no resolution set.
Closed Tickets
Dev Closed
This ticket is completed by the assigned person and submitted to cordinator for furthur processing.
RESOLVED
A resolution has been performed, and it is awaiting verification by QA / Customer. From here tickets are either reopened and given some open status, or are verified by QA and marked VERIFIED.
QAPassedByCustomer
QA / Customer has looked at the ticket and the resolution and agrees that the appropriate resolution has been taken. This is the final status for tickets.
FIXED
A fix for this ticket is checked into the tree and tested.
QUERY
After evaluation it is found to be clarification only by customer. No changes done.
DATA ISSUE
After evaluation only data discrepency / in completness found. Based on advise / data correction system is running fine.
INVALID
The problem described is not a ticket.
WONTFIX
The problem described is a ticket which will never be fixed.
DUPLICATE
The problem is a duplicate of an existing ticket. When a ticket is marked as a DUPLICATE, you will see which ticket it is a duplicate of, next to the resolution.
WORKSFORME
All attempts at reproducing this ticket were futile, and reading the code produces no clues as to why the described behavior would occur. If more information appears later, the ticket can be reopened.

Other Fields

Alias
A short, unique name assigned to a ticket in order to assist with looking it up and referring to it in other places in Maventic Support Portal.
Application Layer
Application layer which is the source of this bug
Assignee
The person in charge of resolving the ticket.
Blocks
This ticket must be resolved before the tickets listed in this field can be resolved.
CC
Users who may not have a direct role to play on this ticket, but who are interested in its progress.
Changed
When this ticket was last updated.
Classification
Tickets are categorised into Classifications, Products and Components. classifications is the top-level categorisation.
Comment
Tickets have comments added to them by Maventic Support Portal users. You can search for some text in those comments.
Component
Components are second-level categories; each belongs to a particular Product. Select a Product to narrow down this list.
Content
This is a field available in searches that does a Google-like 'full-text' search on the Summary and Comment fields.
Creation date
When the ticket was filed.
Depends on
The tickets listed here must be resolved before this ticket can be resolved.
Hardware
The hardware platform the ticket was observed on. Note: When searching, selecting the option "All" only finds tickets whose value for this field is literally the word "All".
Importance
The importance of a ticket is described as the combination of its Priority and Severity.
Keywords
You can add keywords from a defined list to tickets, in order to easily identify and group them.
Originator email
Email ID of the person originally reported the bug. This person may not be part of user group.
OS
The operating system the ticket was observed on. Note: When searching, selecting the option "All" only finds tickets whose value for this field is literally the word "All".
Priority
Engineers prioritize their tickets using this field.
Product
Tickets are categorised into Products and Components.
QA Contact
The person responsible for confirming this ticket if it is unconfirmed, and for verifying the fix once the ticket has been resolved.
Reporter
The person who filed this ticket.
See Also
This allows you to refer to tickets in other installations. You can enter a URL to a ticket in the 'Add Ticket URLs' field to note that that ticket is related to this one. You can enter multiple URLs at once by separating them with a comma.

You should normally use this field to refer to tickets in other installations. For tickets in this installation, it is better to use the Depends on and Blocks fields.

Severity
How severe the ticket is, or whether it's an enhancement.
Sub Componemt
Sub Component
Summary
The ticket summary is a short sentence which succinctly describes what the ticket is about.
Tags
Unlike Keywords which are global and visible by all users, Tags are personal and can only be viewed and edited by their author. Editing them won't send any notification to other users. Use them to tag and keep track of tickets.
Target Milestone
The Target Milestone field is used to define when the engineer the ticket is assigned to expects to fix it.
Ticket ID
The numeric id of a ticket, unique within this entire installation of Maventic Support Portal.
Transport No
Please specify the SAP transport ID for this ticket.
URL
Tickets can have a URL associated with them - for example, a pointer to a web site where the problem is seen.
Version
The version field defines the version of the software the ticket was found in.
Votes
Some tickets can be voted for, and you can limit your search to tickets with more than a certain number of votes.
Whiteboard
Each ticket has a free-form single line text entry box for adding tags and status information.