Project

Profile

Help

Create new Custom Fields » History » Sprint/Milestone 2

Jan Schulz-Hofen, 05/12/2022 01:32 PM
Change Link values to URL example to Wikipedia

1 1 Ema Raven
# Create new Custom Fields
2
3
Custom fields enable you to personalize functionality in Planio according to your organization’s unique operating procedures. 
4
5
No matter how you operate you can add these fields all over your Planio account so you can always fill out and save the information you need, no matter how individual it may be.
6
7
{{>toc}}
8
9
## Steps for creating new custom fields
10
11
As an administrator of an account, your imagination is the limit when it comes to customizing the Planio experience. Planio supports many different field formats (such as text, integer, list, date etc.), and new fields can be added to many different functionalities (e.g. issues, spent time, users, groups, folders, customer companies etc.). 
12
13
In this example, we will add the issue field "Author" to our blog article tracker.
14
15
### 1. Navigate to the custom fields tile in Administration
16
17
In the top right hand corner you should see your name or your Avatar, which you can click on. This will open up a drop down menu. 
18
19
Once you have clicked on **Administration** you will see a set of tiles with global settings for the account. Click on the tile **Custom fields**.
20
21
{{figure(Navigate to the custom fields tile in Administration)
22
![](custom-field-administration-tile@2x.png)
23
}}
24
25
### 2. Create the new custom field
26
27
You’ll be redirected to the Custom fields page where you will see a list of custom fields that already exist in your account. In the top right hand corner there is a green button **New Custom Field**. Click on it.
28
29
{{figure(Green button for creating a new custom field)
30
![](new-custom-field-hand-button@2x.png)
31
}}
32
33
### Choose where your field should be used
34
35
Here you’ll be asked where your custom field should appear. There is a list of all the functionalities in Planio where you can add you own custom field. For this use case we will create a custom field, which we want to see in our **issues**.
36
37
{{figure(List of objects where custom fields can be added in Planio)
38
![](custom-field-types-with-hand@2x.png)
39
}}
40
41
### Choose the format
42
43
Now you can configure your custom to field to exactly what you need. Start by choosing the format of the field. Each format will need slightly different information and so the fields on this page will update automatically once you have chosen which format you want to use.
44
45
In our use case we have a set list of authors who will be writing the blogs and so we can create a custom field with a list of existing authors to choose from.
46
47
{{figure(Choosing your Custom Field format)
48
![](custom-field-format-choose-with-hand@2x.png)
49
}}
50
51
Remember that the format _cannot be changed_ once your custom field has been saved. Everything else can be edited afterwards though.
52
53
### Give your field a name
54
55
This will be the name that appears in your issues, along side the other fields you usually fill out (Project, Assignee, Due Date etc.)
56
57
{{figure(Giving your Custom Field a name)
58
![](give-your-custom-field-a-name-with-hand@2x.png)
59
}}
60
61
### Add a description
62
63
If you choose to add a description, users will be able to read this text in the issues. A little **?** will show up next to the custom field in the issues and if your users hover over that **?** the description will pop up. You can use this to help your users know what exactly they should be filling out here.
64
65
{{figure(Add a description to the custom field)
66
![](add-a-description-to-custom-field-with-hand@2x.png)
67
}}
68
69
### Fill out your custom field details
70
71
Here you can finally add the values that your users can choose from when filling out that custom field. Here we are adding a list of names of authors. For the list format specifically, remember to add only one value per line. There is a little note under the **Possible values** box in each format type to remind you if this is needed.
72
73
{{figure(Fill out your custom field details)
74
![](fill-out-custom-field-values-with-hand@2x.png)
75
}}
76
77
- Also here you can decide whether users should be able to choose more than one value or not. In our case there can only be one author and so we will _not_ put a tick in the box **Multiple Values**.
78
- Depending on which format you have there also might be display options. For the list format you can either choose a drop down menu or checkboxes for your list.
79
- If you want one particular value to show up in the field automatically, you can enter a value into the **Default value** field. If not you can leave it blank.
80
- **Link values to URL** can be defined for boolean, date, list, integer and text format fields. You can set a URL base so users can finish constructing a destination URL with their entry in the custom field. This can provide context for that piece of information in a different place on the Internet – provided that it has a URL that can be constructed using the information entered. 
81
82 2 Jan Schulz-Hofen
If you entered for example `https://en.wikipedia.org/w/index.php?search=%value%` in the **Link values to URL** field, and someone filled out this new Author custom field with "William Shakespeare", the value would become clickable and a click would lead to the Wikipedia entry for William Shakespeare.
83 1 Ema Raven
84
This field accepts the following URL variables:
85
86
| Variable | Explanation | 
87
| --- | ----- | 
88
| **%value%** | the custom field value | 
89
| **%id%** | ID of the customized object e.g., the ID of the issue | 
90
| **%project_id%** | ID of the project of the customized object if defined |
91
92
### Choose your options for how the custom field will be handled
93
94
Here you can set up further options for how to handle or use the new custom field.
95
96
{{figure(Choose your options for how the custom field will be handled)
97
![](custom-field-required-filter-searchable-with-hand@2x.png)
98
}}
99
100
- In the **Required** field, select the check box to indicate that filling out the field is mandatory. That means that there must be an entry in that field at all times otherwise you won’t be able to save the issue.
101
- In the **Used as a Filter** field, select the check box to indicate that the field can be used in the issue list as a filter. 
102
- In the **Searchable** field, select the check box to indicate that you can use the Planio search function to find this data. This is available for the field types listed below.
103
104
### Choose who it should be visible to
105
106
Who should use this field? Depending on who this field will be relevant for, you may want to restrict who can see or use this field.
107
In this case all users who have access to the tracker and project should be able to see and use the new field.
108
109
{{figure(Choose who the custom field should be visible to)
110
![](custom-field-visibility-with-hand@2x.png)
111
}}
112
113
### Choose what trackers and projects it should appear in
114
115
Here you will decide which trackers and projects this field will be shown in. Just highlight the trackers and projects that you want to see and use your new field in. 
116
117
In our use case, we only want this field to show up in the tracker for "Blog articles" and so we have only highlighted that one. We have blogs in both projects "Rocket Quest" and "Thrust Corp" and so we have highlighted both of these. The tracker "Blog article" is also active in both those projects.
118
119
{{figure(Choose what trackers and projects it should appear in)
120
![](custom-field-trackers-and-projects-with-hand@2x.png)
121
}}
122
123
### Save it!
124
125
Finally you can save it!
126
127
{{figure(Save your field)
128
![](custom-field-save-with-hand@2x.png)
129
}}
130
131
You will be directed back to the list of custom fields and you will see that your new one will have appeared.
132
133
### Use your custom field
134
135
Your new custom field will now be wherever you configured it to be. We created our "Author" field to be used in issues in the project "Thrust Corp" when creating or editing the tracker "Blog article" and there it is:
136
137
{{figure(View of custom field in an issue)
138
![](custom-field-in-issue-with-hand@2x.png)
139
}}
140
141
## Different Formats for different requirements
142
143
As we mentioned earlier, there are many different formats for custom fields. We’ll go through what they are here with some explanation of what they can be used for:
144
145
| Format |    | Explanation | Filterable | Searchable |
146
| --- | -- | ----- | --- | --- |
147
| **List** | → | Users can click on options in a drop-down menu or checklist | ✔ | ✔ |
148
| **Text** | → | Users can type a single line of arbitrary text in this field. | ✔  | ✔ |
149
| **Sprint/Milestone** | → | Users can choose from sprints or milestones that already exist in your account | ✔ | ✘ |
150
| **Longtext** | → | Users can write a multi-line text here. Like the description field in issues the field size can be adjusted | ✔ | ✔ | 
151
| **Link** | → | URL | ✔ | ✘ | 
152
| **Key/Value List** | → | As with the format **List** users can click on options in a drop down menu or checklist. The entries however correspond to a static value, which means the entries can be changed at a later date without losing the old data | ✔ | ✘ |
153
| **Integer** | → | Users can enter a positive or negative whole number | ✔ | ✘ |
154
| **Float** | → | Users can enter whole or rational numbers (e.g. 1.5, 25.8, 7) | ✔ | ✘ |
155
| **File** | → | Users can attach a file (it will also be shown in the "attachments" tab in your project) | ✘ | ✘ |
156
| **Date** | → | Users can enter a date | ✔ | ✘ |
157
| **Boolean** | → | Users can choose either yes or no in the form of either a drop down menu, checklist or radio buttons | ✔ | ✘ |
158
| **User** | → | Users can link other users from the account to the issue. Groups can’t be assigned | ✔ | ✘ |
159
160
## Hints, Tips and Troubleshooting
161
162
→  **I can’t find the Administration area** As only administrators of the account can access the administration area, you won’t see the administration option unless you have administrator rights. You are automatically administrator of the account if you created it. If not you’ll have to ask the administrator of your account to do this for you or give you administrator rights.
163
164
&rarr; **I want to change the order of the custom fields** The order of the custom fields list is the same order that the custom fields will show up in your account. Hover over the three dots in the relevant row and the pointer will become a hand. Grab the row to move it up and down into the order you want your custom fields to be shown. <br>
165
166
&rarr; **My custom field isn’t showing up** If you can’t find a field, it is usually because the wrong tracker or projects have been clicked (or none!). Luckily you can edit and change this whenever you want. Just go to **Administration** &rarr; **Trackers** and add the custom field to the list of ticked boxes &rarr; **Save** or **Administration** &rarr; **Custom fields** and add the tracker and/or projects to the new custom field &rarr; **Save**. <br>
167
168
&rarr; **My custom field entry isn’t showing up in my search** Not all custom field formats can be used as filters or be set as searchable. If the option "Used as a Filter" or "Searchable" doesn’t show up when creating the field, then it can’t be used as a filter or be included in a Planio search. You may however just need to go back and put a tick in the right box. <br>
169
170
&rarr; **I just created a custom field but it’s not included in the custom fields list** If you create custom fields for other aspects in Planio (Wiki pages, Contacts, Spent time etc.) they are grouped into tabs on the custom field page. <br>
171
172
{{figure(Tabs showing the different types of custom fields)
173
![](custom-field-tabs@2x.png)
174
}}
175
176
If you get stuck when adding a custom field to your account, have any other questions, or just want to know more, please don’t hesitate to [contact](https://plan.io/contact/) our super friendly support staff.