MantisBT - v3.4 Release (Current)
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001739v3.4 Release (Current)Project Designerpublic2017-09-27 01:342019-01-03 12:53
Reporteropto 
Assigned Toopto 
PrioritynormalSeveritymajorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0001739: User Priority broken
DescriptionUser A owns task and is assigned. B is viewing the task.

A sets his user priority. On refresh on B's PC, (his) UP is set -> bug.
B cannot set his UP.

A assigns B to task. All UP is reset to normal. -> bug.
Now: A cannot set his UP. But B can set his UP.
If A refreshes screen, user B's UP is displayed as his UP.

If I remember correctly, A and B should be totally discoupled with respect to UP.
Both can set theirs individually, and it is only displayed to them.
TagsNo tags attached.
Relationships
Attached Files

Notes
(0003892)
opto   
2017-10-28 00:07   
the user priority table stores all UP with user_id.
getTaskTree has a joint for table user_tasks, but no addwhere for user id.
So always, the first table row for the task is shown. It might belong to the user being displayed, or it might not.
Thus, the confusion in displaying UP in project designer.
 
(0003895)
opto   
2017-10-29 11:51   
the fix caused a regression.

So: still not fixed
(0003897)
opto   
2017-10-29 15:32   
new try: add and with user_id into join:
        $q->addJoin('user_tasks', 'ut', 'ut.task_id = tasks.task_id AND ut.user_id = '.$this->_AppUI->user_id );

otherwise, the first record of ut with the task id is shown, but not necessarily the one for this user
(0003977)
caseydk   
2019-01-03 12:53   
In the 31 Dec 2018 release: http://docs.web2project.net/release-notes/3.4.html

Issue History
Date ModifiedUsernameFieldChange
2017-09-27 01:34optoNew Issue
2017-10-28 00:07optoAssigned To => opto
2017-10-28 00:07optoStatusnew => resolved
2017-10-28 00:07optoResolutionopen => fixed
2017-10-28 00:07optoNote Added: 0003892
2017-10-29 11:51optoStatusresolved => confirmed
2017-10-29 11:51optoNote Added: 0003895
2017-10-29 15:32optoStatusconfirmed => resolved
2017-10-29 15:32optoNote Added: 0003897
2019-01-03 12:53caseydkNote Added: 0003977
2019-01-03 12:53caseydkStatusresolved => closed