User Tools
en:handbuch:kapitel_2:2.12.02_aenderungsantrag
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:handbuch:kapitel_2:2.12.02_aenderungsantrag [2009/09/21 17:23] 192.168.0.76 |
en:handbuch:kapitel_2:2.12.02_aenderungsantrag [2019/10/25 14:11] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| - | With this component, change requests (extensions, reductions, troubleshooting, ...) for selected modules can be entered and recorded. The change requests contain et al., following information: type, recording, rating, scheduled period and assignment to project data. | + | With the component **Tickets**, change requests (extensions, reductions, troubleshooting, ...) for selected modules can be entered and recorded. The change requests contain the following information: type, recording, rating, scheduled period and assignment to project data, etc. |
| - | **Tip:** For more on this subject see chapter [[handbuch:kapitel_3:3.08_produktdokumentation_und_ticketsystem_produktmanagement|3.08 Product Management]] | + | **Tip:** For more on this subject see chapter [[en:handbuch:kapitel_3:3.08_produktdokumentation_und_ticketsystem_produktmanagement|3.08 Product Management]] |
| - | {{:handbuch:kapitel_2:ticket1.gif?direct}} | + | {{:en:handbuch:kapitel_2:ticket_extending1.png|}} |
| The form contains the following elements: | The form contains the following elements: | ||
| Line 13: | Line 13: | ||
| On the "Master Data" tab: | On the "Master Data" tab: | ||
| - | * **Number:** In the number field, a unique number is assigned to the ticket by the system. This number is definable through the number range (autonumbers) function in the administration menu (see also administration guide). | + | * **Id:** In the number field, a unique number is assigned to the ticket by the system. This number is definable through the number range (autonumbers) function in the administration menu (see also administration guide). |
| * **Component:** In the field component, the assigned module for the ticket is entered. If the ticket is generated from the module structure, the system transfers the assigned module automatically. The components are administered in the [[2.12.01_komponente|Component]] form. | * **Component:** In the field component, the assigned module for the ticket is entered. If the ticket is generated from the module structure, the system transfers the assigned module automatically. The components are administered in the [[2.12.01_komponente|Component]] form. | ||
| * **Name:** This field labels the ticket in short form with a maximum of 50 characters. | * **Name:** This field labels the ticket in short form with a maximum of 50 characters. | ||
| * **Description:** This field labels the ticket as long text with a maximum of 255 characters. | * **Description:** This field labels the ticket as long text with a maximum of 255 characters. | ||
| * **Keywords:** Defined keywords of the component can be assigned here. These keywords can be defined in the Product Management - Keywords menu. | * **Keywords:** Defined keywords of the component can be assigned here. These keywords can be defined in the Product Management - Keywords menu. | ||
| - | * **Type:** This field classifies the ticket. In the standard version the drop-down box is populated with the entries extentions, errors, testing and improvement (Erweiterung, Fehler, Testen und Verbesserung). | + | * **Type:** This field classifies the ticket. In the standard version the drop-down box is populated with the entries extensions, errors, testing and improvement (Erweiterung, Fehler, Testen und Verbesserung). |
| * **Target Version:** In this field, the target version for the change can be assigned. The versions are assigned to the components. | * **Target Version:** In this field, the target version for the change can be assigned. The versions are assigned to the components. | ||
| * **Created: By, On:** These fields specify the date of creating the ticket and the employee who created the ticket. The employees can be defined and modified in the [[2.01.24_basic_-_mitarbeiter|Employee]] form. | * **Created: By, On:** These fields specify the date of creating the ticket and the employee who created the ticket. The employees can be defined and modified in the [[2.01.24_basic_-_mitarbeiter|Employee]] form. | ||
| Line 28: | Line 28: | ||
| * **Customer:** This drop-down box is set when the ticket is defined for the customer. The customers can be defined and modified in the [[2.01.13_basic_-_kontakt|Contacts]] (with the contact type "customer") form. | * **Customer:** This drop-down box is set when the ticket is defined for the customer. The customers can be defined and modified in the [[2.01.13_basic_-_kontakt|Contacts]] (with the contact type "customer") form. | ||
| - | {{:handbuch:kapitel_2:ticket2.gif?nolink}} | + | {{:en:handbuch:kapitel_2:ticket_extending2.png|}} |
| On the "Misc" tab: | On the "Misc" tab: | ||
| - | * **Versions: Found, First Occurance, Fixed:** Specifies with tickets (with troubleshooting in particular) when and with which version the error has been found, since when the error exists and when the error has been corrected. | + | * **Versions: Found, First Occurrence, Fixed:** Specifies with tickets (with troubleshooting in particular) when and with which version the error has been found, since when the error exists and when the error has been corrected. |
| * **Developer, Tester :** | * **Developer, Tester :** | ||
| - | * **Estimated Time/Effort, Estimated Costs and Actual Costs:** Arguments for extentions and improvements for the implementation/realisation can be entered here. | + | * **Estimated Time/Effort, Estimated Costs and Actual Costs:** Arguments for extensions and improvements for the implementation/realisation can be entered here. |
| * **Projects:** In the projects field the ticket can be assigned to one or more projects here. The projects can be defined and modified in the [[2.02.02_projekt|Projects]] form. | * **Projects:** In the projects field the ticket can be assigned to one or more projects here. The projects can be defined and modified in the [[2.02.02_projekt|Projects]] form. | ||
| * **Jobs:** In the jobs field the ticket can be assigned to one or more projects here. The jobs can be defined and modified in the [[2.02.04_arbeitspaket|Jobs]] form. | * **Jobs:** In the jobs field the ticket can be assigned to one or more projects here. The jobs can be defined and modified in the [[2.02.04_arbeitspaket|Jobs]] form. | ||
| * **Related Tickets:** Links to similar tickets/change requests can be stored here. | * **Related Tickets:** Links to similar tickets/change requests can be stored here. | ||
| * **Scheduled Period (from/to):** These fields specify the validity of the ticket. Only the date "from" (processing from this point) or "to" (completion up to this point) can be filled. | * **Scheduled Period (from/to):** These fields specify the validity of the ticket. Only the date "from" (processing from this point) or "to" (completion up to this point) can be filled. | ||
| + | |||
| + | {{:en:handbuch:kapitel_2:ticket_extending3.png|}} | ||
| On the "Comments" tab: | On the "Comments" tab: | ||
| Line 46: | Line 48: | ||
| The document type contains the following actions: | The document type contains the following actions: | ||
| - | * **Set State:** Using this action, the status of the tickets can be changed. For several status changes, a comment is obligatory. All status changes are protocolled in the comment tab. | + | * **Set State:** Using this action, the status of the tickets can be changed. For several status changes, a comment is obligatory. All status changes are protocoled in the comment tab. |
en/handbuch/kapitel_2/2.12.02_aenderungsantrag.1253546623.txt.gz · Last modified: 2019/10/25 14:09 (external edit)
