Learn all about issues » History » Sprint/Milestone 8
Jan Schulz-Hofen, 04/02/2014 12:40 AM
1 | 2 | Jan Schulz-Hofen | # Learn how to use issues |
---|---|---|---|
2 | 3 | Jan Schulz-Hofen | |
3 | Let's have a look at new issues and introduce the different fields you’ll encounter when creating one. |
||
4 | |||
5 | ## Issue fields |
||
6 | |||
7 | 4 | Jan Schulz-Hofen | {{>toc}} |
8 | |||
9 | 3 | Jan Schulz-Hofen | Issues can be comprised of much more than their four required fields (tracker, subject, status and priority); in fact, there are a ton of useful fields that can really bring your Planio issues to life. Let’s explore them by walking through the process of creating a new issue: |
10 | |||
11 | 8 | Jan Schulz-Hofen | ### The basics: tracker, private, subject, and description |
12 | |||
13 | ![](basic_issue_fields.png) |
||
14 | |||
15 | 3 | Jan Schulz-Hofen | - In the **Tracker** field, select the most appropriate issue tracker category (learn more about trackers here). |
16 | - In the **Private** field, select the check box to indicate that the issue is a private issue. Based on role permissions, a private issue will not be visible to other users, though they may see other issues within the same project. |
||
17 | - In the **Subject** field, enter a brief yet meaningful subject title for the issue. |
||
18 | - In the **Description** field, describe the nature of the issue. |
||
19 | 8 | Jan Schulz-Hofen | |
20 | ### Status, Priority, etc. |
||
21 | |||
22 | 3 | Jan Schulz-Hofen | - In the **Status** field, select the current status of the new issue. |
23 | - In the **Priority** field, select the relative importance of the issue in terms of its priority with other issues. |
||
24 | 6 | Jan Schulz-Hofen | - In the **Assignee** field, select the person to whom the issue should be assigned. The assignee, like a watcher (see below), receives e-mail notifications when an update to the issue occurs. |
25 | - In the **Category** field, select the relevant category for this issue. If you'd like to create a new category, click on the small + icon next to it. |
||
26 | 1 | Jan Schulz-Hofen | - In the **Target milestone** field, select a milestone. Milestones will be displayed alongside their issues on the roadmap of your project. To create a new milestone, click on the + icon next to it. |
27 | 8 | Jan Schulz-Hofen | - In the **Customer company** field, enter the name of an existing company - Planio will actively display all companies that match the name. Click the company when it appears. You can optionally send issue updates to your customers using the customer fields. |
28 | 6 | Jan Schulz-Hofen | - In the **Customer contact** field, select the name of the contact within the company who is associated with the issue. Both companies and contacts can be managed in the Customers tab. |
29 | - In the **Additional customer contacts** field, you can add additional contacts from within the customer company that should receive issue updates in CC. |
||
30 | - In the **Parent task** field, enter a task/issue number or enter keyword text of a task that is a parent to your task - Planio will actively display all tasks that match your text. Click the parent task when it appears. |
||
31 | 7 | Jan Schulz-Hofen | - In the **Start date** field, enter the date when the issue should begin in `yyyy-mm-dd` format or click the icon to launch the mini-calendar. |
32 | - In the **Due date** field, enter the date when the issue is due in `yyyy-mm-dd` format or click the icon to launch the mini-calendar. |
||
33 | 3 | Jan Schulz-Hofen | - In the **Estimated** time field, enter the number of hours to be allocated to the issue. |
34 | - In the **% Done field**, select the current percentile value of the issue’s completion rate. |
||
35 | 6 | Jan Schulz-Hofen | - In the **Files** field, click **Choose Files** to launch the file upload tool. This field is used to attach files that are relevant to the issue. |
36 | - In the **Watchers** field, select the check box(es) to indicate other people within the project team who should be kept aware of the issue via email notifications. |
||
37 | 3 | Jan Schulz-Hofen | - Click **Create** to finalize the issue and view its details; or, |
38 | - Click **Create and continue** to finalise the issue and create an additional issue; or, |
||
39 | - Click **Preview** to view the appearance of the issue’s description (very useful if you have included wiki syntax text in your description). |
||
40 | |||
41 | 5 | Jan Schulz-Hofen | *Please note that based on your role and the enabled modules in your project not all of the above fields may be available.* |
42 | 3 | Jan Schulz-Hofen | |
43 | image |
||
44 | |||
45 | Spotlight: The Status Field |
||
46 | |||
47 | Assigning a status to an issue is pretty straightforward: during issue creation or editing just select the most appropriate option (if you want to define custom statuses or workflows, you may want to check out this FAQ entry). |
||
48 | |||
49 | Status field options, like many fields in Planio, can be customized according to your organization’s needs. For example, in a change management or customer service environment, status options might include new, in progress, resolved, feedback, closed and rejected: |
||
50 | |||
51 | image |
||
52 | |||
53 | Of course if your organization is a bit more laid-back, you may prefer something along these lines… |
||
54 | |||
55 | image |
||
56 | |||
57 | If you’re a PM, using watchers is a great way to keep everyone in your organization in the loop when it comes to project issues. Do you include issue watchers? Tell us how you customize your Planio issues via a Comment below! |
||
58 | |||
59 | Your dedicated Planio blogger, Brian, is currently studying German, reading “The Canterbury Tales,” and (of course) preparing a cheeseburger for dinner. |