We are working on implementing Wrike and already have a long established job numbering system that there is strong consensus that the team would like to retain. Has anyone retained a non-wrike job numbering system. How have you used it in collaboration with Wrike?
Hi Kathleen, I'm more than happy to discuss this with you here but I need a little more information.
Where are these Job numbers coming from and where are they kept now?
How are you and the team using, or want to use Job numbers? e.g. reporting, cross-referencing jobs etc.
Depending on your answers to Stephen's questions, a quick note, that if you use Request forms for projects/tasks, you can insert the job number as a part of the request form, and have it either take that information and make it part of the title of the new task/project, or you can make it a prefix to all the tasks in the project. (You can also just have it placed in the body of the new task/project). I see you are new to Wrike and may not know about the Wrike Request forms. Take a moment and review this information: Create a Request Form. This one is a good read as well: Dynamic Request Forms.
Welcome to Wrike!
Currently new job comes in it is assigned two letters representing the client and a number representing the next job in line. For example Fall Commencement is managed by Academic Affairs, the job is assigned a job number AA100. All tasks under this are AA100 and all print components have the code AA100 printed on them. The next job in for Academic Affairs when would be AA101 and so forth.
Our plan in Wrike is to have an Academic Affairs folder and within the folder a project called AA100 Fall Commencement. All projects would have the job number first, followed by short descriptor. We would also want to tag all tasks with the college client when part of the commencement project is also a Fall Commencement project but for a college.
We want to know if this makes sense, or are there other best practices? We are just starting in Wrike and open to looking at new ways to manage job numbering.
Thanks for feedback. kathleen
if each new job has standard tasks, create a blueprint for it. Then, using the request forms, use the option for either prefix based on a question in the form, or have the form put the answer automatically in the Title. I hope this makes sense. if not, i could maybe do some screen shots for you. :D
If you haven't already - give this post an up vote so we can encourage Wrike to add custom job numbering to the platform:
Wrike has a comprehensive API which can be used to add functionality to Wrike that is suited to your business.
I have been able to use a custom numbering system for changes to software by maintaining the numbers in an external database and creating tasks in Wrike using the tasks APIs.
You can take a look at the api documentation at the following link.
This is excellent Ansel, thank you.
For anyone a little apprehensive about setting up API (I know it's definitely not my strongest point!) please raise any questions you have and we can talk through them here 👍
Ansel, it would be great to hear a little more about what this looks like for you and how you're using it. Thanks again!
Ansel Robateau, can you expand on how you did this? We are currently deploying and NEED our own numbering system (like almost every business does), but can't do so in Wrike! I need a field with a job number for every project ideally. Any help would be greatly appreciated.
Richard McIlrath Thank you for your interest. I would love to show you in more detail. Unfortunately, I no longer have a paid account with Wrike since I have changed jobs. If I can find a way to get access to those features temporarily, I would happily put together some code samples and documentation that will hopefully help you in your endeavors.
Ansel Robateau, anything you have to hand is great, but I don't want to impose on your time. I have a dev team who say they will look at it soon for me and will use 'webhooks' and other things that left my head spinning, so I'd not want to put you out. Thanks so much for even replying!
Thank you for your interest, Richard.
I am posting my source code without modification at the following url.
I will expand it and add more to the documentation as I have time. I made the repository public so that you can provide feedback and submit pull requests.
This is an insane conversation. Why isn't this part of the base code set yet? Relying on API for such a basic need seems unnecessary.
This really hasn't been developed?
Wrike believes no business needs a way of tracking their work beyond lengthy job titles or equally lengthy, obscure, meaningless Wrike numbers. Of course, if you want multiple clicks per task you could have your own development team figure it out themselves with no support from Wrike. They do however point out that a subscription to Workato and Wrike Integrations works. Workato is a thrifty $10,000 per year so no reason not to ^_^
Hey Jeremy Sievers and Richard McIlrath,
Thank you for sharing your feedback here, input like this is instrumental to the Product team as they put together the product roadmap. The team is interested in this suggestion, but they can't fit this into their plans at the moment. If there are any future updates here, they will be in this Product Feedback post.
If you need anything else, be sure to let me know.