Bug 1088059

Summary: [RFE] Allow markdown or similar for hinting at styling of known long/wide comment sections
Product: [Community] Bugzilla Reporter: Ian Wienand <iwienand>
Component: User InterfaceAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED UPSTREAM QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: 8ru2u4gz, berrange, jmcdonal, lars, rjoost
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-08 06:18:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
mock-up of a long-comment idea none

Description Ian Wienand 2014-04-16 00:20:44 UTC
Created attachment 886691 [details]
mock-up of a long-comment idea

Description of problem:

Openstack projects tend to have very long log lines; for example some log messages start with

 2014-04-11 18:40:32.805 9578 AUDIT nova.compute.manager [req-80b5a559-fa95-4d0a-919f-4a9ecc47b92a 6c84f979672f44039145387a0e0fb864 bd6159c7f8aa4baba9a33f0b2725e6d1] [instance: 71aa7d02-aca0-490b-abab-3c2
+f2f8df8bf]

before the actual message.  Other common things like qemu command lines can get very long.

There's no real way around this when posting bugs and trying to keep context.  For some examples of bugs that are unreadable without unwrap and a large monitor see bug#1087127, bug#1084833, bug#1086077.

It would be nice if we could deliminate such output with some known plain-text formatting (markdown or similar) and have them styled by bugzilla into something more readable in the browser.

The idea I was thinking was wrapping it in a fixed height/width div with scroll-bars.  See the attached screen-shot for my suggestion

Comment 1 Jason McDonald 2014-04-16 02:12:00 UTC
This is probably not something we'd provide as a Red Hat-specific customization to Bugzilla, as it sounds like a problem that users of other Bugzilla instances would also encounter.  Therefore, I think it would be better to file this RFE with the upstream Bugzilla project at https://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla so that a solution can benefit users of all Bugzilla instances.

Comment 2 Simon Green 2014-04-16 02:21:23 UTC
There is already a bug upstream for it. Only filed 8 and a bit years ago :) This might get some traction now that upstream supports the Preview tab in comments.

Comment 3 Daniel Berrangé 2014-04-16 08:56:50 UTC
The bug shows that someone implemented it as a drop-in extension https://github.com/columbusmonkey/Bugzilla-Extension-Markdown

Is there any mileage in adding this extension to our test instance of bugzilla, so we can see if it does a good enough job for the original reporter's request ?

Comment 4 Simon Green 2014-04-22 01:34:10 UTC
(In reply to Daniel Berrange from comment #3) 
> Is there any mileage in adding this extension to our test instance of
> bugzilla, so we can see if it does a good enough job for the original
> reporter's request ?

IMO. no. There is a GSOC upstream project for this, and I would much rather take this from upstream than use the limited development resources that Red Hat have.

http://www.google-melange.com/gsoc/project/details/google/gsoc2014/koosha/5757334940811264

  -- simon

Comment 5 Jason McDonald 2014-05-08 06:18:54 UTC
Closing this RFE in favour of the upstream RFE.  If this feature makes it into the upstream 4.5/5.0 branch, we'll happily accept it when we move to that branch.

Comment 6 Mr. Beedell, Roke Julian Lockhart (RJLB) 2024-04-07 15:55:52 UTC
A superseding Bugzilla ticket referenced at https://discussion.fedoraproject.org/t/switch-to-bugzilla-harmony/35269/6 may be relevant to this. I'd like to add it directly to this issue, but as https://discussion.fedoraproject.org/t/does-redhat-bugzilla-support-relating-reports-without-dependency/112114 explains, this instance doesn't appear to provide that functionality.