Automatic Incrementing Number on Forms/Requests

It would be nice if Wrike could automatically assign a number on a form/request submission that could be used as a case number, order number, etc. We would want to set a fixed prefix and suffix, and then, use the number in the title of the task/project created from the submission.

Find more posts tagged with

On hold

Status: On hold

Comments

Ben Silverstein

Agree! We've spoken about using Forms for everything from Vacation Requests to Support Tickets. Setting prefixes and suffixes and auto-incrementing numbers will hugely help for that.

Permanently deleted user

Hi guys,

Currently, you can't set a prefix number for these, however, I wanted to point out that you can map a Request form answer to a task title which may be helpful here. Meaning, the person filling out the form, can create an answer and this answer can populate as a prefix on the task or Project generated in Wrike.

This might help for now 👍

Matthew Amoss

Thanks, Stephen. We're well aware of the ability to map a form answer to the task title. The auto-incrementing number feature that I'm requesting would supplement the mapping feature. Auto-incrementing numbers are necessary for just about any form when the form request will be used more than just a handful of times.

Stephanie Westbrook

@Mattthew Hi! Each task (whether it's generated from a Request form or not), has a unique identification number. Would that number work for your use case or do you need sequential numbers for tasks specifically from Requests?

Jeff Kaemmerling

@Stephanie- can you pipe in that unique task ID as a title for a request?

Matthew Amoss

Is there any plan by Wrike to add this feature? The form submissions are not very useful if you cannot automatically assign a number that appears in the task title.

Ben Silverstein

I agree with Matthew. This is a standard ticketing need - stakeholders and service providers both need a highly visible unique ID. If you can show and search by Job ID in List View, that would be a suitable holdover, but setting prefixes and suffixes on incremental numbering is critical.

Matthew Amoss

This is a feature that should be relatively easy to implement. I'm not sure why Wrike hasn't responded yet to this request.

Michał Masadyński

Agree very useful feature that is need it to deal with notification/tickets.

Bram Robyn

Would be very usefull! Are there any plans to implement this in the near future?

Iñaki Montero

Any news about this feature? It would be very useful

Elizaveta Bogdanova

Hey everyone, thanks for adding you comments here. I don't have any updates to share with you currently, but I'll make sure to pop back here if I have news. In the meantime, more +1's will definitely help our Product team assess the popularity of this feature 🙂

Buddy Gregory NLWC

We definitely want to implement a ticketing system in Wrike. I will allow me to add more of our enterprise to the wrike family ... maybe anothe 75 users. In the meantime we will continue with our present system.

I concur with other comments, this should be a fairly easy implementation.

Would like it know where it is on the implementation list.

Leila van Zyl

To add another requirement to this: it would be great if we could have more flexibility and control over the ticket number. For instance, under Account Management, have the ability to set whether the ticket should be a sequential number starting from a number set by the account owner (it could be 1, it could be 1234) and/or whether the ticket number should contain a present prefix or suffix.

The prefix/suffix should be able to pull through a team or project's 2/3 letter code, which is also set by the account owner. For instance, if the "Kit Kat product team" submits a request then the case number/ticket number would be e.g. KIT1234. This would especially be helpful considering Wrike's new Spaces feature. We need to have a way of distinguishing where requests are coming from, especially if more than one team is using Wrike.

Venugopalan Narayanan

I concur with Matthew and Leila request, this would be very helpful if implemented soon. I believe the automatic numbering of the form once submitted should be fairly easy to implement. Would appreciate if Wrike team would consider this on priority.

Marina Jimenez

Hello, we will need to reconsider Wrike if this feature is not added within the next fiscal year. We are an internal graphics design team with a constant stream of incoming projects. Our naming convention is not working as well as a numbered system would. This will be a deciding factor in choosing to move forward with Wrike.

Elizaveta Bogdanova

Hey everyone, thanks for your support here!

Our Product team is really interested in this suggestion. After checking with them as this post got 60+ upvotes, I added the "Backburner" status here. The team is planning to investigate soon - I'll get back to you when I have more details. 🙌

Chris Mentone

I currently use excel for generating engineering change notices. Wrike would be good for communicating between departments. If we have to enter the automatic number manually, this would allow the chance of skipped or duplicate numbers. Also a 9 digit number is too long for us. We use a 6 digit number, where the first two digits is the year and the last four is the sequential number.

This change will help justify keeping the Wrike software! Thank you.

Permanently deleted user

Hey everyone,

This suggestion is still on the radar of our Product Team, but it isn't on the roadmap just yet. That's why the status is still "Backburner".

However, we are still reading all of your feedback and use cases. Be sure to comment them under this thread to help with the conversations that are going on!

Thank you for all of your feedback so far!

Ben Doorn

Please add this to the roadmap, having a generated code with a project prefix is an absolute must to have, working with multiple projects simultaneous is almost not doable without having an easy to remember project related ticket/issue/task number.

Michelle Hammond

Our company uses metal dies and each new die is assigned a six-digit sequential number, with a two-letter code at the beginning of the number indicating what type of die it is. A number of different people can assign a new number to a die, but the number must come from a single source so that different dies aren't named with duplicate numbers. This has always been done with a spreadsheet that people signed into in order to claim the next available number.

We have now created a request form in Wrike so that our sales partners can request a new art asset that causes each new die to be ordered, ostensibly bypassing the need for information to be entered on our spreadsheet -- except that we still need the sequential die numbers with the two-letter code at the beginning. If Wrike could generate these sequential numbers as each form was submitted, including the two-letter code from a drop-down list on the form, this would streamline our workflow and increase our efficiency tenfold.

I see that the status of this sequential numbering option is still listed as "Backburner." Any new update since February 2020?

Elizaveta Bogdanova

Hi @Michelle Hammond, welcome to the Community! 🙂 Thank you for sharing your feedback and use-case here!

@Everyone I've just checked with the Product team - they are now researching how this could be implemented in Wrike. I changed the status accordingly here and I'll keep you posted on the progress here. Thank you for your feedback and votes! 🙌

Michelle Hammond

Thank you, @Elizaveta Bogdanova, I'm glad this has been upgraded to Investigating and will watch this space. I am excited to see what could happen!

Marina Jimenez

Yes, Wrike is already assigning numbers when a request is created, but we can't search for projects based on that number. We then have to explain to the client, yes, you have that number but it doesn't match your project! Am I missing something on this process? We need to be able to number projects as they come in. Thanks! - M

Elizaveta Bogdanova

Hi @Marina Jimenez! Each project has a unique ID and you can search by that number, but request forms' IDs work in a different way and can't be searchable. I'll let you know once I have an update from the team regarding this suggestion.

Simon Foulser

Is there any update on when this feature will become available? Like many of the contributors on here I need sequential numbers against forms.

Gerrit Lane

This would be a massive help for us, too.

We use incrementing numbers for drawings, quotes, projects, etc.

Our current (messy) workaround is to import a spreadsheet with a few thousand blank tasks with a deferred status, blank character as the task title, and the incrementing number pre-filled in a custom field. Then users can sort by this custom field and modify the first of these blank tasks to ensure duplicates aren't created. But this means we can't use request forms & also leads to slower opening times for folders with these tasks.

Cansu Yetisgin

Hello @Gerrit Lane, @Simon Foulser, welcome both to the Community 👋🏻

Thanks a lot for your support and for sharing your use cases here! The idea is still under investigation by our Product team with no ETA available at this point. As soon as the team begins the development, we'll change the status to "In the making" here and share an update.

Stacey Olsen

Hi, is there a status update on this? We desperately need this to increment Serial Numbers, FIFO, etc.

Cansu Yetisgin

Hi @Stacey Olsen, thanks for posting 😊

At the moment, the Product team continues the research and unfortunately, I have no further updates. If there are any changes we'll be sure to let you know here.