Reference Number Changing

[RebeccaJo1]

We noticed that the reference number assigned to an issue is now changing once converted to a project. Anyone else have this problem? 

[KatherineLa]

Each record in WF has an associated reference number, but I wouldn't expect the reference number of the original issue to change. The resulting project would have it's own separate reference number though. Are you seeing the original issue's number changing? 

[Doug_Den_Hoed__AtAppStore]

Hi @RebeccaJo1 and @KatherineLa,

It's possible you're both right: Workfront can be configured to either preserve or delete an Issue when it is converted to a Project. Technically, the Project is its own "row" with its own ID and Reference Number, which (if "delete" were the case) could easily appear as if the Reference Number had changed.

Regards,

Doug

[RebeccaJo1]

@KatherineLa 

 The reference number changes multiple times. After I submit, the request creates the 1st one, then I go to "Covert to project from template" and that shows a different reference number. Then I hit "Convert" and the now project shows another new reference number.

[RandyRoberts]

That's because you're creating a new database entry with each conversion, with its own ref number.

If you preserve the original issue as Doug mentioned, you can reference it with the resolvable object on the new object.

[kautuk_sahni]

@RebeccaJo1 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!