#180 Ultra dynamic fields

[T Chiu]

What I'd like to do is to create dynamic fields on a project-by-project basis.
For example, I'd like to create a field type "foo" with columns "name" (char 20) and "value" (int 16) that's applicable to project XYZ and then a field type "bar" with columns "Event" (char 20) and "date" (datetime)
I'd then like to be able to insert into project XYZ multiple instances of "foo" with differing "name" and "value" values and "bar" with differing "Event" and "date" values
When cloning a project, provide an option to copy: NONE, ALL FIELDS INCLUDING VALUES, or EMPTY FIELDS ONLY to the new project
Provide an option within the project, an option to COPY ALL FIELDS INCLUDING VALUES or EMPTY FIELDS ONLY to a different project
Within each project, visibility would be a grid with expanding rows of field type and values.

For example
"foo"
Notebook, 2
Pen, 4
Pencil, 4
Eraser, 2

"bar"
Mid-Term, 2014-02-18
Final, 2014-05-28

Report initial
foo (4) {Expand} {Add New} {Copy ALL} {Copy Field}
bar (2) {Expand} {Add New} {Copy ALL} {Copy Field}

Report Expanded
foo (4) {Shrink} {Add New} {Copy ALL} {Copy Field}
Name | Value
{Edit} {Delete} Notebook | 2
{Edit} {Delete} Pen | 4
{Edit} {Delete} Pencil | 4
{Edit} {Delete} Eraser | 2
bar (2) {Shrink} {Add New} {Copy ALL} {Copy Field}
Event | Date
{Edit} {Delete} Mid-Term | 2014-02-18
{Edit} {Delete} Final | 2014-05-28

[Frank Bergmann]

Rejected, sorry! We won't include this (per project fields) in our product ever.

However, ]po[ can already do fields per project sub-type (Consulting project, Other, ...), maybe that's sufficient for you? Otherwise it's not that difficult to develop something like this if you need it. A skilled developer should not take more than a week.