Users App (UXPROD-784)

[UXPROD-2092] Improved "Fielded" searching in User app Created: 01/Oct/19  Updated: 03/Jan/24  Resolved: 11/Nov/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021
Parent: Users App

Type: New Feature Priority: TBD
Reporter: patty.wanninger Assignee: Annika Schröer
Resolution: Done Votes: 0
Labels: round_iv, ui-only, users
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-2760 Improved searching in User app with E... Open
Defines
is defined by UIU-1706 Add search type: Last name Closed
is defined by UIU-1707 Add search type: Username Closed
is defined by UIU-1708 Add search type: Barcode Closed
Epic Link: Users App
Front End Estimate: Small < 3 days
Back End Estimate: Small < 3 days
Development Team: Leipzig

 Description   

In order to create efficient workflows, the searching for Users in User Management needs additional features:
1.) explicit truncation (requirement covered in stories below) (The feature was split to UXPROD-2760 Open )
2.)the abilty to limit a search to an particular index, e.g., Last name ( UIU-1706 Closed ), username ( UIU-1707 Closed ), barcode ( UIU-1708 Closed ), external system id ( UIU-1363 Open )
3. add the ability to search/filter departments. (out of scope for this feature - see UIU-1355 Closed )

Wireframe: https://drive.google.com/file/d/1v9BAMunYLCF8VAJB8IY45btEEdnTqYiR/view?usp=sharing

Per discussion on 2020-06-29, RA SIG thinks this is higher priority than Boolean/Query searching in Users ( UXPROD-1015 Draft ). This will cover most common use cases and requires less training.



 Comments   
Comment by Cate Boerema (Inactive) [ 07/May/20 ]

Bohdan Suprun and Michal Kuklis could you please estimate this feature? Thanks much!

Comment by Bohdan Suprun (Inactive) [ 08/May/20 ]

Hi Cate Boerema,

The 1-2 should not require a lot of backend work, just to make sure that all indexes are in place.

The 3rd one, is it a new field to add? I don't see any department field on user record.

Comment by Cate Boerema (Inactive) [ 11/May/20 ]

Good catch, Bohdan Suprun.

patty.wanninger, can you please move the "ability to search on departments" into the Department feature (which would then need to be re-estimated to include this additional work) or create a separate feature for filtering by departments? I'll X it out of this feature for now so this one can be estimated.

Comment by Cate Boerema (Inactive) [ 13/May/20 ]

Michal Kuklis can you please add a frontend estimate for this?

Comment by Michal Kuklis [ 13/May/20 ]

Sorry Cate Boerema I missed this. It should be now done. I think if we take a similar approach to what has been done in ui-inventory then this should be a pretty quick change on the UI.

Comment by Holly Mistlebauer [ 17/Jun/20 ]

Cornell comment from Round IV Outliers spreadsheet: This outlier is a showstopper for Cornell

Comment by Cate Boerema (Inactive) [ 19/Jun/20 ]

patty.wanninger can you say more about what users are expecting with "explicit truncation"? They want to have to search for "John*" in order to find "Johnson"?

Comment by Erin Nettifee [ 22/Jun/20 ]

Does the scope of this also include searching custom fields, or is there another jira for that? patty.wanninger

Comment by Charlotte Whitt [ 24/Jul/20 ]

Hi Erin Nettifee patty.wanninger - sorry for being late to the party re. this question which Erin raised above: re. ability to search custom fields.

Khalilah Gambrell - when you and your team defined the Custom fields concept - UXPROD-33 Closed - then how did you envision making these tenant configured data elements search able.

I can see how this would also be very relevant for when we plan to do the implementation of Custom fields in Inventory - UXPROD-2211 Draft .

CC: lew235

Comment by Khalilah Gambrell [ 24/Jul/20 ]

Erin Nettifee, patty.wanninger, lew235, and Charlotte Whitt, custom fields searching is already supported by the backend. To be honest, I have not given a lot of thought on the custom field searching/filtering other than the following:

  1. Tenants need the ability to select which custom fields are eligible for keyword searching and as a fielded search. (My assumption is each tenant can do this now but not via a UI. But I need to confirm.)
  2. AND/OR may want to support a feature similar to how Agreements handles custom field search/filter
    Unable to render embedded object: File (screenshot-1.png) not found.
Comment by patty.wanninger [ 17/Sep/20 ]

User Management SIG agreed that the current searching in users covers required use cases. The RA SIG also reviewed and agreed. So we are not pursuing the development of this feature at this time. 9/16/2020

Comment by Björn Muschall [ 05/Oct/20 ]

Per discussion with A.-M.: If there's a general keyword search box in Users (in addition to fielded searches), then it would be good to be clear about which fields the general search box covers, similar to Inventory keyword search.

UM SIG now agreed that Leipzig dev-team will be developing this feature.

Comment by Cate Boerema (Inactive) [ 05/Oct/20 ]

Changed dev team from Core Functional to Leipzig

Comment by Annika Schröer [ 06/Oct/20 ]

Moved to Leipzig for development, as discussed with patty.wanninger.

Comment by Annika Schröer [ 17/Oct/20 ]

Reset all rankings on 2020-10-17, as the feature was split.
This feature only deals with Fielded searching in the users app. For explicit truncation see UXPROD-2760

Generated at Fri Feb 09 00:21:04 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.