Last Modified: Jul 13, 2024
Affected Product(s):
BIG-IP APM
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10
Fixed In:
11.6.0
Opened: Jul 09, 2013 Severity: 3-Major Related Article:
K03051405
In custom report, you can select 'Assigned User' as a report. However, 'Assigned User' is actually reports logged-in user.
Returned values in the custom report are confusing. There are two columns: 'Login user name' and 'Assigned User'. These point to the same object: login user.
In custom report, select 'Assigned User' as a report.
There is no workaround other than not using 'Assigned User' as a report, or ignoring the 'Assigned User' column.
When user creates a custom report, the 'Assigned User' is no longer an available to select.