agreed! especially where those are linking fields between data clusters (e.g. client <-> project) where the client CRM data is essentially not deeply integrated in the task / todo structure of project management
1st priority: setting the default values based on ancestor nodes or sibling nodes
2nd priority: required or not required
3rd priority: display or hide when empty
side note: would this be hard to do if it is in an extended supertag? e.g. fields in todos inherit from the parent node but a project which could be an extension of the todo base tag inherit from the associated client node
nice to have: move it up or down in hierarchy when it is from an extended supertag
You don't have permission to do this.
You're going a bit too fast! Take a break and try again in a moment.
Something went wrong! Please reload the page and try again.
Your session has expired. Please reload the page and try again.
agreed! especially where those are linking fields between data clusters (e.g. client <-> project) where the client CRM data is essentially not deeply integrated in the task / todo structure of project management
1st priority: setting the default values based on ancestor nodes or sibling nodes
2nd priority: required or not required
3rd priority: display or hide when empty
side note: would this be hard to do if it is in an extended supertag? e.g. fields in todos inherit from the parent node but a project which could be an extension of the todo base tag inherit from the associated client node
nice to have: move it up or down in hierarchy when it is from an extended supertag