customizing the requirement fields

[karomann]

Hi,
is there any way to change the possible values for the priority and difficulty fields of the requirement 'class'?

[thomaskilian]

It looks like these are hard coded. I thought there were tables for these, but I could not find them back...

[«Midnight»]

I think this came up a long time ago folks.

IIRC Thomas is quite correct; the answer from Sparx was that these two (perhaps one other) properties were hard-wired.

I got the impression they were not about to change that anytime soon. Given that such a change would likely require a new schema I doubt (entirely without proof) that we'll get any action on such a change until at least some "future major version" change. Perhaps 8.0?

David

PS: I wonder what would happen if you tweaked the underlying data and added your own values. Would they appear in the class properties dialog? [If so, you'd almost certainly trash your changes if you used the drop-down to set a value.] Also, would project integrity checks flag this as an error?

PPS: I tried adding a new entry to t_complexitytypes. It does not appear in the properties drop-down of a class. For that matter, nor do the same entries as the table had previously. If I tweak the database to store the new entry's ID in a class record, that class has a blank complexity when I open the properties dialog.

As to priority, I could not see it on a class dialog (which doesn't imply it was ever there at all). So I did not try anything in that area.

[KP]

PPS: I tried adding a new entry to t_complexitytypes. It does not appear in the properties drop-down of a class. For that matter, nor do the same entries as the table had previously. If I tweak the database to store the new entry's ID in a class record, that class has a blank complexity when I open the properties dialog.

Try creating a tagged value type with:

Type=Enum;
List=ComplexityType;

See also the help file. That is the only place where the t_complexitytypes table is used (by an odd coincidence, I was searching the source code for this only yesterday).

Note that rather than modify the database directly, you can import complexity types as reference data (export as reference data first to see what the format is).

[«Midnight»]

Now I remember.

Thanks Neil.

Karomann and Thomas, this doesn't quite do what you described, at least not in the same way. Still, it might work well enough. What say?

David

[thomaskilian]

Maybe the Tags could serve as a more general approach. Thus it would make sense to clean up the properties pane (like version number, creator and all that stuff I never use).