Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1665

usability fixes #2 - Taranta

    XporterXMLWordPrintable

Details

    • Stories Completed, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • Taranta technical_debt usability

    Description

      We need to improve maturity of Taranta, and reduce its UX debt.

      This featue includes improvement in how th dashboard editor works, how widgets can be configured, how widgets can be placed in a dashboard, how dashboard are imported. See below for details. 

      NOTE: this feature can be thought of the continuation of a "usability fixes #1" which is https://jira.skatelescope.org/browse/SP-1699

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SS-8 Technical Debt - Feature Set

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done
          is cloned by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1868 usability fixes #3 - Taranta

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          supported by

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1699 look & feel guidelines for engineering UIs

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          mentioned in

          Page Loading...

          mentioned on

          GitLab Commit - SP-1665 updated webjive chart

          GitLab Merge request - SP-1665 Taranta usability fixes

          Structure

            Activity

              People

                g.brajnik Brajnik, Giorgio
                g.brajnik Brajnik, Giorgio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete816.0
                  Total816.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel