Newly Created Records Should be In Focus

Description

Purpose: To put newly created records (e.g. users, items) in focus so that you can see your record was successfully created and make any changes (such as adding permission sets). We initially thought we might not want to display a newly created record that potentially conflicts with the search and filters, but we've decided it may not be that bad and is worth trying out and getting some user feedback.

Scenarios:

  1. Scenario

    • Given the Users App

    • When I have created a new user

    • Then:

      • The new user is in focus in the right hand panel

      • Any search or filter applied prior to the new record being created will still be displayed and applied to the search results, even if they conflict with the newly created record

  2. Scenario

    • Given the Items App

    • When I have created a new item

    • Then:

      • The new item is in focus in the right hand panel

      • Any search or filter applied prior to the new record being created will still be displayed and applied to the search results, even if they conflict with the newly created record

      • Unless the record is displayed in the result set, no record in the result set should be highlighted

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Mike Taylor June 22, 2017 at 10:29 PM

Closing this now, since the ui-users and ui-items blockers have both been closed.

Mike Taylor June 21, 2017 at 4:41 PM

The new ui-users issue is ("Newly created user records should be in focus")

Mike Taylor June 21, 2017 at 4:39 PM

I'm going to make a specific issue to trial this for ui-users; then if it's successful, I'll make a separate issue for porting to ui-items. (For now, I will choke down my discomfort about the increasing amount of duplicated logic between those two modules.)

Mike Taylor June 21, 2017 at 4:39 PM

I think there is a way forward, using the new props.resources.users.successfulMutations, but the details will need careful thinking through.

Mike Taylor June 12, 2017 at 1:25 PM

As discussed on the call, I am not necessarily expecting to fix this, at least not in the present sprint. I'm just going to look into it, and figure out whether the STRIPES-111 work gives us an easy solution.

Flagged
Done

Details

Assignee

Reporter

Priority

Sprint

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created April 4, 2017 at 9:31 AM
Updated July 11, 2017 at 10:49 AM
Resolved June 22, 2017 at 10:29 PM
TestRail: Cases
TestRail: Runs