http://www.activecollab.com/forums/topic/4336/ Recent posts on topic: Project slug instead of project ID in URL-s en-us Wed, 23 May 2012 20:08:10 CDT http://www.activecollab.com/forums/post/19367/#post19367 http://www.activecollab.com/forums/post/19367/#post19367 infield I like this idea. I like the idea of a brief project job code. Our old home-grown tracking system used to generate a unique job code in the form:

CAB-0001

Where CAB was a company abbreviation code (defined in the company setup) and the number was serialized to the company. We used the code for all our job backups, it was pretty handy.

I'm not sure we would do it now, but we also used to assign a leading number for job category. So if 8 was the code for a web project a job number could look like CAB-8010 and we would know who the client was and what kind of job it was at a glance. Kind of complicated but it came in handy when we were doing lots of little jobs.

]]> Fri, 24 Apr 2009 02:44:45 CDT http://www.activecollab.com/forums/post/19359/#post19359 http://www.activecollab.com/forums/post/19359/#post19359 Matt Robenolt How how implementing a hashing feature to generate random strings to use instead of numerical project ids. Then a project will have a url like: /projects/sd8dnas instead of /projects/10

I see this being slightly more beneficial because then clients won't know how busy you are, per say. Sometimes that kind of information isn't idea to be revealed. If they see: /projects/2, they can be a bit more leery as opposed to seeing a /projects/1400 url.

Or even take this to another level and allow "slugs" to be created either automatically, or set manually, then we can use the job # in the url instead of a random string: /projects/ydek-09-001 for example.

This wouldn't be too complex of a feature, but I think the benefits would be real nice. It's not something that I'd enjoy writing a patch for because every update would then require to modify the patch.

Thoughts?

]]> Thu, 23 Apr 2009 19:40:57 CDT