...
https://ecosystem.atlassian.net/browse/FRGE-778
...
Release timeline:
Status | ||
---|---|---|
|
...
Issue 2: Using the Forge custom field on transition screens is impossible. The fields can be assigned to the screen, but they will be rendered as text fields.
https://ecosystem.atlassian.net/browse/FRGE-322
...
Release timeline:
Status | ||
---|---|---|
|
...
Issue 3: Forge custom fields do not support inline editing on issue view.
https://ecosystem.atlassian.net/browse/FRGE-243
...
Release timeline:
Status | ||
---|---|---|
|
...
Issue 4: Forge custom fields do not work on Jira Cloud mobile app.
https://ecosystem.atlassian.net/browse/FRGE-538
Release timeline:
Status | ||
---|---|---|
|
...
Issue 5: Custom fields are rendered as free text fields on bulk update.
https://ecosystem.atlassian.net/browse/FRGE-648
...
Release date:
Status | ||
---|---|---|
|
...
Issue 6: Forge custom fields do not work in Forms.
https://ecosystem.atlassian.net/browse/FRGE-1243
...
Release date:
Status | ||
---|---|---|
|
...
Issue 7: Calculated and Comment fields (Hardcoded fields) won´t appear on screens where the Default or Field tabs are not selected.
...
...
Release timeline:
Status | ||
---|---|---|
|
...
Issue 11: Forge custom fields are not supported by Jira automation of the box
https://ecosystem.atlassian.net/browse/FRGE-1108
...
Release timeline:
Status | ||
---|---|---|
|
Issue 12: Forge custom fields do not work in JWM list view.
https://ecosystem.atlassian.net/browse/FRGE-1114
...
Release timeline:
Status | ||
---|---|---|
|
Issue 13: Using Forge custom fields in other apps doesn’t always work as expected
Status | ||
---|---|---|
|
...