We use the project description section to share with the users of the project how to use the project correctly. Essentially, a step-by-step procedure can be found there. As a project can evolve, and we have everything being updated within a bundle, it would be really helpful to be able to update the project description as well, instead of it being static. One bundle can be used in 100+ projects for us as a small business.
Hi @David_Ryan , I can see how this could be useful but wouldn’t it also be dangerous that this could overwrite existing project descriptions or other important information within them?
I’m just curious; could you elaborate on how you would expect this feature to behave?
Sure, at this point, we have up to 2 different projects for each client, depending on what services we provide. One of the projects is quite complex and continues to be refined over time for every client (We love bundles). This means that we would need to update the description of how to engage the project if and when needed. It would give us more scope in what we can add in there and fine to replace the previous description.
Here is an example of one of the descriptions for our client projects.
Ah I see @David_Ryan , thanks for sharing.
So it appears you are using the project description as a generic guideline (which is great) that could be easily applied/updated to all projects since it does not contain specific project-related information.
I’m sure you know you can have this in your project template (step 2 in the template editor) but that will just include the most updated project description in only projects being created from the project template, going forward.
Don’t forget to vote for your own feedback - I did! (scroll to the top, on the left)