Content
View differences
Updated by Jens Ulferts about 3 years ago
### Steps to reproduce
_Please write down the steps to reproduce. Try to write down all necessary preconditions (what permissions do you have, are other users involved?). Example:_
1. Have two projects (PA and PB)
1. In PA, create a work package
2. wait until the aggregation time is over
3. Move the work package to project PB
2. Have a user with permissions to see work packages in PA but not in PB
3. Filter for work packages with at least one timestamp before moving the work package to PB
### What is the buggy behavior?
_Please describe the bug in as much detail as possible. Example:_
* The work package is not returned
### What is the expected behavior?
_Describe how the application should behave like. Example:_
Copied from #26448 : #26448:
> * When a work package has been moved from one project to another, the set of users who has access to view it might also change (depending on each users permissions' in the new vs the old project). When show changes is activated and the user viewing has the necessary permissions to view it:
> * in the past and in the present
> * No special rule
> * in the past but _not_ the present
> * Show a "-" (grey, removed from view) change
> * Replace new values with a dash "-" (since we cannot show the new values)
> * It would be like the work package has been deleted
> * in the present but _not_ the past
> * Show a "+" (green, added to view) change
> * Show both previous and new values (since if user navigates to the work package show page, the whole history will be displayed, so these values are available)
> * It would be as if the work package has been created.
> * has permissions to view it in neither project:
> * Work package is not displayed at all
_Please write down the steps to reproduce. Try to write down all necessary preconditions (what permissions do you have, are other users involved?). Example:_
1. Have two projects (PA and PB)
1. In PA, create a work package
2. wait until the aggregation time is over
3. Move the work package to project PB
2. Have a user with permissions to see work packages in PA but not in PB
3. Filter for work packages with at least one timestamp before moving the work package to PB
### What is the buggy behavior?
_Please describe the bug in as much detail as possible. Example:_
* The work package is not returned
### What is the expected behavior?
_Describe how the application should behave like. Example:_
Copied from #26448 :
> * When a work package has been moved from one project to another, the set of users who has access to view it might also change (depending on each users permissions' in the new vs the old project). When show changes is activated and the user viewing has the necessary permissions to view it:
> * in the past and in the present
> * No special rule
> * in the past but _not_ the present
> * Show a "-" (grey, removed from view) change
> * Replace new values with a dash "-" (since we cannot show the new values)
> * It would be like the work package has been deleted
> * in the present but _not_ the past
> * Show a "+" (green, added to view) change
> * Show both previous and new values (since if user navigates to the work package show page, the whole history will be displayed, so these values are available)
> * It would be as if the work package has been created.
> * has permissions to view it in neither project:
> * Work package is not displayed at all