Improving CSS and HTML structure so that it can be configured if necessary

[PJ]

Hello,

The html part of the field view is something like this:

<tbody>
            <tr>
                <td width="5%">
                    <img src="https://vgjira.xx.de/secure/viewavatar?size=xsmall&avatarId=10812&avatarType=issuetype" title="Server" alt="Server" height="16" width="16">
                </td>
                <td style="word-wrap:break-word" width="10%">
                    <a title="Follow link" href="https://vgjira.xx.de/browse/DPITSRVMGT-71" class="link-title">DPITSRVMGT-71</a>
                </td>
                <td style="word-wrap:break-word" width="75%">
                    <span class="link-summary">vgvmjira (172.20.6.100)</span>
                </td>
                <td width="5%">
                                    <img src="https://vgjira.xx.dehttp://icons.iconarchive.com/icons/icons-land/play-stop-pause/16/Pause-Normal-icon.png" title="Normal" alt="Normal" height="16" width="16">
                                </td>
                <td width="5%">
                                    <img src="https://vgjira.xx.de/images/icons/statuses/closed.png" title="Done" alt="Done" height="16" width="16">
                                </td>
            </tr>
        </tbody>

This is very difficult to adjust. For example, the key is always broken (goes to the next line), since the width is too short. If the <td> had a css class instead of width="10%", then it would have been easy to overwrite it. It would be great if you can remove the hard width fields within TDs and define a css class for it.

If it is too much to do, please increase the 10% width of the TD to 20% and decrease the summary link to 65%.

[William Crighton [CCC]]

I don't see a question here. this looks like A JIRA enhancement request. these work better/our address more rapidly when you create them at jac - jira.atlassian.com.

-wc

[William Crighton [CCC]]

not that I disagree with your sentiments

[PJ]

Thanks William, I'll add it there. Whether you agree or not is not the issue. The FACT is that there is little control over how the field value is structured and shown. What kind of solution is provided to address this issue, is basically not my concern. :)