MantisBT - v3.2 Release
View Issue Details
0001552v3.2 ReleaseTaskspublic2014-05-26 03:382014-07-16 21:30
Assigned Tocaseydk 
PrioritynormalSeveritymajorReproducibilityhave not tried
PlatformOSOS Version
Product Version 
Target Version3.2Fixed in Version3.2 
Summary0001552: tasks per user sql totally (?) broken
Descriptionfeature (I will do): display only projects in progress, maybe have checkbox for others.
Currently, not defined is displayed as well

bug: multiple occurance of same task.
|-moduletester is a subtask.

in this window, it is displayed as


and a few lines further down for same project as:

another example from daily life:

project FFFFF is complete. Three tasks are not finished.
Actually, that happens. The customer does not seem to bother and has paid.
I would like to keep them unfinished in w2p so we know if he should have a request.
I want these tasks to disappear from my tasks and tasks per user, because project status is complete
TagsNo tags attached.
related to 0001561new  Pending Requests Task per user shows tasks for all active projects, should filter by status 
Attached Files

2014-06-02 22:19   
Is this an annoyance or does it prevent the form from working as expected?

I ask because the task display in general needs a lot of refactoring. I'm trying to hold off on that for v4.0 to do it once instead of partial solutions now.
2014-06-06 13:24   
I think the multiple occurance of tasks is more than an annoyance.

If a user doesn't know the project structure well, it is not clear whether the tasks are doubletts.

The subtasks moduletester is dispalyed as:


and a few lines down as:


is this the same task? or another with same name? How shouuld my employees know?

I think this window does not display the desxcription popup - that would help.
2014-06-12 22:12   
The duplicate task issue is resolved in development:
2014-06-12 22:14   
The rest of this issue related to only displaying certain project statuses is a feature request, so I'm creating a related issue and attaching it here: 0001561
2014-06-12 22:14   
The bug portion is resolved in development, the rest is separated out as a feature request.

Issue History
2014-05-26 03:38optoNew Issue
2014-05-26 03:46optoDescription Updatedbug_revision_view_page.php?rev_id=51#r51
2014-06-02 22:19caseydkNote Added: 0003411
2014-06-02 22:19caseydkAssigned To => caseydk
2014-06-02 22:19caseydkStatusnew => feedback
2014-06-06 13:24optoNote Added: 0003415
2014-06-06 13:24optoStatusfeedback => assigned
2014-06-10 22:09caseydkTarget Version => 3.2
2014-06-12 22:12caseydkNote Added: 0003454
2014-06-12 22:14caseydkNote Added: 0003455
2014-06-12 22:14caseydkRelationship addedrelated to 0001561
2014-06-12 22:14caseydkNote Added: 0003456
2014-06-12 22:14caseydkStatusassigned => resolved
2014-06-12 22:14caseydkResolutionopen => fixed
2014-06-12 22:15caseydkFixed in Version => 3.2
2014-07-16 21:30caseydkStatusresolved => closed