Components are re-usable so you can have many instances of the same component with different settings for the custom fields each one hassettings. You can add/, remove and change custom fields for each component:
| Expand |
|---|
| title | Step1 - STEP 1: In the translator click on config.json to open and edit the custom fields |
|---|
|
 Image AddedClick on config.
|  Image Removedjson Click EDIT to edit the fields
|
| Expand |
|---|
| title | Step STEP 2 - : Add a test field and save. |
|---|
|
 |
| Expand |
|---|
| title | Step STEP 3 - : Commit these changes by pressing the commit button. |
|---|
| 
Image RemovedNOTE: |
 Image Added| Panel |
|---|
| panelIconId | atlassian-warning |
|---|
| panelIcon | :warning: |
|---|
| bgColor | #FFFAE6 |
|---|
| If you do not want to commit these changes, you can change the Using Commit: to |
DEVELOPER, DEVELOPMENT in the next step |
, so it will use the changes made in the translator without a commit. |
|
| Expand |
|---|
| title | Step STEP 4 - : Exit the translator and change the commit to the new one or select Development mode |
|---|
|
 Image RemovedNOTE:  Image AddedClick the ellipses to change the commit. If you do not want to commit
these the changes you made, you can change the Using Commit: to
DEVELOPER DEVELOPMENT so it will use the changes made in the translator without a commit. The custom field you created in the translator, TestField, now shows up.
|
Some more information:
| Expand |
|---|
| title | How does the Lua script get access to the fields |
|---|
|
To get programatic access of the values of the custom fields, there is this api call: | Code Block |
|---|
| local Fields = component.fields(); |
This returns a Lua table with the custom fields and their values for the component. |
...