|
42
6
|
We are using FogBugz extensively, including the release notes feature. Unfortunately the columns you are presented with in the release notes are static and limited to:
Could this be made customizable so we could include more columns? Especially we would like to include Area and Resolved By in the release notes. |
|||
|
|
4
|
The release notes report is not currently customizable in terms of which fields are shown. We do have a case open to consider adding this functionality. Please up-vote this question if you would like to see this implemented. |
||
|
|
|
0
|
The problem that I have with this is that the default order is: Grouped by milestone and category and then ordered by priority. If I'm doing release notes, it tends to be because I am releasing a particular milestone, so grouping by that is completely pointless. This then leaves a list of release notes that are grouped by category and then ordered by priority - two columns that are not present in the resulting data, which seems like a major no-no to me. When I send these release notes to the client, they have no idea what the ordering is - they would probably believe me if I said that we had ordered the results using random numbers. c |
||
|
|
|
0
|
Glad to find this post - and that others have the same pain. I get asked - what features are in this release. I have several builds in a release\milestone and so put the major.minor.buildnumber in the front of the release note. I use projects for sub projects - which get rolled into the core product - but require I repeat Areas. My specific desires: Release note report as is - Order I need is not milestone, priority - but either date closed or case number decending order, for one or more projects. Why not add release note to the standard customiable filter and put an export feature on that if its not there already. Also clickable heading sort. That way we can determine the WHERE clause, the columns and the sort order. |
||
|
|
