Context Navigation

MultipleProject

v9	v10
175	175	- ease sharing workflows between users: having workflows encapsulated encourages implementation of several generic workflow solutions (that can be easily tweaked for specific use) that could be worked and provided by default or in a file repository - that would even ease to choose the starting workflow of a new TRAC user because he could easily choose a base workflow instead of having to hack the default one, simply adding modifications each time it seems required;
176	176
	177	Another option is a combination of both alternatives:
	178	- Workflows are independent entities, that can be associated to projects, resource-realms, resource-types, and maybe even specific resources (I'm using "resources" instead of "tickets" in order to strive towards GenericTrac :-) ).
	179	- When a workflow is needed for a specific resource, the workflow used is chosen to be the workflow entity that is the closest to the resource in the hierarchy.