Specification similar to the copying of projects having Nextcloud project folder(s) but with SharePoint.
To be detailed.
# User Problem
## User
_What persona, persona segment, or customer type experiences the problem most acutely?_
* Project manager
## Problem
When switching between projects it can get very tedious to find files if there is not a common folder structure for all projects of the same kind.
_Example_:
* Where do you put files related to work packages? Project member * Where do you put final version of specifications? Product owner * Where do you put contracts? Customer * Where do you put quotes and invoices?
....
## Problem
_What problem or job does the user have?_
* ...
*
## Pain
Assuming shared project folders (<mention class="mention" data-id="50988" data-type="work_package" data-text="#50988">#50988</mention>) were implemented. When setting up a new project with a shared folder a project manager would first need manually(!) setup a folder structure, similar to _What is the other projects. primary workaround that users perform that we could remove or replace? Why is it painful?_
* This is tedious, unnecessary work .... * Error prone as it easy
# Business Case
## Reach
_About how many users, customers or potential customers currently have this problem? (Low / Worst Case)_
> Add this value to forget something the custom field and delete this section.
## Solution Impact
When setting up projects based on project templates we also allow _Among relevant customers or prospects, how much value do they get from a comprehensive solution to setup a default folder structure for its shared project folder. this problem? (Conservative case)_
* In > Add this value to the project template in OpenProject an admin custom field and delete this section.
## Confidence
_What are the top risk factors that could inhibit our ability to deliver this solution? Please consider how we can link a group folder. This folder serves as mitigate these risks._
> Add this value to the template for a folder custom field and file structure.
* When creating a new project based on a template delete this section.
## Urgency and Priority
_What is the group folder relative priority of this opportunity in your backlog? What tradeoffs must you make? Is there a hard deadline or could this wait?_
> Add this value to the project template is copied custom field and linked to the newly created project. delete this section.
### Acceptance criteria ## Solution
1. `Project folder` checkbox is selected during a project copy process.
2. After _How do we solve the copy user’s problem. What is finished our “pain killer”? What must we have a copy achieve in the first version of the project folder setup solution in _SharePoint_. order to achieve value for the user?_
* .... 3. File links that are present *
## Out of Scope for the MVC
_What should NOT be in the origin project (the template) minimal viable change, and reference a file **inside** can be considered for future iterations? Why? Please order them by importance._
* ...
## Differentiation
_What do you believe will differentiate us from the origin project folder do get copied over current experience or competitive experiences?_
* ...
## Next iteration
_What is the next solution that would allow us to the target projects release meaningful customer value quickly?_
* ...
*
# Launch and Growth
## Measures
_How will link you know you solved the fresh copy of problem? Please list measurable, quantitative indicators (preferred) or qualitative ways you plan on assessing the file.
4. File links that are present in the origin project (the template) and reference solution?_
* ...
## Messaging
_If you were to write a file **outside** press release, how would you describe the origin project folder will get copied but will reference the original file. value to customers?_