Truncating story summary on new boards is AWFUL

Question

With the "new enhanced" boards, Jira has made it so the summary truncates. It now shows the epic, which I didn't want or care about. Even when I turn off the epic on card, it doesn't change this because I'm using swimlanes.  This makes it super hard to facilitate standup which used to be very straight forward.

Anyone aware of anything that could be done to get the old version back, not have the summary truncated, or get Jira to recognize that they've put out something that doesn't work for everyone??

Ricardo Severo · Answer

When we started increasing the title of Issues with the description of Subsystems and Features, we also noticed this problem here.

After some research, I saw that the bug is still open and has not been resolved.

However, we found a workaround that may most of the users of Google Chrome.

On the Active Sprint (Board) page, open the browser console and include the following script:

// Function to apply the stylefunction applyStyle() {    document.querySelectorAll('.css-1s193e4').forEach((div) => {        div.setAttribute('style', 'max-width: 100%!important');    });}
// Observer to monitor changes in the DOMconst observer = new MutationObserver(() => {    applyStyle();});
// Observer settings: observe changes in children and subtreesobserver.observe(document.body, { childList: true, subtree: true });
// Apply or style initiallyapplyStyle();

You can see that the script above solves the problem, however, it would need to be run every time you enter the page. To do this, you can use a third-party extension so that this script runs automatically every time you access the Board.

Extension: https://violentmonkey.github.io/

Simply install the extension in your browser, include the script and activate it to run on the Board page.

I hope it helps.

Mancy (Manman) Xu · Answer

We met the same issue and the truncated summary are annoying.

Sent a feedback through JIRA. But not sure whether a response will happen.

Thanks!

Martin Trouman_1h1n7a · Answer

I have the same feedback from my organisation - has an official bug been reported on this issue?