Yes, Dynamic Forms for Jira supports using IP allowlisting. See Atlassian documentation for details and instructions.
IP list:
Back to App page
18.236.52.165/32
34.215.254.205/32
35.160.6.102/32
52.43.192.52/32
52.89.100.78/32
54.190.195.254/32
54.214.155.219/32
54.218.196.28/32
If you set a field configuration to Hide or Required in native Jira settings you can use some actions and conditions related to these fields. An affected field is a field you add an action to and condition field is a field your condition refers to.
See tables below for details:
| Affected field action | Valid configuration |
|---|---|
| Show field | - |
| Set value |  |
| Required | - |
| Read only | - |
| Default value | |
| Condition field operator (examples) | Valid configuration |
|---|---|
| Is empty | - |
| Is not empty | |
| Contains/equals | |
| Does not contain/equal | |
If a field is set as hidden in native Jira no actions and conditions related to this field will work.
Your Description field is set as required in native Jira settings and you set an action for this field - Read only. A field can’t be both read-only and required therefore Dynamic Forms for Jira will return an error.
An evaluation loop occurs when two rules have overlapping conditions, making the create process unable to complete. The administrator is able to detect which fields cause this by checking the browser console.
The conflicting conditions warning will be displayed only when two fields are directly connected. The loop may occur, for example, between three fields A>B>C>A and then no warning will be displayed. If such a loop is created, then it will only be visible in the create issue window.
If an instance has two applications that affect fields on issues, only the app installed first will function properly.
