-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Minor
-
Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals.
Steps to Reproduce
- Create a Request with >100 Fields.
- Try to edit it in Slack.
- See this Error appear in the Modal:
Something went wrong.
⚠ An error occurred while loading the issue details.
Share this error ID with support: <error id>
Expected Results
The Modal loads correctly and the issue is editable.
Actual Results
The Modal fails to load and an error is returned.
Suggestion
Have the Modal only load up to 98 Fields, while using the first 2 to warn the User that not all Fields are present, rather than just erroring out.
Workaround
Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens.
- mentioned in
-
Page Failed to load
[JSDCLOUD-14345] JSM Chat Slack: Having over 100 Fields makes Requests uneditable in Slack due to error.
Remote Link | New: This issue links to "Page (Confluence)" [ 934762 ] |
Support reference count | Original: 1 | New: 2 |
Status | Original: Needs Triage [ 10030 ] | New: Short Term Backlog [ 12074 ] |
Support reference count | New: 1 |
Description |
Original:
h3. Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals. h3. Steps to Reproduce # Create a Request with >100 Fields. # Try to edit it in Slack. # See this Error appear in the Modal: {quote} *Something went wrong.* ⚠ An error occurred while loading the issue details. Share this error ID with support: <error id> {quote} h3. Expected Results The Modal loads correctly and the issue is editable. h3. Actual Results The Modal fails to load and an error is returned. *+Suggestion+* Have the Modal only load up to 98 Fields, then use the last 2 to warn the User that not all Fields are present, rather than just erroring out. h3. Workaround Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens. |
New:
h3. Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals. h3. Steps to Reproduce # Create a Request with >100 Fields. # Try to edit it in Slack. # See this Error appear in the Modal: {quote} *Something went wrong.* ⚠ An error occurred while loading the issue details. Share this error ID with support: <error id> {quote} h3. Expected Results The Modal loads correctly and the issue is editable. h3. Actual Results The Modal fails to load and an error is returned. *+Suggestion+* Have the Modal only load up to 98 Fields, while using the first 2 to warn the User that not all Fields are present, rather than just erroring out. h3. Workaround Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens. |
Description |
Original:
h3. Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals. h3. Steps to Reproduce # Create a Request with >100 Fields. # Try to edit it in Slack. h3. Expected Results The Modal loads correctly. h3. Actual Results The Modal fails to load and an error is returned. *+Suggestion+* Have the Modal only load up to 98 Fields, then use the last 2 to warn the User that not all Fields are present, rather than just erroring out. h3. Workaround Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens. |
New:
h3. Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals. h3. Steps to Reproduce # Create a Request with >100 Fields. # Try to edit it in Slack. # See this Error appear in the Modal: {quote} *Something went wrong.* ⚠ An error occurred while loading the issue details. Share this error ID with support: <error id> {quote} h3. Expected Results The Modal loads correctly and the issue is editable. h3. Actual Results The Modal fails to load and an error is returned. *+Suggestion+* Have the Modal only load up to 98 Fields, then use the last 2 to warn the User that not all Fields are present, rather than just erroring out. h3. Workaround Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens. |
Description |
Original:
h3. Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals. h3. Steps to Reproduce # Create a Request with >100 Fields. # Try to edit it in Slack. h3. Expected Results The Modal loads correctly. h3. Actual Results The Modal fails to load and an error is returned. h3. Workaround Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens. *+Suggestion+* Have the Modal only load up to 98 Fields, then use the last 2 to warn the User that not all Fields are present, rather than just erroring out. |
New:
h3. Issue Summary
If a Request has >100 Fields and a User tries to Edit it in Slack, the Modal fails to render the Fields because there's a 100 entry limit on Slack Modals. h3. Steps to Reproduce # Create a Request with >100 Fields. # Try to edit it in Slack. h3. Expected Results The Modal loads correctly. h3. Actual Results The Modal fails to load and an error is returned. *+Suggestion+* Have the Modal only load up to 98 Fields, then use the last 2 to warn the User that not all Fields are present, rather than just erroring out. h3. Workaround Reduce the number of Fields to fewer than 100. Be mindful of system fields like Shared With which can't be removed and won't be listed on Screens. |