Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Routing Architecture Refactor

Description

Current state of routing relies on queries and as result routing is

  • Not scalable

  • Not Performant

  • Results in numerous bugs due to queries and state management

  • App Maintenance - Developer Level - more difficult - more dependent to support navigation support.

  • Not Accessibility

  • Limits User experience

    • Unable to display a detail record in Full View

    • Unable to do hierarchy result list layout needed for Inventory

Need to refactor so that routing relies on browser/links not queries

Priority

Labels

Fix versions

Development Team

Stripes Force

Assignee

Solution Architect

Parent

Parent Field Value

None

Parent Status

None

relates to

requires

Checklist

hide

TestRail: Results

Activity

Show:

Cate Boerema February 6, 2019 at 1:14 PM

Thanks , and . I marked this as an NFR.

Theodor Tolstoy (One-Group.se) February 6, 2019 at 9:31 AM

should we make this into a NFR?

Anya February 1, 2019 at 5:40 PM

FC is in agreement with - not ranking

Kristin Martin January 30, 2019 at 7:58 PM

This seems like a NFR, so Chicago is not ranking.

Done

Details

Reporter

Potential Workaround

HK: Workaround, Use Stripes "as-is" for now and fix on a future release in 2nd half of 2020

PO Rank

101

Front End Estimate

XL < 15 days

Front End Estimator

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created January 11, 2019 at 7:58 PM
Updated October 29, 2019 at 7:47 PM
Resolved October 29, 2019 at 7:47 PM
Configure
TestRail: Cases
TestRail: Runs