gnats-prs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnatsweb/719: RE: gnatsweb/719: Include Description field in query resul


From: bug-gnats
Subject: gnatsweb/719: RE: gnatsweb/719: Include Description field in query results
Date: Tue, 2 Jan 2007 16:05:02 -0600 (CST)

The following reply was made to PR gnatsweb/719; it has been noted by GNATS.

From: "Craig Senior" <address@hidden>
To: <address@hidden>, <address@hidden>,
        <address@hidden>
Cc: 
Subject: RE: gnatsweb/719: Include Description field in query results
Date: Tue, 2 Jan 2007 16:44:58 -0500

 I noticed that the e-mail notice below included the multitext fields we
 were after.
 
 Interested in sharing your dbconfig file?
 
 >Craig
 >Place du Portage, Ph III, 2A1, Stn 26L
 >W (819) 956-3295
 >F (819) 956-6476
 
 -----Original Message-----
 From: address@hidden [mailto:address@hidden
 
 Sent: January 2, 2007 4:32 PM
 To: address@hidden; address@hidden
 Cc: Craig Senior
 Subject: gnatsweb/719: Include Description field in query results
 
 >Number:         719
 >Category:       gnatsweb
 >Synopsis:       Include Description field in query results
 >Confidential:   no
 >Severity:       non-critical
 >Priority:       low
 >Responsible:    unassigned
 >State:          open
 >Class:          support
 >Submitter-Id:   net
 >Arrival-Date:   Tue Jan 02 15:32:15 -0600 2007
 >Originator:     Craig Senior
 >Release:        Gnatsweb v4.00, Gnats v4.1.0
 >Organization:
 Public Works and Government Services Canada (PWGSC)
 >Environment:
 Not sure
 >Description:
 In our query results, we'd like to include the multitext fields
 Environment, Description, and Organization. After running the query, we
 "pass" copy and paste from the query results into a spreadsheet for a
 little extra formatting.
 
 Currently, we display every PR that matches the query criteria, copy and
 paste the Description field to a Word table. This is a waste of time and
 unworkable as the number of PRs increases.
 
 I tried adding "Description" to the fields in the standard query and
 adding "columns=3DDescription" to the query URL, but it didn't work. It
 seemed to interpret the EOL character in the Description field as
 separate fields, yielding 1233 search results from our 100 records and
 understandably hanging after it processed the field headings.
 
 Any help getting pointed in the right direction would be greatly
 appreciated.
 >How-To-Repeat:
 >Fix:
 >Notify-List:    address@hidden
 >Unformatted:
 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]