From 8df3db566a3a937b45ebf11adb90d265e6f5e2d4 Mon Sep 17 00:00:00 2001 From: Andreas Baumann Date: Sun, 17 Nov 2019 20:45:02 +0100 Subject: initial checking of customized version 1.0rc9 --- themes/CleanFS/templates/details.edit.tpl | 255 ++++++++++++++++++++++++++++++ 1 file changed, 255 insertions(+) create mode 100644 themes/CleanFS/templates/details.edit.tpl (limited to 'themes/CleanFS/templates/details.edit.tpl') diff --git a/themes/CleanFS/templates/details.edit.tpl b/themes/CleanFS/templates/details.edit.tpl new file mode 100644 index 0000000..d56bd56 --- /dev/null +++ b/themes/CleanFS/templates/details.edit.tpl @@ -0,0 +1,255 @@ + + +prefs['visible_fields'] ); +# FIXME The template should respect the ordering of 'visible_fields', aren't they? +# Maybe define a 'put visible_fields in default ordering'-button in project settings to let them make consistent with other projects and a no-brainer. +# But let also project managers have the choice to sort to the order they want it. + +# FIXME If user wants a task to be moved to other project and a hidden list value (not in visible_fields) would be not legal in the target project: +# Should we show that dropdown-list even if the field is not in the $fields-array to give the user the chance to resolve the issue? +# The field list dropdown is not a secret for webtech-people, it is just not visible by css display:none; +?> + +
+ + + + +
+
    + +
+
+ + - + +
+ + - + +
+
+
+ + + + +
+ + + 'details'), Req::val('detailed_desc', $task_details['detailed_desc'])); ?> +
+ +
+ + +
+ listTaskAttachments($task_details['task_id']); + $this->display('common.editattachments.tpl', 'attachments', $attachments); + if ($user->perms('create_attachments')): ?> + + + + +
+ + +
+
+ +
+
+ perms('add_comments') && (!$task_details['is_closed'] || $proj->prefs['comment_closed'])): ?> + + +
+ + +
+
+ + + +
+
+
+
+ -- cgit v1.2.3-54-g00ecf