Notes |
|
|
Would this ideally be configured on a per project basis, as a set of fields related to a "Project Group", or system wide? |
|
|
(0000062)
|
a104
|
2013-03-11 21:07
|
|
I would say "system wide" for our needs, but per project would probably be more flexible. |
|
|
(0000081)
|
a104
|
2013-03-18 08:23
|
|
After some thoughts, I think system wide with an override option per project would be great to have. Because if we go per project, it would be time consuming and most of the time its always the same extra fields. Adding in an override option would by default add the system wide extra fields are added, but we would then be able to to click on a button (Override custom fields), and this would allow us to define extra fields.
Or have both options available at all time.
- System Wide extra Fields
- Per project extra Fields
If you already have a project created and an extra field is added in the system wide, then it would be added to every project, whereas per project it wouldn't affect any other project.
My 2 cents. |
|
|
|
The goal will actually be to implement custom fields, layout editors, and table column editors. |
|
|
|
Also - the ability to specify in table view that the column should be summarized in the footer (ie: custom price field on action, total price in footer) |
|