Anonymous Login
2022-10-02 07:02 PDT

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000454v2.0 Release (Closed)[All Projects] Generalpublic2010-06-21 21:11
Assigned Tocaseydk 
Product Version 
Target VersionFixed in Versionv2.0.0 
Summary0000454: can't display user related task priority for single user, can't reset the same to normal
Descriptionsee both for description and patch
TagsNo tags attached.
Attached Files




opto (manager)

currently, there is no way to intentionally display all users on this page.
This can be changed the following way:

in reading the POST for $log_userfilter, use default 0

before the arrayselect for the displayed user list is called,
enter '0' => 'All users' to the array containing the user names.
If I remember right from what I did 6 weeks ago, this allows to select 'all users'.

Also, in my case, where the display of all users takes 100sec, I just use another default than 0 for my installation


caseydk (administrator)

Resolved differently than described but the same result in r1129.


opto (manager)

Last edited: 2010-06-01 07:57

sorry, the forum post also had another issue:

can't reset the user task priority to normal because there is an onchange event for the drop down list, if this is preset with normal in default display, it cannot be thrown by setting to normal.

In the current version, part of my proposal is there, but not all:
I see select user prio, high, normal, but no low.

Setting to high works, resetting to low does not.

if you change
$taskPriority[999]=$AppUI->_('Select User Priority');

and -1 to 999 in
    $tmpuser .= '<td align="center">' . arraySelect($taskPriority, 'task_priority', 'onchange="javascript:chPriority(' . $user_id . ');" size="1" class="text" title="' . $AppUI->_('Change Priority of selected Tasks') . '"', -1, true);

this is resolved.
beware, there is another location of this for the orphans, where it also needs to be changed.

No low in dropdown:
I intentionally set the set user priority to 999, because the priorities are centered around 0: low is -1 (at least in my dP conversion - is that nonstandard now?). And nobody (hopefully) will have +- 999 priority levels
So currently, the select ... at [-1] overwrites the low priority.


caseydk (administrator)

Thanks for the tips.
Resolved in r1131.

-Issue History
Date Modified Username Field Change
2010-05-31 11:20 opto New Issue
2010-05-31 11:20 opto File Added:
2010-05-31 11:45 caseydk Status new => assigned
2010-05-31 11:45 caseydk Assigned To => caseydk
2010-05-31 15:55 opto Note Added: 0000923
2010-05-31 20:29 caseydk Note Added: 0000925
2010-05-31 20:29 caseydk Status assigned => resolved
2010-05-31 20:29 caseydk Resolution open => fixed
2010-06-01 07:46 opto Note Added: 0000932
2010-06-01 07:46 opto Status resolved => feedback
2010-06-01 07:46 opto Resolution fixed => reopened
2010-06-01 07:51 opto Note Edited: 0000932
2010-06-01 07:57 opto Note Edited: 0000932
2010-06-02 19:50 caseydk Note Added: 0000938
2010-06-02 19:50 caseydk Status feedback => resolved
2010-06-02 19:50 caseydk Resolution reopened => fixed
2010-06-21 21:11 caseydk Status resolved => closed
2010-06-21 21:11 caseydk Fixed in Version => v2.0
+Issue History