Content
View differences
Updated by Parimal Satyal over 1 year ago
**As** a project member
**I want to** be able to see that a work package has a relation, and the dates of that related work package
**even if** I don't have the permissions to view the details of that work package
**so that** I have the necessary context to why a work package is scheduled in a certain way
**Note**
This feature requires the Primerisation of the relations tab: ##22360
**Acceptance criteria**
* In the _Relations_ tab in work packages or the date picker:
* Show entries for related work packages that the current user does not have the permission to view
* Do not show/leak any information other than:
* Start date
* Finish date
* Lag (if present)
* Show these additional information only for the following relation types:
* Predecessor: start date, finish date, lag
* Sucessor: start date, finish date, lag
* Children: start date, finish date
* For the above relations, if a date missing (start date and/or finish date) we will nevertheless show the relevant icon with a dash (-) to indicate what is missing.
* If lag is not set (or if it is set to 0), do not show lag information.
* If start and finish dates are the same, show them as a single date (not a range).
* _This will also mean we will not necessarily leak info about a work package being a milestone; it could just as well be a work package with the same start and finish dates._
* For other relations (like 'Related to', 'Blocked by', 'Requires...'), do not show the dates, if present.
* These "ghost relations" appear different from other relations:
* They are more muted and cannot be interacted with
* They tell the user that the work package is invisible to them due to permissions
* See visuals/Figma for how this should be represented
**Figma**
workPackageValue:"Figma wireframes"
**I want to** be able to see that a work package has a relation, and the dates of that related work package
**even if** I don't have the permissions to view the details of that work package
**so that** I have the necessary context to why a work package is scheduled in a certain way
**Note**
This feature requires the Primerisation of the relations tab: ##22360
**Acceptance criteria**
* In the _Relations_ tab in work packages or the date picker:
* Show entries for related work packages that the current user does not have the permission to view
* Do not show/leak any information other than:
* Start date
* Finish date
* Lag (if present)
* Show these additional information only for the following relation types:
* Predecessor: start date, finish date, lag
* Sucessor: start date, finish date, lag
* Children: start date, finish date
* For the above relations, if a date missing (start date and/or finish date) we will nevertheless show the relevant icon with a dash (-) to indicate what is missing.
* If lag is not set (or if it is set to 0), do not show lag information.
* If start and finish dates are the same, show them as a single date (not a range).
* _This will also mean we will not necessarily leak info about a work package being a milestone; it could just as well be a work package with the same start and finish dates._
* For other relations (like 'Related to', 'Blocked by', 'Requires...'), do not show the dates, if present.
* These "ghost relations" appear different from other relations:
* They are more muted and cannot be interacted with
* They tell the user that the work package is invisible to them due to permissions
* See visuals/Figma for how this should be represented
**Figma**
workPackageValue:"Figma wireframes"