Does the app support team-managed spaces?

No. The current release supports company-managed Jira Service Management spaces.

Are custom fields supported?

No. The current supported fields are Summary, Description, Priority, Due date, and Comment. Custom field support is planned for a future release.

Can customers edit closed requests?

Portal Edits does not override Jira or JSM restrictions on closed, resolved, archived, or otherwise non-editable requests. Use your approved Jira workflow process first if a request must be reopened.

Can unlicensed portal users use the app?

The portal module supports customer and unlicensed access contexts where the request, participant, space, and Jira rules allow it. Test with an unlicensed account if this is important to your service model.

Why is Summary different?

Summary must have a value in Jira, so Hide when empty is not available for Summary.

Why is there no rich-text toolbar?

The current native Forge UI Kit portal module supports standard text areas. The tested rich-text editor component is not supported in this extension point. Rich text would require a larger Custom UI/editor architecture.

Why is an action missing?

Check enabled state, request type, participant permission, JQL, request access, space type, and Jira restrictions.

Why did an update fail?

The field may be unavailable on the request type, blocked by Jira configuration, rejected by workflow rules, invalid, or affected by a permission or service error.

Why did the internal note fail while the request updated?

Internal comments require Jira to accept the app-authorized operation and the space permissions. The OAuth scope alone does not guarantee success.

Does the app store request content?