Content
View differences
Updated by Wieland Lindenthal about 3 years ago
# User Problem
## User
* 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?
* Where do you put final version of specifications?
* Where do you put contracts?
* Where do you put quotes and invoices?
* ...
## Pain
Assuming shared project folders (<mention class="mention" data-id="41400" data-type="work_package" data-text="#41400">#41400</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 the other projects.
* This is tedious, unnecessary work
* Error prone as it easy to forget something
## Solution
When setting up projects based on project templates we also allow to setup a default folder structure for its shared project folder.
* In the project template in OpenProject an admin can link a group folder. This folder serves as the template for a folder and file structure.
* When creating a new project based on a template the group folder of the project template is copied and linked to the newly created project. project.
## Out of Scope for the MVC
* Files are not part of the structure. This prevents creating duplicate documents. We want to foster the use of just one(!) template for all projects.
* No further refinement of access/sharing rights for sub-folders.
* File links that are present in the origin project (the template) do not (yet) get copied over to the target projects.
## Differentiation
I can't say how that differentiates us from competitors. The OpenProject-Nextcloud-Integration is pretty unique.
## Next iteration
* This is pretty much a "one shot". I don't see how this could get broken down into smaller iterations.
* We could consider, copying file links that belong to work packages of the origin project.
* file links targeting files in the origin project folder will get copied establishing a relationship between the copy of the work package and the copy of the linked file
* file links targeting files/folders outside the origin's project project folder fill get copied to the newly created work packages, however, they link to exactly the same file/folder (same origin file ID)
# Launch and Growth
## Measures
* People use that feature for project templates.
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-p op-uc-table--cell op-uc-table--cell_head">Headline</th><td class="op-uc-p op-uc-table--cell">Shared folder structures and file templates: structures: Easily find your files when working on many projects simultaneously. </td></tr><tr class="op-uc-table--row"><th class="op-uc-p op-uc-table--cell op-uc-table--cell_head">First Paragraph</th><td class="op-uc-p op-uc-table--cell">OpenProject's Nextcloud integration already introduced Nextcloud folders that are shared with all project members. That was already a huge step for every organization as this allows to have a clearly defined location for the digital assets of a project. Now, the integration goes one step further. Project templates can define a folder structure for those shared project folders. So every project that was created with such a template will have the same folder structure. This allows to implement a convention on how the files of a project a organized, saving time when searching for a file and reducing errors when saving them.</td></tr><tr class="op-uc-table--row"><th class="op-uc-p op-uc-table--cell op-uc-table--cell_head">Customer Quote</th><td class="op-uc-p op-uc-table--cell">At XYZ we handle more than 50 projects a year. Some people work on 5 projects at the same time. It is crucial to know where the project files are and where they shall get saved. OpenProject's templated shared folder structures helped our organization to reduce that uncertainty of where files were saved that we had before. </td></tr></tbody></table></figure>
## Go to market
_How are you planning on getting this into users' hands?_
## User
* 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?
* Where do you put final version of specifications?
* Where do you put contracts?
* Where do you put quotes and invoices?
* ...
## Pain
Assuming shared project folders (<mention class="mention" data-id="41400" data-type="work_package" data-text="#41400">#41400</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 the other projects.
* This is tedious, unnecessary work
* Error prone as it easy to forget something
## Solution
When setting up projects based on project templates we also allow to setup a default folder structure for its shared project folder.
* In the project template in OpenProject an admin can link a group folder. This folder serves as the template for a folder and file structure.
* When creating a new project based on a template the group folder of the project template is copied and linked to the newly created project.
## Out of Scope for the MVC
*
*
* File links that are present in the origin project (the template) do not (yet) get copied over to the target projects.
## Differentiation
I can't say how that differentiates us from competitors. The OpenProject-Nextcloud-Integration is pretty unique.
## Next iteration
* This is pretty much a "one shot". I don't see how this could get broken down into smaller iterations.
* We could consider, copying file links that belong to work packages of the origin project.
* file links targeting files in the origin project folder will get copied establishing a relationship between the copy of the work package and the copy of the linked file
* file links targeting files/folders outside the origin's project project folder fill get copied to the newly created work packages, however, they link to exactly the same file/folder (same origin file ID)
# Launch and Growth
## Measures
* People use that feature for project templates.
## Messaging
_If you were to write a press release, how would you describe the value to customers?_
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-p op-uc-table--cell op-uc-table--cell_head">Headline</th><td class="op-uc-p op-uc-table--cell">Shared folder structures and file templates:
## Go to market
_How are you planning on getting this into users' hands?_