Accessing 'Project Workspace consumes a Project Number integer without creating a new ProjectIssue Typically, in an OOB scenario, whenever a user navigates to a new Project form, a Project 'number' is generated, i.e. PRJ000001. Even if that Project is not submitted, that number is used up, meaning, if you navigate to 'Projects > Create New' again, without ever submitting a Project, the second time the new Project form loads, you will see PRJ000002. This is an expected OOB scenario. It is always possible to workaround this by setting the System Property glide.itil.assign.number.on.insert to true. This System Property will NOT display a 'number' for ANY Task record when you view a new Task/Project/etc form and will therefore only use up a number once the Project is inserted. There is however a scenario you may run into - slightly different - where, if you simply navigate to Project Workspace (AND DO NOT CLICK 'NEW PROJECT'), you will see the next time you do create a new Project (using any method), a Project number is skipped. Steps to reproduce this might look like: Navigate to Projects > Create NewView Project Number (example: PRJ000023)Navigate to Projects > Project Workspace (do nothing once Project Workspace loads)Navigate to Projects > Create NewView Project Number. It will now be PRJ000025 (skipping a number)ReleaseOrlando +CauseThis number skip is caused by an OOB UI Macro 'html_page_pm_home' Specifically, line 10: gr.newRecord(); As long as this UI Macro loads, as it does when Project Workspace loads, the system will set a new number via 'gr.newRecord(); (as if we were on a NEW Project form) By updating this line to a new script, we can keep all the OOB functionality, without using up a number value. That script is: gr.initialize();ResolutionNavigate to UI MacrosFilter for an open 'html_page_pm_home'Locate line 10: gr.newRecord();Replace this line with: gr.initialize();Save/Update