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

usability fixes #3 - Taranta

    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      People will use it with 

      • higher effectiveness
      • higher efficiency/productivity
      • better satisfaction
      Show
      People will use it with  higher effectiveness higher efficiency/productivity better satisfaction
    • Hide

      This feature is timeboxed. 

      I expect that  these user stories are covered (picked in this order). 

       

      Show
      This feature is timeboxed.  I expect that  these user stories are covered (picked in this order).  https://jira.skatelescope.org/browse/CT-321*timeline widget not working properly*. https://jira.skatelescope.org/browse/CT-303   There are at least 2 bugs to fix: one is the usability fix related to adding new devices, and also a bad behavior when dealing with 2+ devices. https://jira.skatelescope.org/browse/CT-296   investigation of blank canvas at the bottom of the editor and widgets not being configurable if put there The investigation was carried out and the necessary fixes were identified: one dealing with CSS and one dealing with missing ID params used by a React action. Now we need to fix this. https://jira.skatelescope.org/browse/CT-317**   Attribute writer input validation https://jira.skatelescope.org/browse/CT-318*Attribute writer style improvements* https://jira.skatelescope.org/browse/CT-319   Widget default size too small https://jira.skatelescope.org/browse/CT-238 Importing a dashboard that refers to non-existing widgets . This was dismissed/de-prioritized because the user is alerted that the dashboard is not valid. However the dashboard is not loaded at all, and a better solution would be to load it anyway, discard the invalid widget(s), alert the user.  
    • 2
    • 2
    • 13
    • 6.5
    • Team_CREAM
    • Sprint 3
    • Hide

      All implementation is done, all code is merged and available at:
      https://gitlab.com/tango-controls/web/taranta
      Test and coverage:
      https://ska-telescope.gitlab.io/-/webjive/-/jobs/1689434881/artifacts/build/coverage/index.html
      There is a recording of the system demo (start min 30 to 52) available at:
      https://skatelescope.zoom.us/rec/share/RaOdZcVhLaBU_S9UjSlqhbJZVpXLquAGAYiYEaT5MC17u8ucjapq35GwNV150zc2.9Hcietin3Cbkc4oE

      Show
      All implementation is done, all code is merged and available at: https://gitlab.com/tango-controls/web/taranta Test and coverage: https://ska-telescope.gitlab.io/-/webjive/-/jobs/1689434881/artifacts/build/coverage/index.html There is a recording of the system demo (start min 30 to 52) available at: https://skatelescope.zoom.us/rec/share/RaOdZcVhLaBU_S9UjSlqhbJZVpXLquAGAYiYEaT5MC17u8ucjapq35GwNV150zc2.9Hcietin3Cbkc4oE
    • 12.4
    • Stories Completed, 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 feature is the continuation (and hopefully completion) of "usability fixes #2": https://jira.skatelescope.org/browse/SP-1665.

      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. 

       

      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
          clones

          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-1665 usability fixes #2 - 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...

          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
                  Complete614.0
                  Total614.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel