Can we have a classification for Tasks?
-
Wooah, I keep you guys pretty busy. Whatsoever, I started to use Tasks today and discovered that I can have a Status for a Task, but not a classification. Can we have something like a type of Task? e.g. Something which helps me to divide new features from Bugfixes? I can imagine the following types of Tasks: - New feature - Bugfix - Update of an existing feature and so on... If we have this, we could allow other Members to submit tasks classified as "Bug". This Tasks would have a normal priority and the responsible Workspace admins can then go through the list and Accept, Close or reject Bug-Tasks.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek -
Wooah, I keep you guys pretty busy. Whatsoever, I started to use Tasks today and discovered that I can have a Status for a Task, but not a classification. Can we have something like a type of Task? e.g. Something which helps me to divide new features from Bugfixes? I can imagine the following types of Tasks: - New feature - Bugfix - Update of an existing feature and so on... If we have this, we could allow other Members to submit tasks classified as "Bug". This Tasks would have a normal priority and the responsible Workspace admins can then go through the list and Accept, Close or reject Bug-Tasks.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf WondratschekYou can add your own fields to the items as well as define new tag groups. So, in our internal workspaces we've been adding classification column like that. And, yes, one of our todo items is to improve the defaults so each instance will have such field out of the box.
-
You can add your own fields to the items as well as define new tag groups. So, in our internal workspaces we've been adding classification column like that. And, yes, one of our todo items is to improve the defaults so each instance will have such field out of the box.
Can I specify something like Task-Templates, so that other Members who are not added to the Workspace are allowed to add Tasks of a certain classifications, e.g. Bug Tasks? They only should be able to add them, and not to modify them. Edit: Just found out how to do it, really nice work :thumbsup:
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf Wondratschek -
Can I specify something like Task-Templates, so that other Members who are not added to the Workspace are allowed to add Tasks of a certain classifications, e.g. Bug Tasks? They only should be able to add them, and not to modify them. Edit: Just found out how to do it, really nice work :thumbsup:
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf WondratschekCurrently the templates are not available, unfortunately. As for the modification, the original author is restricted to be able to add description/title/comments/attachments, not other fields.
-
Wooah, I keep you guys pretty busy. Whatsoever, I started to use Tasks today and discovered that I can have a Status for a Task, but not a classification. Can we have something like a type of Task? e.g. Something which helps me to divide new features from Bugfixes? I can imagine the following types of Tasks: - New feature - Bugfix - Update of an existing feature and so on... If we have this, we could allow other Members to submit tasks classified as "Bug". This Tasks would have a normal priority and the responsible Workspace admins can then go through the list and Accept, Close or reject Bug-Tasks.
The scariest moment is always just before the Start - Stephen King
Die Frauen warten auf die Liebe, und die Männer warten auf die Frauen - Wolf WondratschekWe've just added a Category field as a default field for all Tasks instances. I got sick of adding it manually to each Tasks instance I spun up!