Settings and activity
2 results found
-
421 votes
Hi community, some time passed since our last update in the thread here we do want to return and share - while our product teams explored possibilities for how we might represent Purchase Orders in Projects research has confirmed that there is underlying work needed to the platform Purchase Orders are built on before we can achieve any good outcomes of your needs here.
We have enthusiasm and a close eye remaining on the support for this, but want to be honest that this is not something that we’ll be able to focus our attentions on in the near future.
Once we have completed work first needed in the Purchase Orders space we can reassess how to integrate purchase Orders into Projects and will update you all of steps forward, here.An error occurred while saving the comment An error occurred while saving the comment 
Maggie Strevens
commented
This is an essential function for our Business, hope to see it implemented soon...
Maggie Strevens
supported this idea
·
-
176 votesMaggie Strevens
supported this idea
·
It would be extremely handy to add Purchase Orders (POs/WO's) to a project, but with a specific restriction: they should not be "costed" until they become actual Bills.
This feature would be beneficial because it would reduce the amount of double handling we currently experience. Unfortunately, the current setup of the Projects add-on involves quite a bit of redundant effort.
By allowing POs to be linked to a project but only impacting the project's cost once they are converted into Bills, we can ensure more accurate project costing and efficiency in our processes.
I believe this change would significantly improve our workflow and reduce unnecessary administrative tasks.