en:tickets:task_new
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| en:tickets:task_new [2024/11/25 12:40] – Lada Svobodová | en:tickets:task_new [2026/09/02 14:12] (current) – Milan | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== New task ====== | + | ====== New Ticket |
| + | The basic way to create a ticket is to use the {{: | ||
| + | <WRAP 100%> | ||
| + | <WRAP 500px left> | ||
| + | {{: | ||
| + | </ | ||
| + | The new ticket form has a section collapsed by default, which is marked with a red frame in the image.\\ \\ | ||
| + | The ticket author enters the **Subject** - a concise and descriptive name for the ticket.\\ \\ | ||
| + | **Description** - a space for a detailed description of the ticket, if needed.\\ \\ | ||
| + | **Category** - the default categories can be modified by the administrator in Project Settings.\\ \\ | ||
| + | **Status** - when creating a ticket, the following statuses are available: Draft / Not Started / In Progress / On Hold. | ||
| + | <WRAP tip round> **In the Ticket Kanban**, a ticket can be created using the **+** icon in the header of the Draft / Not Started / In Progress / On Hold columns. A ticket created this way has its **status preselected** according to the column from which the option was launched. | ||
| + | </ | ||
| + | The author specifies the ticket **priority**.\\ \\ | ||
| + | A **Label** can be added if labels have been configured.\\ \\ | ||
| + | **Planned Dates** - the start date is preset to the current date and the end date to +7 days. The author can change these dates.\\ \\ | ||
| + | The ticket can be **localized on a drawing using markers or on the map**. To do this, expand the **Location and Drawings** section using the corresponding icon to display the drawing selection field and map.\\ Drawings must be uploaded under Project Parts and Drawings to enable adding markers to them - LINK. Clicking a selected drawing opens an enlarged view, where markers can be placed by double-clicking the desired locations.\\ On the map, a marker can be placed by clicking the desired location or by entering an address in the Project Location field below the map. | ||
| + | <WRAP tip round> On the **Drawings and Map** page, a ticket can be created by double-clicking the desired location in the relevant drawing or on the map. A ticket created this way has a **pre-filled drawing marker or map location** at the point where the user double-clicked. | ||
| + | </ | ||
| + | **Attachments** - the author can attach photographs, | ||
| + | **Assignees and Approvers** - the author specifies who should handle the ticket and who should approve it, selecting from users who are members of the Project Team. Multiple people can be selected. | ||
| + | <WRAP tip round> By defining **Rules** for Assignees / Approvers, these fields will be filled in automatically when the conditions of the ticket being created are met, with the option to modify them. | ||
| + | </ | ||
| + | <WRAP clear /> | ||
| + | </ | ||
| - | A new task can be created | + | ==== New Related Ticket ==== |
| + | <WRAP 100%> | ||
| + | <WRAP 500px left> | ||
| + | {{: | ||
| + | </ | ||
| + | Buildary provides the option to create a **ticket linked to another ticket**.\\ In the details of an existing ticket, selecting **Create Related Ticket** opens the New Ticket form with a link to the selected ticket. The link can be removed at the end of the form. | ||
| + | <WRAP clear /> | ||
| + | </ | ||
| + | \\ | ||
| + | ===== New Ticket | ||
| + | **1/ Copying the Last Created Ticket** ⇒ the Copy Last Ticket option is available **on the New Ticket page** | ||
| - | **Form with information about the new task** | + | <WRAP 100%> |
| - | <WRAP 100%> < | + | < |
| - | {{:en:tickets:new_task_1.png?600|}} | + | {{:cs:tickets:ukol_kopie.png?direct& |
| - | </ | + | </ |
| - | Fill in the fields in the form and save it by clicking the Save button in the bottom right corner of the form. | + | **2/ Copying a Ticket** ⇒ **in the details |
| - | + | ||
| - | **Copy the last task ** - If you are entering tasks repeatedly, this can save you time. | + | |
| - | + | ||
| - | **Subject ** - Brief description of the task. | + | |
| - | + | ||
| - | **Category** - It is used to categorize tasks into specific areas. | + | |
| - | + | ||
| - | **Status** - List of possible task statuses. | + | |
| - | + | ||
| - | + | ||
| - | **Labels** - You can add your own information to individual tasks in the form of attributes. | + | |
| - | + | ||
| - | **Planned start and finish** - Planned task deadlines. The default value for the start date is today, and for the end date, it is in 7 days. Both dates can be changed. | + | |
| - | + | ||
| - | **Actual Start and Finish** - Actual task deadlines. The date is automatically entered when the ' | + | |
| - | + | ||
| - | **Project Section** - A list containing the hierarchical structure of the construction. In the window, the number of drawings associated with each part of the construction is displayed. The default drawing for the specified part of the construction is always automatically pre-selected in the drawing window. If a part of the construction does not contain any drawings, drawings from a higher level are offered. | + | |
| - | + | ||
| - | **Plan** - You can use the icon to select | + | |
| - | + | ||
| - | **Attachment** - Photos or any other files attached to the task. | + | |
| - | + | ||
| - | **Assigned 1,2** - Select a person from the project team member list who is responsible for solving the task. It is necessary | + | |
| - | + | ||
| - | **Approver** - Select a person from the project team member list who is responsible for reviewing and approving the task. This item is not mandatory. | + | |
| - | + | ||
| - | + | ||
| - | <WRAP info> The actual start date or even the actual end date may be automatically populated depending | + | |
| - | + | ||
| - | + | ||
| - | ====== Creating a new task by copying an existing one ====== | + | |
| - | + | ||
| - | + | ||
| - | You can now create a new task by duplicating an existing one and adjusting only the details that differ between the tasks. | + | |
| - | + | ||
| - | In the task form of the web application, open the menu by clicking the icon with three dots and select **New Task Copy.** | + | |
| - | + | ||
| - | <WRAP 100%> | + | |
| - | <WRAP 600px left> | + | |
| - | Before saving the task, you have the option to select Create a link to the original task. All related tasks can then be found in the task editing view, in the upper right corner next to the three dots. | + | |
| <WRAP clear /> | <WRAP clear /> | ||
| + | </ | ||
| + | \\ | ||
| + | ===== New Ticket from a Project Diary Record ===== | ||
| - | + | Users working with the Project Diary module can create tickets directly from diary records. The Ticket Management module must be enabled for the project.\\ | |
| - | + | **Tickets can be created from records in the Performed Works and Additional Records sections:** | |
| - | + | <WRAP group> | |
| - | + | <WRAP half column> | |
| - | ====== Code Lists - Task Management | + | {{: |
| - | + | </ | |
| - | At the construction level in „Code Lists- Task Management“, | + | <WRAP half column> |
| - | + | {{: | |
| - | <WRAP 100%> | + | </ |
| - | < | + | </ |
| + | \\ | ||
| + | ==== Displaying Related Tickets | ||
| + | <WRAP 100%> | ||
| + | < | ||
| + | {{:cs:tickets:souvisejici_ukoly.png?direct& | ||
| + | </ | ||
| + | Tickets linked to diary records or other related tickets can be displayed in the Ticket List by **adding the Related Tickets column**.\\ \\ | ||
| + | The blue {{: | ||
| + | The orange {{: | ||
| <WRAP clear /> | <WRAP clear /> | ||
| - | + | </ | |
| - | + | \\ | |
| - | <WRAP 100%> | + | |
| - | <WRAP 600px left> | + | |
| - | + | ||
en/tickets/task_new.1732534851.txt.gz · Last modified: 2024/11/25 12:40 by Lada Svobodová
