For an immediate solution, I created a custom form with fields for a year, campaign number and job number. This form lives on all projects. Then I created a report titled "Next Job Number" and every time we resource a job, we also manually give it a job number (and fill in the year and campaign numb...

I will also submit a feature request for it. Hopefully some additional support will get it moving faster. It's shocking to me that it's not a standard feature.

It is. We're running into issues where they're trying to shorten files names--while keeping all pertinent information. Also the PMs are used to having the project numbers burned into their brains, and 6 numbers is stretching their mental capacity, since they're used to 4 digit numbers. :-)

We've been using the reference number for a project as an identifying job number since our implementation. This was working OK--but after only 6 months in, the number is already 6 digits long, so we're on the hunt for another solution. Does anyone have any recommendations on how you populate job n...