Subtask IDs - make them relevant to the parent tasks

I would find it really useful if the ID number of Subtasks within Wrike could follow on from the ID task of the parent task they are a part of.

 

I.e. instead of 

Parent task - 12345
Sub task 1 - 18976 (totally unrelated)

It could be something like

Parent task - 12345
Sub task 1 - 12345-1 or 12345-a

So, if I searched for task 12345 in the search bar, it would show all tasks that fall under the same main task.

The reason I ask this is because our teams currently use ID numbers in part of our file naming conventions as it makes it easy for us to find files and related files from previous jobs in the system, however, when we have multiple teams that work in subtasks, I need to be able to see and easily find the files relating to the sub task too.

Example, we have a "creative" brief as the parent task. It's subtasks are: Photography, Design & Video. I want to be able to search by ID number and find all the collateral together, rather than having them all under separate ID numbers.

As I understand it, the ID numbers cover the whole of Wrike, regardless of team/account, and so every task is unique which I can appreciate, but think it could be great if the IDs were unique to teams, rather than the entirety of Wrike.

 

Upvote 11
7 comments
Spot On Innovative Approach Stellar Advice
Avatar
Thanks for posting your idea on the Community, Holly! You're right, task IDs are unique across all Wrike accounts, so it’s not currently possible to make subtask IDs correlate with parent task IDs. Another reason it’s not possible is that in Wrike a subtask can belong to different parent tasks.
I wanted to add that even though subtasks don’t currently show up in the search results when you search by a parent task ID (because subtasks have different IDs), you still see them when you click a parent task and open it in the Task View. Could you let me know why you prefer seeing subtasks in the search results rather than in the parent task? I’ll be looking forward to your reply!
 

Anna G Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Anna G Wrike Team member Become a Wrike expert with Wrike Discover

1
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hey Anna,

 

It's more for when searching and referencing jobs outside of the system, i.e. our files in the network.

 

We work in a way that we have a top level "design task" which is the main job, and any supporting work from other teams is a sub task within that.

So, say we have a campaign as the main task. We have photography to support the campaign, and video work to support the campaign that all sit under the same task as subtasks, and these sub tasks are in different folders so that the relevant teams can move their own tasks along at their own rate.

I understand it's fairly easy to click to get to the parent task to find the number, but I'm more concerned that people won't do this, or that people may not realise that there is a parent task to reference the number of and that causes our photography work to end up in a different folder or location in our storage solution (not wrike), so we may end up duplicating work if they are saved under different numbers, or not being able to find work.

 

Hope that makes more sense :)

3
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

In addition to my comment above, if it could also be possible to have a custom field or some other way to automate the job numbers for situations like our use case?

 

Our only other way to reference the files is to generate the ID numbers elsewhere (i.e. google sheets) and copy the job number into Wrike, but this leaves a lot of room for human error and duplication and would add unnecessary time into our workflows. 

3
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Holly, I am very sorry for the delay in response. Thanks for describing your use case here, I will make sure to pass all details to our Product team.
As for Custom Fields: it is possible to add a numeric-type Custom Field to your tasks, however, you or your teammates will have to manually enter job numbers there and there's no way to automate this process. That's an interesting idea though, thank you for sharing it here!
I'll make sure to direct other people who have similar setups to this post so they could share their tips and tricks. Let me know if I can answer any other questions or be of any help!

Anna G Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Anna G Wrike Team member Become a Wrike expert with Wrike Discover

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Anna!

 

No problem, thank you :)

 

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar

This is our problem, too. It has been very difficult and confusing when we historically use project numbers to name our stored file and jobs on our servers. We have to manually force the main "project ID task#" into the naming of our subtasks so designers know what code to use.

 

We can not manually assign custom numbers or use a google sheet because we have too many people and jobs.

0
Comment actions Permalink
Spot On Innovative Approach Stellar Advice
Avatar
Stephen

Hi Heather, thanks for your input here on this. 
 
@all - just to note Heather has made a great suggestion about generating project ID numbers from Request forms too - which may interest members here. If it does, please make sure to vote there also. Thank you!
0
Comment actions Permalink

Folllowing List for Post: Subtask IDs - make them relevant to the parent tasks
[this list is visible for admins and agents only]

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