In my case of Work Flow, when create automatic the task in workflow Rules, I need to use the trigger Task Type.
So, it would be better in this Type selection, the product provide the Type set from the Trigger Task.
It sounds like, in a rule you want to create a new task/subtask and value its custom field with the value of the triggering task’s custom field. You can use the + sign to do this for some fields (like Task Title and Description–see screenshot) but not for custom fields (yet).
@Richard_Sather & @lpb
yes, you can add a variable on a number custom field.
It will give you options to select from all other number fields in the project.
Thanks all for the feedback and responses. Appreciate all.
After check with all of other custom field type, actually there is a workaround to use the additional Fields,
so create new Field with Text.
Together with Selection ( user could not freely choose it )
then when auto create, we set that Text Field from the selection field of the trigger task.
This seems work in Rule.
The Field in the Task can be used to do some different flow of auto created task/approval in Section/Board flow.
The solution is a workaround to use both fields: Selection type and Text type. First task should use Selection Field, second triggered task is using Text Fields, and the further tasks/approvals keep use the Text Field. In this way the same Field Variable will have constant value from beginning to the end.
new task is created manually by user, set the X manually
then create Rule for Completion task
** when complete, and if the section is New, set the Y by X in new Triggered task
** when complete, and if the section is Analysis, set the Y by Y in new Triggered task
** when complete, and if the section is In progress, and if Y was Major, set the Y by Y in new Triggered task to Section of Approval A
** when complete, and if the section is in progress, and if Y was Minor, set the Y by Y in new Triggered task to Section of Approval B.
fyi, this Rule can not be used for Template, because right now the rules only can set the specific existing Project and Section. After the template is created, whenever we use it for new project, the position of project and section was lost anywhere and it would go to the first section. To solve this, I guess need some development to provide the “this” project in Task Creation option for Project-Section; it is the whatever project id where the rule is used.
For the template, I have a workaround. Perhaps I will share in the next coming days/weeks.