Edgewall Software
Modify

Opened 15 years ago

Last modified 5 years ago

#8088 new enhancement

Allow a WikiFormatted Custom Ticket Field Parse Through the Wiki Engine in Reports, without Using 'Magic' Column Name

Reported by: anonymous Owned by:
Priority: low Milestone: next-major-releases
Component: report system Version: 0.11.3
Severity: minor Keywords: wiki custom bitesized
Cc: Ryan J Ollos, franz.mayer@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Now that #1791 is provided in version 0.11.3, there should be a way to show a wiki formatted custom field in reports with a user defined column name. Currently WikiFormatting of a custom field shows in report only when "AS description" is used in SQL.

Attachments (1)

trac-wiki-oneliner.patch (2.1 KB ) - added by nexus@… 15 years ago.
wiki_to_onliner patch for custom reports

Download all attachments as: .zip

Change History (14)

comment:1 by Christian Boos, 15 years ago

Suggestion?

comment:2 by Christian Boos, 15 years ago

Milestone: 1.0
Priority: highlow
Severity: normalminor

by nexus@…, 15 years ago

Attachment: trac-wiki-oneliner.patch added

wiki_to_onliner patch for custom reports

comment:3 by nexus@…, 15 years ago

I was in need of creating URLs to our external wiki documentation system from custom reports. My solution was to simply add syntax which enables wiki_to_oneliner in columns which begins with '~'. You can try out my patch and see wheter it helps you

comment:4 by Remy Blank, 15 years ago

Milestone: 1.00.12
Owner: set to Remy Blank

I'll grab that.

comment:5 by Remy Blank, 15 years ago

Keywords: needinfo added

I was going to integrate this patch (better late than never :-), but ~ is not a valid character in an SQL identifer. It seems that we're stuck with letters, digits and the underscore. And adding more underscores as prefix or suffix isn't really an option.

So I'm looking for ideas how to flag a column for:

  • Wiki formatting as a one-liner
  • Full wiki formatting (like the description)

Ideally, one should be able to combine this with the row_ syntax for adding a line break after the column, and the _row_ syntax for a full-width column.

Ideas?

comment:6 by Remy Blank, 15 years ago

Milestone: 0.120.12.1

No new ideas, re-targeting.

comment:7 by Christian Boos, 14 years ago

Keywords: needinfo removed

What about __wiki__col? And maybe even __wikihtml__col and __wikioneliner__col.

comment:8 by Remy Blank, 14 years ago

Keywords: bitesized added

comment:9 by Christian Boos, 14 years ago

Milestone: next-minor-0.12.xnext-major-0.1X

comment:10 by Remy Blank, 12 years ago

Owner: Remy Blank removed

Refocusing.

comment:11 by Christian Boos, 11 years ago

#10955 was closed as duplicate.

comment:12 by Ryan J Ollos, 10 years ago

Cc: Ryan J Ollos added

comment:13 by franz.mayer@…, 10 years ago

Cc: franz.mayer@… added

In mailing list entries Trac Development > Error in Wiki-Page "Custom Reports Configuration" and Trac Users > Wiki Column in an ordinary table I had asked about that very feature.

As suggestion I would do it like other "Custom formatting columns" (see TracReports#Customformattingcolumns) and trigger formatting a DB column as wiki by naming it as __wiki__ (and maybe __wikioneline__ for full row).

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.