Uploaded image for project: 'OODT'
  1. OODT
  2. OODT-986

A React based new UI for OPSUI

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments


    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: opsui
    • Labels:
    • Skill Level:
      Committer (Medium) - This is for regular contributors/committers


      As of now, OODT provides a webapp to monitor component status, ingested files (and metadata) and workflow status through a wicket component (available under webapp directory) based UI. This UI lacks few important features like searching capability and lacks in stability at the moment. Furthermore, the existing UI is not user friendly and some occasions prints stack traces when errors occur in backend. To address all these loopholes, we are thinking of implementing a new UI based on a modetn front end framework.

      As of now, React is the suggested framework while other suggestions can be discussed as well. The original plan is to have a component based webapp, where individual components can be used out of the box when OODT based apps are being developed by users or embed/add these components to their existing webapps. When these components are developed individually, they can be integrated together to build the new OPSUI webapp.

      These UI wireframes were created by Tom Barber as a starting point. Some information on this issue is available under OODT-1001 as well.

      To support the web app developments, an existing set of REST APIs (JAX-RS) are available under webapp module. Few minor modifications may require to be made to achieve all the suggested functionalities from the new user interface.

      Please refer the following links for more information on OODT:


        Issue Links



            • Assignee:
              imesha Imesha Sudasingha


              • Created:

                Time Tracking

                Original Estimate - Not Specified
                Not Specified
                Remaining Estimate - 0h
                Time Spent - 1h 50m
                1h 50m

                  Issue deployment