Context Navigation

Changes between Initial Version and Version 1 of Ticket #13328, comment 16

initial	v1
1	1	Replying to [comment:15 anonym]:
2	2	> Maybe because there is already consensus among the proponents that adding a simple project DB field alone would be enough? No concrete problems with this approach were ever mentioned anywhere, and there are no obvious problems or downsides. The silly / fancy frills can be left to plugins of course. We think this would clearly help many users of Trac and Trac plugins could grow enormously more useful.
3		The only "concrete problem" I know is people who just have 1 project have a new "useless" ticket field. But this is already true for most users with ticket field "component". I saw several sites using track where the components field is not used or just treated very stepmotherly. Probably it makes sense to simply give the opportunity to redefine the field name "component" to "project" during Trac Installation.
	3	The only "concrete problem" I know is people who just have 1 project have a new "useless" ticket field. But this is already true for most users with ticket field "component". I saw several sites using trac where the components field is not used or just treated very stepmotherly. Probably it makes sense to simply give the opportunity to redefine the field name "component" to "project" during Trac Installation.
4	4
5	5	>