-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
- When looking at queues, issues with Summary field values that contain strings longer than 26 characters will not wrap
- Would be a problem for use cases where monitoring tools are configured to send alert emails to Jira Service Desk and service/server hostnames need to be displayed in the queue
- The Summary field "bleeds" into other columns
- In the below example, the Description field displays within the column as expected, but the Summary field does not:
Steps to Reproduce
- Create an issue where the Summary field contains a continuous string of characters longer than 26 characters
- View the issue in a queue
Expected Results
The Summary field text wraps neatly within the Summary column.
Actual Results
The text does not wrap and "bleeds" into the proceeding column(s) - see the screenshot in the "Issue Summary".
Workaround
- Avoid the use of words/strings that are longer than 26 characters
- Use spaces in between words
- Increase the width of the browser window/tab
- relates to
-
JSDCLOUD-7842 Add the ability to resize queue columns
- Gathering Interest
[JSDCLOUD-8678] Queues: Summary field label/field does not wrap when the page is resized
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Long Term Backlog [ 12073 ] | New: Closed [ 6 ] |
| Labels | New: timeout-bulk-close202012 |
| Support reference count | New: 1 |
| Status | Original: Needs Triage [ 10030 ] | New: Long Term Backlog [ 12073 ] |
| Link | New: This issue relates to JSDCLOUD-7842 [ JSDCLOUD-7842 ] |
| Attachment | Original: Screenshot 2019-12-05 at 15.47.32.png [ 381474 ] |
| Attachment | Original: Screenshot 2019-12-05 at 15.46.04.png [ 381473 ] |
| Attachment | Original: Screenshot 2019-12-05 at 15.45.55.png [ 381472 ] |
| Description |
Original:
h3. Issue Summary
* When looking at queues, issues with Summary field values that contain strings longer than 26 characters will not wrap * Would be a problem for use cases where monitoring tools are configured to send alert emails to Jira Service Desk and service/server hostnames need to be displayed in the queue * The Summary field "bleeds" into other columns * In the below example, the Description field displays within the column as expected, but the Summary field does not: h3. Steps to Reproduce # Create an issue where the Summary field contains a continuous string of characters longer than 26 characters # View the issue in a queue h3. Expected Results The Summary field text wraps neatly within the Summary column. h3. Actual Results The text does not wrap and "bleeds" into the proceeding column(s). h3. Workaround * Avoid the use of words/strings that are longer than 26 characters * Use spaces in between words * Increase the width of the browser window/tab |
New:
h3. Issue Summary
* When looking at queues, issues with Summary field values that contain strings longer than 26 characters will not wrap * Would be a problem for use cases where monitoring tools are configured to send alert emails to Jira Service Desk and service/server hostnames need to be displayed in the queue * The Summary field "bleeds" into other columns * In the below example, the Description field displays within the column as expected, but the Summary field does not: !Screenshot 2019-12-05 at 16.10.51.png|thumbnail! h3. Steps to Reproduce # Create an issue where the Summary field contains a continuous string of characters longer than 26 characters # View the issue in a queue h3. Expected Results The Summary field text wraps neatly within the Summary column. h3. Actual Results The text does not wrap and "bleeds" into the proceeding column(s) - see the screenshot in the "Issue Summary". h3. Workaround * Avoid the use of words/strings that are longer than 26 characters * Use spaces in between words * Increase the width of the browser window/tab !Screenshot 2019-12-05 at 16.11.03.png|thumbnail! |
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com.
Thank you again for providing valuable feedback to our team!
Jira Service Management Cloud team