- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Thanks @Kim Donkers‚‚. After reading, and at a high-level, here is how I understand it based on your needs:
Today
- A request is submitted, it gets ref # 16050.
- The request gets converted to a project and the project now gets ref #16051 (because a new project or "object" was created so it incremented by one). If several other objects are created before the conversion takes place there could be a big gap between these reference numbers.
- You can create a custom calculated field or "job number" to capture and move the original ref #16050 from the request to the project so that you have one number, but essentially you end up with three numbers today (16050/16051/custom job number), even though you are really only referencing one of them.
Ideal Scenario
- A request is submitted, it gets #001
- This request is converted to a project, the project then adopts #001.
- If the request is not converted, the next request is #002, and so on. A project number is not generated; however, if request #002 IS converted to a project then this project adopts this number (002) and so on...
Last two questions:
- Do we need a sequential number for requests/issues or only for projects?
- Do you need to be able to edit or reset this number at any time?
As for the "copied number being buried in a custom form," this is great feedback and is currently on our backlog as an important usability enhancement. I don't yet have a date as to when this would be available, but wanted to acknowledge that we are aware of this.
Views
Replies
0 Likes
Total Likes