Wiki TODO_Feature_Requests page doubt and suggestions

[worm]

Hi, people!

Doubt:
Anyone with a better understanding of contents of page TODO_Feature_Requests from the Wiki, could please explain where those code numbers beside every "todo" item come from?

I've checked the Ingres bug tracking system, but didn't find any related numbers there.

Suggestion:

1. If that number is related to any accessible URL (GET) giving more info on the "todo", maybe It could be interesting transforming that number into a link to "more info". Maybe it could be wise to implement a simple "macro" ("template" in Mediawiki talk) receiving the number as a parameter em converting it into a link.
2. Most of the content of this page come from other wiki pages where the same list of "todos" exist. Again, a template could be created and included/referenced on both pages: the topic page (e.g.: SQL_Enhancements) and the TODO comprehensive page. Each list would be edited only once, and instantly updating every page that references the template.

Samples:
Small template to link to more info (template page: TodoMoreInfoTmpl):

[http://moreinfo.ingres.com/givemoreinfo.cgi?number={{{number}}} {{{number}}}]

Template with some "todos" for "SQL Enhancements" topic (template page: SQL_Enhancements_Tmpl):

{|
|- valign="top" align="left" 
! width="100"|'''DBMS Feature'''
! '''Description'''
|- valign="top"
|'''SQL Enhancements'''
|'''Extend Ingres SQL support to provide user requested functionality, implement SQL-2003 non-core functionality and support a broader range of applications'''
|- valign="top"
|{{TodoMoreInfoTmpl|number=108795}}
| update from aggregate 
|-
|{{TodoMoreInfoTmpl|number=110960}}
| Order by in subselect 
|-
|{{TodoMoreInfoTmpl|number=112485}}
| SQL -s (Completely) Silent Enhancement request. 
|}

SQL Enhancements page includes the template:

{{SQL_Enhancements_Tmpl}}

TODO Feature Requests page also includes the SQL_Enhancements_Tmpl and others to compose a comprehensive TODO page:

{{SQL_Enhancements_Tmpl}}
...
{{Other_Tmpl}}

[kschendel]

Those are bug / enhancement numbers from the old (internal) Ingres bug tracking system.

As far as I know, the issue of how to integrate the internal and external bug trackers, and how to tag projects with an enhancement number, is still unresolved. I've heard a few ideas but I don't know how it will end up.

For the moment, those numbers can be treated as magic numbers assigned by Ingres Engineering, but that is not viable long term.

[teresa]

For the most part those are Service Desk Enhancement numbers as the enhancements were typically logged as part of an issue raised with Ingres Support.

There is a bit more info in the actual Service Desk issue that isn't available in the brief description added on this page by the person who transferred the data externally.

I'll discuss with the page owner and see how we can best move this forward and provide more useful detail on the actual feature request itself.

If an actual project has been started for a particular feature (with project page, dds, etc.) I try to remember to add a hyperlink from this number to the project page but it is hit or miss as I don't own the content on the page.

I'll also discuss with the page owner better ways to organize the info, including templates, and avoid the duplication of information/multiple ways.

Regards,
Teresa

[kschendel]

Are they SD numbers or bugs numbers? or are the two sync'ed in some manner? (not that it really matters hugely.)

[denjo02]

They are SD numbers. Pity they're in the same range as bug numbers...

[teresa]

As John says they are really SD numbers. When the project page is created, I try to ensure both the bug number and the SD number are listed on the project page but I'm sure I don't catch everything

[worm]

Originally Posted by teresa

As John says they are really SD numbers. When the project page is created, I try to ensure both the bug number and the SD number are listed on the project page but I'm sure I don't catch everything ;)

Thanks for your reply, and just send a message if any help is needed in case somebody comes up with a viable solution (such as a magic "more info" GET-like URL), because it would reduce a lot of tedious and error prone effort.