Configuration Limits
| Setting | Limit |
|---|---|
| Configuration name | Max 250 characters |
| Description | Max 5,000 characters |
| Display JQL | Max 1,000 characters |
| Configuration size | Max 230 KB (total serialized size) |
| Link buttons | Max 5 per panel; label max 60 characters, URL max 2,000 characters |
| Date and date-time formats | Max 64 characters |
| Translations | Max 10 languages per panel |
Data Limits
| Setting | Limit | Default |
|---|---|---|
| Linked requests loaded per panel | 50 | - |
| Rows Per Page | 1-100 | 10 |
| Table fields per configuration | Max 50 | - |
| Display fields per configuration | Max 50 | - |
Issue link types per configuration (linkTypes) |
Max 100 | - |
Caching
Customer Portal Fields Panel uses a 3-level caching strategy to optimize performance:
| Level | TTL | Purpose |
|---|---|---|
| KVS (Forge Storage, server-side) | Persistent | Configuration data, module settings |
| IndexedDB (browser) | 4 hours | Cached configuration lookups |
| localStorage (browser) | Session | Quick access for active configurations |
Cache Invalidation
- Saving a configuration immediately invalidates the server-side cache
- Browser caches refresh after the TTL expires
- Users can force a refresh by hard-reloading the page (Ctrl/Cmd + Shift + R)
Performance Tips
Optimize Field Selection
- Select only the table fields you actually display - each field adds to the data transfer
- Use display fields sparingly - they add additional field rendering per panel
Reduce Panel Count
- Each visible panel makes independent API calls
- Consider combining related information into a single panel with sections
- Use conditional display (Display JQL) to prevent unnecessary panel rendering
- Disable panels that are no longer needed rather than leaving them active
Next Steps
- Configuration Basics - Panel setup
- Data Sources - Configure queries and limits
- FAQ - Performance troubleshooting
- Permissions Reference - Security constraints

