| 10 | |
| 11 | For example this will add a new field supporting multiple selection called 'environment' with some predefined values: |
| 12 | |
| 13 | {{{#!ini |
| 14 | [ticket-custom] |
| 15 | environment = text |
| 16 | environment.format = list |
| 17 | environment.label = Environment |
| 18 | environment.multiselect = true |
| 19 | environment.options = Android|iPhone|iPad|Windows|Linux|MacOs |
| 20 | environment.order = 2 |
| 21 | }}} |
| 22 | |
| 23 | [[Image(multiselectfield.2.png)]] |
| 24 | |
| 25 | '''Note''': Adding new selection choices is always fine. However, be careful when changing the existing options of a field when there is existing data with the old options. When you view a ticket the ui will only show currently valid options. Any old options will be cleared when the ticket is modified and the field in question has been changed. |
45 | | == Example |
46 | | |
47 | | For example this will add a new field supporting multiple selection called 'environment' with some predefined values: |
48 | | |
49 | | {{{#!ini |
50 | | [ticket-custom] |
51 | | environment = text |
52 | | environment.format = list |
53 | | environment.label = Environment |
54 | | environment.multiselect = true |
55 | | environment.options = Android|iPhone|iPad|Windows|Linux|MacOs |
56 | | environment.order = 2 |
57 | | }}} |
58 | | |
59 | | [[Image(multiselectfield.2.png)]] |
60 | | |
61 | | '''Note''': Adding new selection choices is always fine. However, be careful when changing the existing options of a field when there is existing data with the old options. When you view a ticket the ui will only show currently valid options. Any old options will be cleared when the ticket is modified and the field in question has been changed. |
62 | | |