I created the custom task type below
When it is NOT the default task type, it’s labeled “Untitled template”
When it is switched to the default task type in Customize > Project settings > Type, it then shows the template label correctly (although it keeps the “Untitled template” bit at the bottom of the list, which is not the primary issue)
Is this a bug?
What IS the primary issue for you?
Hello @Phil_Seeman , thanks for the quick response. Here’s the issue I’m experiencing:
Issue#1 of 2:
When I clear out the ‘Content’ field in Customize >Task templates, and click Done,
Now, the name field is NOT auto-populated IF the custom task is set as the default for the project
this is all well, and good, but I don’t want the custom task to be the default. I want the regular, canned Asana task to be the default, and have the option to select the custom task when desired
Issue #2 of 2:
When the custom task is set as the default, it shows the name of the template “Customer MDM accurate status”, but when it is not set to the default, it is named “Untitled template”. (you can use the above screenshots to see this behavior)
Thanks, @Tim_Graham - very clear explanations, thanks!
I understand your points but I don’t find anything inconsistent or odd about the current behavior. Specifically:
A task template has to have a name so if you don’t supply one, it defaults to “Untitled template”; as far as I recall that’s always been the case and I don’t think is anything new with the introduction of custom task types.
The task-naming behavior is consistent:
Frankly I think the whole design of defining custom task types as part of the task template feature was a mistake to begin with and easily leads to confusion. Having said that, we have the design we have, and given what we have, I think it’s all behaving consistently. But let me know if you disagree!
I think we’re getting close. Since there’s a few different odd things occurring, I’ll stick with one very specific inconsistency that we can zero-in on. I think we’ll agree that the below is an inconsistency:
When I set the custom task type of “Customer MDM accurate status” as the default for the project, it correctly shows the task name in the button, and also as the first drop-down item when I click the carrot on the button. Let’s ignore the exed-out in red Untitled template at the bottom of the first screenshot for now
When I set the canned task type as the default for the project, the custom task name of “Customer MDM accurate status” doesn’t even appear in the drop-down.
I know that it IS the “Untitled template”, but what the heck?
Hi @Tim_Graham,
Very clear on your last post above, thanks!
A couple of things to note:
.@Forum-team could you check on this and file it as a bug if it’s deemed to be one? Thanks!
Checking on it, will get back with more info ASAP.
Looked into it @Phil_Seeman and @Tim_Graham. Here’s what I can add:
Naming of the Task type is to determine what kind of task type you’re creating (same is with milestone, approval or task - those are different task types). It makes sense to name your convention in way that it represents what it is intentioned for.
If you don’t name the template, it will appear like this:
If you give a name to the template
If you select this task type to be the default for the project, it will appear like this
As you can see at the top we’re seeing the name of the task type and in the Task templates section we’re seeing the name of the template. I hope this clarifies the confusion. With all of that being said I’m looking into the last part of the conversation - if we created a new task type should it appear in the dropdown menu or only as a template although technically we’ve created a template so it shouldn’t appear in the upper menu (this is my logic, I’ll check on it and get back to both of you).
Yes, that is the question - thanks for checking into that, @Stefan_Kirilov! Also when you do, please don’t forget to include the behavior of the “Convert To” menu - I assert that it’s inconsistent and confusing to not show the (non-default) custom type in the “Add task” menu but show it in the “Convert to” menu.
Absolutely agree on the inconsistency with the Convert to and the Dropdown Task menu. What I found out is that this is how it was released. I’ll forward the suggestion about the “Convert to” and Dropdown menu to the Dev team as well as another one about the option to have the task type listed in the create task dropdown menu even when the new task type isn’t the default. Thank you both for the conversation and for flagging this.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
