Skip to end of metadata
Go to start of metadata

UI Issues

  • links to documentation point to docs.acumos.org/en/latest instead of docs.acumos.org/en/athena  – that base URL really needs to be configurable by a properties file because it will change with each release
  • links, buttons to functionality that require a user to log in are enabled even when a user is NOT logged in - the UI pops up a window asking the user to sign in - better would be to not display the link or button unless the user is actually logged in (Manage Themes is visible in the Marketplace main view even when user is NOT logged in)
  • user account - trying to change my email address to one already in use doesn't even display a warning that the address is already in use and therefore can't be changed- just BAM immediately taken to the login page
  • other weird things.. like pressing the "Data Broker" button on the "Deploy to Azure" modal dialog triggers the "Please sign in to application" modal dialog and when I click OK the app logs me out and the Sign In screen appears and i'm forced to log in again
  • No explanation for Notification frequency in Account Settings - three choices (low, medium, high) but what do those mean? Low means I get notified when my model is onboarded and high means I get spammed?
  • Account Settings - the whole social media section has no explanation and then of course the social media sharing button on the Model Details page don't work.... probably because I don't have any social media accounts tied to my profile... but who knows? 
  • Ken encoutered an issue today one IST or maybe IST2 where the user name displayed in the upper R corner did not match the user's name on the Account Settings page...
  • no way to return to the Marketplace list from a Model Details page; have to either click the Marketplace left menu item, use the breadcrumgs, or use the browser back button - in all cases, the state of the marketplace list is lost
  • marketplace main page - sort by list - "sort by - all" - this means unsorted, and once you select a sort criteria, you cannot select unsorted again
    • sort by Created Date does not display the same results as Recent or Older selections, so explanation is needed as to exactly how these options work
  • marketplace main page - Tags
    • tags displayed on left side inner menu do not match the tags displayed in the models on the page (see screenshot in user guide)
  • session timeout management - numerous times I have been actively using the app and the app decides to log me out
  • acumos-challenge site; Acumos Property Assistant model, Deploy to Local - clicked "Download Solution Package" and received an error page
  • Marketplace main page: 

    • the Tag section of the marketplace is flaky; it takes a while to load, and sometimes no tags are displayed at all even though the displayed models clearly have tags
    • Tags area only displays tags based on the models displayed on the page, not the entire list of models. Also several times today the Tags list was blank even though the displayed models clearly had tags.
  • Themes -  "Choose your tags to customize your marketplace experience" but you cannot choose more than one tag; should have used a single-select list if that's the case

  • no way to return to the Marketplace list from a Model Details page; have to either click the Marketplace left menu item or use the browser back button - in both cases, the marketplace list state is lost
  • marketplace main page - sort by list - "sort by - all" - this means unsorted, and once you select a sort criteria, you cannot select unsorted again
    • sort by Created Date does not display the same results as Recent or Older selections, so explanation is needed as to exactly how these options work
  • marketplace main page - Tags
    • tags displayed on left side inner menu do not match the tags displayed in the models on the page (see screenshot in user guide)
    • in other cases, tags displayed on left side inner menu only reflect the tags in the models displayed on the current page instead of for all the models in the list (workaround: select a higher number of models be displayed on the page)
  • IST2 - clicking the notification bell does not open the list of notifications screen
  • Manage My Model - clicking on ellipsis pops up an empty tool tip type box
  • IST2: Publish model to company marketplace - status blobs never update; form doesn't clear/reset after model is published; if you click the Submit to Publication button again, a message pops up saying the model has already been published
  • ON-Boarding model - web onboarding - Status row does not reset after model is onboarded; status row does not reset when a new model is uploaded; status row does not reset when page is accessed after moving away to publish model and coming back to upload another model
  • Publish model is a long page. User has to scroll down to press the Publish button, but the system message is displayed at the top of the screen, so the user may miss the message; what about displaying the message next to the button that was pressed? 
  • Select **Add Model Name** to give the converted model a different name OR you can select the **Keep Model Name As It Is** checkbox to keep the model's current name; note: if you select to keep the model's name, both **Add Model Name** and **Keep Model Name As It Is** are disabled - that's kind of kludgy - users should be able to uncheck the box

  • PUBLISHING a model - adding a TAG
    • need to document workaround - the only place to add a tag is from the publishing page; DO NOT HIT ENTER in the Model tags field. Type your tag if it is not in the list and then click someplace else on the UI; you should see a "tag added" notification

  • SESSION TIMEOUT (IST2) - right in the middle of an action, Please sign in pop up
  • WEB-ONBOARDING (IST2) - notification bell icon does not update when on-boarding fails; tried to onboard DataMapper.zip from the DS wiki page, dockerize step failed but notification bell icon never updated to indicate a new message
    • when Onboarding fails at the Dockerize step, the addition of the model is not rolled back (ie, model it not deleted), so the "error" model is displayed in MY UNPUBLISHED MODELS but the user can't do anything about it
  • MY MODELS - tiled view doesn't fill up space so user has to "See All" to see the rest of the models
  • number of models displayed must be based on the "list" view  - still an enormous waste of screen real estate


Other Issues

  • Design Studio requires installer/operator/Admin to onboard and publish DS Toolkit Models; models stored on DS wiki
  • Testing
    • Nobody from the "business" side (stakeholders) is writing UAT cases and doing UAT
    • Not all the requirements are in Jira user stories so the test team is not able to fully test functionality
    • installed instances act differently; need a definable, repeatable procedure to ensure standardization across test instances
      • Solution: Ken is working on the scripts and Ken/Bobbie the guide
    • Jira needs to be modified so test cases can be created under use stories; also need test management plugin so traceability matrix can be done inside Jira
      • Ken asked Akash? to look into this
  • Docs
    • Portal user guide is not being updated by Portal team when new functionality is added or existing is changed
    • Severe lack of explanation on what UI fields mean; for example: 
      • Deploy to Cloud databrokers area
      • Marketplace - Sort By - what the difference between Created Date, Recent, and Older because each displays a different sort order; plus what do Highest Reach and Lowest Reach choices mean?
    • Suggested solution:  each use story that impacts end user functionality must have a documentation task that is completed at the same time the code is committed; the test and docs team will verify the documentation and open a bug if it's missing or incomplete
  • Release process
    • not all components were promoted to  release
    • Solution:  update the PTL guide to include release activities so PTLs know they are responsible for promoting their components to the release nexus.
  • Test reports/weekly build release notes
    • they never listed what versions of the onboarding clients (Java, Python, R) were being used (ie, certified to work with platform version xxx), nor did they list *all* the libraries/versions (only the ones deployed as images that dont't need to be started.. but never, for example, the version of the common data services client or the nexus client, which are imported as libraries in the java source code...).
    • Solution: working with Ken/Sai and testing team to include this info this going forward
  • UI changes need to signed off to prevent churn from stakeholders
    • Major UI functionality, like the search - the need to have comprehensive requirements and design, and have them signed off by the stakeholders prior to implementation. OpenStack has the concept of a blueprint. Acumos could have a separate "blueprint" repo. Requirements/Design docs would be created in RST and along with supporting design images (both source and exported PNG**) pushed to gerrit like any other patch. Stakeholders and PTLs would have to review the blueprint in gerrit (great way to track comments) and +1 would indicate sign-off. Then the jira ticket would reference the requirement/design doc in the repo (no ppt decks or word docs attached to jira epics and user stories). 
      • ** draw.io can be used to create the diagrams. tspace incorporated it a while ago. the acumos wiki has the plugin. also there is a desktop version for mac, windows, linux 

  • No labels