Changing the default task type (plain sticky note) to custom task type

Every time I create a new task, it starts with the default task.. Which has a lot of useless (IMO) information like author, task ID, creation date, etc. I wish there was an ability to change the default task type to a custom task type so that it could display the information (that I find useful) in the item details.

Currently, I have to make sure to click the task type before I create the task, which is easily forgotten when making 100+ tasks a day. Further, my coworkers who are not tech savvy will 90% of the time leave the task type as the default, even after creation of the task.

If I could change the account wide default task type to be the custom item type we specified, it would streamline our processes and make the interface a lot more efficient. Changing the default task type for individual spaces and projects would be ideal, but I am sure it will be more difficult to implement. Thank you in advance!

Upvote 15
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
6 commenti
Avatar
Juan

Hi Mike Montalvo, welcome to the Community! Thank you for creating this post, it's an interesting suggestion. I've passed it on to our Product Team 👍

May I ask what is the process you follow to create your tasks? 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Hi there! Any updates on this request??
It is something that is quite restrictive.

We also want to set our Custom Task as the default Task. But as Mike has pointed out, people on the team will inevitably miss it.
Otherwise, we should be able to change the "Default Task" to any structure we want.

Thanks

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Hi Marco dos Santos! 👋 Welcome to the Wrike Community!
 
There's no new update to share at the moment, but I have shared your interest with our product team. 😊 It would be great if you could share more details about the process you or your team currently follow to create tasks.
 
In the meantime, we'll wait for more engagement on this post. Once it reaches 60 upvotes, we'll be able to assign a status. Thank you again! 🙏

Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Conosci le straordinarie funzionalità di Wrike e le best practices

Basudha Sakshyarika Wrike Team member Conosci le straordinarie funzionalità di Wrike e le best practices

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Unless I'm doing something wrong, I just discovered the need for this functionality. 

I set up a custom item type (project) called "Epic" for our scrum team. I want my "User Story" custom item type (task) to be the default option when I add a new story to the Epic. This would prevent me or anyone else on the team from creating a normal default task and having to convert it to the correct custom item type. I would also like to have my "Bug" custom item type and the default task to be options to select within the Epic (which is what I have set up now).

I just tested unselecting the default task from the Epic to see if that would force User Story as the default but the default task is still the default even though I didn't select it! From a user perspective, this is extremely frustrating and it makes me think the feature is not working as designed. Thank you for your time considering this!

3
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Makes sense, Daisy Hibbard! I will pass your feedback on to our product team. Thank you! 👍🏽

Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Conosci le straordinarie funzionalità di Wrike e le best practices

Basudha Sakshyarika Wrike Team member Conosci le straordinarie funzionalità di Wrike e le best practices

1
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

I also support adding this functionality. When we use the default task type, by default all subitems are also the default task type. This prevents a true hierarchy of items, especially in reporting and dashboards and especially when broken down by status. With other tools like Jira and Azure DevOps Boards, it provides this. Having to manually go back and update each subitem to a custom task type is painstaking, not user friendly, and is prone to misses/gaps, especially when multiple people are creating tasks. I don't understand the use case for having a flat structure with task types at all.

      - Task

              -Subtask

              -Subtask

      -Task

            -Subtask

            -etc.

 

Thanks!

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Changing the default task type (plain sticky note) to custom task type
[this list is visible for admins and agents only]

Su

Upcoming Live Sessions

Didn’t find what you were looking for? Write new post