Content
View differences
Updated by Parimal Satyal 3 days ago
**As** an OpenProject project admin
**I want to** easily understand the sharing options of versions
**so that** I don't need to think too much about it
#### **Acceptance criteria**
In Project settings → Versions → {a version},
* Bring the settings down from five to three, like we did for sprints:
* Not shared
* With subprojects
* ~~With project hierarchy~~ (remove)
* ~~With project tree~~ (remove)
* With all projects
* Present the three The options in an [Advanced Radio Button Group](https://qa.openproject-edge.com/lookbook/inspect/OpenProject/Common/advanced_form_inputs/advanced_radio_button_group?_display=%257B%257D), with the following text and icons:
* **Option 1:**
* Title: "Not shared"
* Text: "This version is only visible to this project."
* Icon: _(SVG export to be added)_
* **Option 2:**
* Title: "Share with subprojects"
* Text: "This version can be used by this project all of its subprojects."
* Icon: _(SVG export to be added)_
* **Option 3:**
* Title: "Share with all projects"
* Text: "This version can be used by any project in this instance."
* Icon: _(SVG export to be added)_
* **\[open\] Migration:** For users using the other two options (share with project hierarchy or share with project three), move the versions to a higher-level project such that this hierarchy can still be respected using the "Share with subprojects" option.
####
#### **Technical notes** are currently:
* <br>
#### **Permissions and visibility considerations**
* _tbd_
#### **Translation considerations**
* _tbd_
#### **Out of scope**
####
#### Archive of original post from Christophe
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924666/content">
Currently, the options are:
* Not shared
* With subprojects
* With project hierarchy
* With project tree
* With all projects
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924666/content">
Some are hard to differentiate.
Using some graphics to illustrate which projects would have access to the version would make it easier to understand and select.
Proposition: radio panels with illustrations of a project list, hightlighting which ones would be able to use the shared version. Icons should be distinguishable for color-blind people.
Mockup proposition:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924667/content">
**Acceptance criteria**
* <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** easily understand the sharing options of versions
**so that** I don't need to think too much about it
#### **Acceptance criteria**
In Project settings → Versions → {a version},
* Bring the settings down from five to three, like we did for sprints:
* Not shared
* With subprojects
* ~~With project hierarchy~~ (remove)
* ~~With project tree~~ (remove)
* With all projects
* Present the three
* **Option 1:**
* Title: "Not shared"
* Text: "This version is only visible to this project."
* Icon: _(SVG export to be added)_
* **Option 2:**
* Title: "Share with subprojects"
* Text: "This version can be used by this project all of its subprojects."
* Icon: _(SVG export to be added)_
* **Option 3:**
* Title: "Share with all projects"
* Text: "This version can be used by any project in this instance."
* Icon: _(SVG export to be added)_
* **\[open\] Migration:** For users using the other two options (share with project hierarchy or share with project three), move the versions to a higher-level project such that this hierarchy can still be respected using the "Share with subprojects" option.
####
#### **Technical notes**
* <br>
#### **Permissions and visibility considerations**
* _tbd_
#### **Translation considerations**
* _tbd_
#### **Out of scope**
####
#### Archive of original post from Christophe
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924666/content">
Currently, the options are:
* Not shared
* With subprojects
* With project hierarchy
* With project tree
* With all projects
Using some graphics to illustrate which projects would have access to the version would make it easier to understand and select.
Proposition: radio panels with illustrations of a project list, hightlighting which ones would be able to use the shared version. Icons should be distinguishable for color-blind people.
Mockup proposition:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/924667/content">
**Acceptance criteria**
* <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._