[Status: Backburner ⌛️] Automatic Incrementing Number on Forms/Requests

Add me to the many that are requesting this feature.  Some thought needs to be given to how to implement it.  The "counter" would be associated with a project or folder, at least for my purposes.  There may also be applications that need a counter that is global to a space.  Then any new task within that folder or project would be created with a copy of the counter incremented by one.  The counter should have some properties like starting value and increment value (default to one).  It might be handy for some applications to allow a negative increment for a countdown.  It may also be useful to set a ceiling so that when the counter reaches that value it resets to the starting value. I would recommend making the counter available in formulas for custom fields.

Looking for a workaround, I did look at the ID field and for my purposes I just need a unique ID so it would meet that requirement.  However, the ID was 9-digits which is too much for humans to read and transfer reliably.  We need something like 3-4 digits that can be used to tag physical items and enter in another database so that we can relate those items to a task.  Barcoding would help, but inevitably we end up having conversations about specific tasks and it is so much easier and precise to refer to a short number (9 digits would be too much for that).   

Welcome to the Community Mark Ireton 👋 Thank you so much for sharing your thoughts in support of this feature suggestion! 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

(Very) New to Wrike, but already want to voice an opinion on this.  Some kind of token system for titles or bodies of new tasklists would be an essential for me/us.

Currently we are using the token [Sn] for unique task ID, [###] for the project name and then [title] for the task title.

These are all set up in the blueprint for new tasks, but must be manually changed (creating un-necessary updates to the tasks users.)

Some kind of token system should include:

Unique id
Creation date/time
Project name
Created by user name
Original completion date

Having a token system allows for future or custom updates (ie counters).

Hi Matthew Traherne, welcome to the Community! 👋 

Thank you for sharing your use case here! I'm passing it on to our Product team  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! 
If you'd like to know what this Community has to offer, please check out our New to Community forum 🤗

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Automatically being able to automatically assign request form #s when the form is submitted is critical for us.  There is no way I can roll out a project request process in WRIKE without auto request numbers being assigned.   This form would be public and anyone in the company can submit a request.  Each request must have a unique identifier.  We would like to decommission our project request form in Sharepoint to reduce manual effort between WRIKE and Sharepoint, but cannot do this until WRIKE provides this functionality.   It really can't be that hard.   Create a little widget that can be added to forms.  Ask the form creator to enter starting #/character, then simply add 1 to the counter every time that form is filled out and submitted.    I don't even need it added to the title (although that would be preferable)... As long as it is in a field, then that field can be added to reports or dashboards or exported with other data to do reporting outside of WRIKE.

Welcome to the Community Mic Jackson 👋 Thank you for throwing your support here and sharing your use case here! The team continues the research here, so your feedback comes at a good time 👍

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Hello, same need here. It's honestly disappointing to see such a hugely requested feature in "investigating" status after months and months....anyway, upvoted

Hi Michele Pighi, thank you for posting, I completely understand that this is disappointing for you.

Please allow me to add some details about the research process. The Product team is looking at its feasibility, possible effects on other features, and other criteria to ensure that if this suggestion is implemented, it can be done so successfully.

We don't have any more information to share on this at the moment and there is no time frame available yet, but as soon as we have more news to share here, we'll be sure to update the thread.

Cansu Community Team at Wrike Wrike Product Manager En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

Cansu Wrike Team member En savoir plus sur les fonctionalités et les meilleures pratiques grace à nos Webinaires online

This request was made in 2018. How do we get this feature added? I moved the company off another platform to Wrike. To find that there are no plans to add (case) numbers to the form template for helpdesk requests is extremely disappointing. I had assumed that this was a basic, best practice. Does anyone have a suggestion to how to create a numbering (sequential) system? 

We would like to see this as well.  I have upvoted.  Thanks!

Hi everyone! 

I understand that this is not going to be welcome news for you, but the Product team has completed the research and for now, they can't prioritize this update as this would require major development resources. For that reason, I've changed the Product status here to 'Backburner'. This status designates that the team would like to implement this suggestion in the future but can't prioritize it for now. Thank you for all your feedback and support here, we will continue to pass your interest to the team and we'll let you know if there are any changes in the future.  

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Very disappointing.  We currently are manually assigning numbers with the hope that someday this feature will be added, but that hope is gone.  Really hard to believe that this would require "major" development resources.   Seems like an intern could crank this out this summer.

Thank you for letting us know your thoughts on this Mark Ireton; I will pass your feedback to the team. Please let me know if I can help you with anything else. 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover

Are there any workarounds?   SQL has an auto increment feature.  Can that be used in Wrike?  Can Wrike interface to an external database that would generate an auto increment number?   If Wrike can interface to an external database, could it for example add a row that would contain the Wrike ID as the primary key and another column or columns that would be auto incrementing numbers that would be available within Wrike as described in the use cases above?

Mark Ireton I share your disappointment

I was thinking about workarounds and I think the cleanest, though quite roundabout, would be to set up an event handler with a wrike webhook to look for newly created tasks, which then calls the wrike API PUT method to modify the task custom field to some text+number incremented and stored on your external database. It would require an app/api registration but I think it would be possible entirely within the existing functionality

Gerrit, great idea.  I am not familiar with the Wrike API but I'll look into it. 

Throwing in my support / absolute need for autogenerating numbers to use in request form submissions.  We're new to Wrike, moving over from Jira.  Our requested items range in the many thousands of learning assets of different types (video, SCORM, webcast, etc) - so each resulting wrike task needs to be tagged with a unique asset type + identifier (e.g. VID-12345, WCAST-4321) for retrieval, reporting, dashboards, etc.  

Thanks.

Hi everyone! I've checked with our Product team - they don't have this on their immediate plans, but they are planning to research this suggestion. I'll let you know when we know more! 

Lisa Community Team at Wrike Wrike Product Manager Become a Wrike expert with Wrike Discover

Lisa Wrike Team member Become a Wrike expert with Wrike Discover