Known Issues

Limitation	Why	Workaround
No scripted workflow conditions	Forge evaluates conditions as a fixed Jira expression, so they can't run a script	Use a validator to block the transition
Scripted fields compute on view only	Jira asks for the value when it renders the field	Values aren't recalculated when work items change through the REST API or automation; keep that in mind before relying on them in reports
One Script Toolkit panel per location	Forge modules are fixed when the app is deployed	Several fragments in one place appear as tabs
Fragment previews run as the admin	The preview uses your Jira permissions	Check with a test account for permission-sensitive fragments
Scheduled jobs are checked every 5 minutes	Forge's shortest schedule is five minutes	Use a web trigger for anything that must react immediately
Scripted fields have 5 seconds	A slow field stalls the work item view	Keep field scripts to one or two Jira calls
No Node.js APIs in backend scripts	Scripts run in an isolated sandbox	Use requestJira, fetch and secrets

Found something else? Contact Yamuno support.