• Sign In
  1. Messages

16.3 to 18.2 Upgrade - Issue Tracker Differences

LabKey Support Forum

View Message

view list print
16.3 to 18.2 Upgrade - Issue Tracker Differences slatour  2018-11-12 07:08
Status: Closed
 

Hi LabKey,

When running a User acceptance test after upgrading to 18.2 from 16.3 we noticed that the issue tracker is no longer populated from all project users. We noticed that the assigned users list is populated only if a user belongs to a project group AND has an editor or higher role. What was the reasoning behind this change? As of current, some users are editors but since they do not belong to a specific project group we have added them ad hoc in an editor role, therefore they will no longer be populated in the assigned list for issue tracking in version 18.2.

Please advise,

-Sara
 
 
Jon (LabKey DevOps) responded:  2018-11-27 17:19
Hi Sara,

I tested out 16.3 and the behavior you're describing is the same as how you're saying 18.2 is behaving, so this is appearing to be by design.

When testing both versions, I'm seeing the same consistent behavior where the users need to be listed in a group for the project and they also need to be at least Editors or higher.

Are you certain that the previous behavior you were seeing didn't require this? The Issue Tracker for 16.3 is pretty much the same framework as 18.2, which include how the permissions function for assignment of issues.

Regards,

Jon
 
deniro tyvon responded:  2019-04-06 18:00
I'm seeing the same consistent behavior where the users need to be listed in a group for the project and they also need to be at least Editors or higher.