Include unique task ID in title even if it has mapped responses

Every task that is created within the Request Form should contain a unique ID in the title (can be configurable), no matter if there are mapped responses or not.

For example, a title should look like this: [UniqueID] - [Name]

The unique ID is generated automatically, whereas the name is an answer to one of the request form questions, which is set as 'Title'.

Unfortunately, currently it is only possible to choose between a default title where a unique ID is created or a custom title which is generated by the answers within the form.

Find more posts tagged with

On hold

Status: On hold

Comments

Permanently deleted user

Hi Romana, this is a fair suggestion and I can see, by the votes, it's something other members would like to see happen too.

I'll make sure the Product Team is made aware of this post and if/when I have further information I'll get back to you here. Thanks for sharing and welcome to the Community! 🙂

Thomas Finney

Take this a step further you really should be able to use any number of variables to build a standard structured title automatically.

Faris Armaly

Hi - We use Wrike for Change Control. With each new request, we'd like to assign it a unique short code. For example, "CR-120"

Ideally it would increment and be non-repeatable.

Karl Johnson

Any update on this feature?

Keir Johnson

Adding to this thread. Our team is in support of this concept. For us, it would be great to have the option to configure whether the ID is added to the task automatically whether or not the task was created from a request form. For example, we often forward emails to create a task in Wrike when we receive a support request from our clients. It would be awesome to have the ID added automatically to the title of the task in this case or when a task is created manually in Wrike.

Having the ID makes the task more easily searchable and generally just makes keeping track of tasks more efficient.

We would be grateful if the Wrike team considered this request!

Anna Cunningham

Echoing support for this idea!

Joshua Devine

Adding my support for this feature. As we build our infrastructure with Wrike this is becoming a significant pain point as multiple teams manage hundreds of requests per week.

Al Sape

Yes big need, hard to reference tasks in meetings without this. Also, essential to board views

Elizaveta Bogdanova

Hi everyone! Our team is planning to research this suggestion, thanks a lot for bringing this up!

Stephanie Bannister

Any update on this feature? It is important to our team as we expand Wrike's use across the entire organization.

Elizaveta Bogdanova

The team isn't currently planning this functionality. We'll continue to pass on your feedback from this thread and if/when we get an update from the Product team, we'll let you know here.

Cris Milian Ganz

Just following up on this request again. When are they aiming to release this feature?

Elizaveta Bogdanova

Hi @Cris Milian Ganz, welcome to the Community 👋
Thanks a lot for supporting this idea! I'm passing your feedback to our Product team. Although the team isn't currently planning to work on it, please make sure to upvote the original post above if you haven't yet. The number of votes helps the team understand how popular the suggestion is. Here's more detail on that, but please let me know if you have any questions!
Once this post reaches the 60 upvotes' threshold, we'll add a Product status here 👍

Michele Pighi

We're adopting Wrike also for software support and we need this feature.

Upvoted, please consider it :-)

Cansu Yetisgin

Welcome to the Community and Wrike @Michele Pighi, thank you for adding your support here🙌🏼

Shraddha Gupta

Hi , We need feature too .

Juan Muttoni

Hi @Shraddha Gupta welcome to the Community! Thank you for supporting this idea, please feel free to upvote it, in case you haven't already. You can check how we process feedback in this article.

Also, I'd like to mention that you can use automation rules to automatically add prefixes or change the name of your tasks.

Lastly, please feel free to visit our New to Community forum to get the most out of your experience with our Community 🙂

Josh Walker

Hi Juan,

I think the automation rule would be perfect if you could add a dynamic field such as a unique id. At a minimum I would want to add the wrike id which can be seen from the table view.

I've upvoted the above.

Thanks.

Elizaveta Bogdanova

@Josh Walker Thanks a lot for sharing your use case and upvoting the main post here 🙌

And welcome to the Community 👋

Benjamin Rodd

Agree with this idea. The prefix/suffix is useless for us without dynamically generating the content. At a minimum adding the ID...

I'm using Wrike Integrate to automatically create dropbox folders for each task/project. In order to do this I need to first re-write task names to pre-pend the task id ... except for those that have been created by form completion which already have this...

Elizaveta Bogdanova

Thank you for supporting this idea @Benjamin Rodd, we appreciate your interest! We don't have updates at the moment, but we'll be sure to let you know here in the Community if we do in the future 👍

James Ackerly

Have upvoted in support of this idea.

Shaun Buckley

Upvoted. It's such a useful feature - I've used it on other form tools. I hope it gets implemented soon.

Juan Muttoni

Hi @Shaun Buckley, welcome to the Community! Thank you for adding your feedback here, I've shared it with our Product Team 👍

Also, please allow me to suggest that you explore our New to Community forum to uncover all the available resources within our Community 🙂

Dan Fuller

Yes, please. We are just setting up and surprised not to see this capabilty. common on other platforms. Make management of large lists alot easier.

Kevin Cooper

Attn: Wrike Support

It’s now been over 7 years since this minor (but valuable) update was first requested which would yield great benefits for your customer base. I don’t see the programing/code to add this functionality to be overly complex, costly, or onerous, yet the value that would be derived from this would be significant.

Allowing the UNIQUE ID to be used in conjunction with a mapped CUSTOM TITLE (generated by answers within a given request form) should be core/basic functionality -- table stakes. One should not have to choose between (1) having a DEFAULT TITLE appear with the dynamically generated UNIQUE ID or (2) having a CUSTOM TITLE with no ability to include the systematically generated UNIQUE ID – either as a prefix or suffix.

Can you please let us know if this update is completely off the table given that it has been 7 years since it was first requested -- with seemingly no movement or progress made to implement? OR since it has been 7 years, and in many circles 7 is considered to be lucky – can this feature fix/update be implemented in your next update cycle?

I have no doubt your customer base would be extremely appreciative if you could address this low hanging fruit.

Many thanks on behalf of everyone here, and all those who opted not to ask or provide support for this update because they felt it would not get the attention it deserves.

Rohan V

Hi Everyone 👋

Thank you for sharing your thoughts and feedback. We understand that some of our users are looking for this functionality. Our team has thoroughly researched this idea, but unfortunately, we haven't been able to add it to our roadmap for this year as other priorities are taking precedence.

We value your input and will continue to forward all feedback to the responsible team. We'll keep you updated if there are any changes regarding this feature implementation.

Thanks again for your patience and understanding in this matter.

Kevin Cooper

Thanks Rohan for the update. We were hopeful that since having waited patiently for 7 years for this minor change to be made, that it might have made the cut for the 2025 roadmap. Such a small change with great benefit -- yet still sitting in the queue. Guess we'll wait to see if it shows up on the 2026 roadmap.

Francois Boulanger

After 7 years!!! They might be just not figuring out how to implement this simple thing! ... or at least just inform the community that you would never implement it. That way, we can just select another solution!

Basudha Sakshyarika

Thank you so much for your patience, @Kevin Cooper and @Francois Boulanger. As Rohan mentioned, we haven’t been able to add this to our roadmap yet because of other priorities, but please know that it may be considered in the future. We’ll continue to keep an eye on this and will let you know if there are any updates. Thanks! 😊