Autonumbering and titles

[colinc]

Auto numbering is a nice adition but it is hard to use since you loose titles.

This would be much better if it generated the autonumber and leaves the title field free for entry.

Obviously this is more difficult as it involves adding a new field into all element types but it would make generating readable documentation very straightforward.

Colin

[thomaskilian]

I once suggested that the cursor should simply be placed after the generated number. I still would like to see that for ALL kinds of autonumber fields

[mikewhit]

Or better still, autonumber by template which would allow you to specify where you wanted the number - could then also allow you to add hierarchies and (e.g.) package identifiers ... ?

[thomaskilian]

Yeah.  I could live with simple templates which are already used for Tags.

[mikewhit]

My interest was in being able to generate hierarchical autonumbered requirements numbering e.g. 4.6.4.11

A bit of thought into templatised autonumbering would give a really powerful facility - if you're turned on by that kind of thing ;-)

But even a simple mechanism would, it seems, prove a big plus from the current feature.

[allenmarshall]

Perhaps the number could be user supplied as a discretionary property.  We have a set of reqs. that are already nunbered which have been accepted by our client.  I would rather not have solely autonumbering for this case.  As a matter of fact, the numbers reflect Use Case #s which further confounds the situation.   Does anybody know if the numbering feature is planned for a future version?

[mikewhit]

Some time ago I asked about having more control over autonumbering - e.g. being able to specify a template or hierarchy or 'format string', but heard nothing further.

http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=suggestions;action=display;num=1097072326;start=3#3

[thomaskilian]

A pity. These are probably easy to implement and give the user a lot more flexibility. Obviously only a few users seem to see that