Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-2848

Usage Stats for actual used features

    XMLWordPrintable

Details

    Description

      We currently know that people are using JBDS/JBoss Tools but not specifically which features people are actively using. Our key base metric is "daily usage".
      Areas worth tracking include (in priority order):

      • Use of the OpenShift Wizard to successful completion vs error
      • Use of the archetypes on JBoss Central (adding Hybrid/Cordova in JBDS 8)
      • Successful installation of the features found on Software/Update tab of JBoss Central
      • Use of the JSF/RichFaces Visual Page Editor
      • Use of the Hibernate Tooling
      • Use of the jQuery Mobile Palette
      • Use of BrowserSim
      • Use of CordovaSim

      We will also need to update http://www.jboss.org/tools/usage and https://devstudio.jboss.com/usage/

      Ideally, we would be able to distinguish between a single "hit" (end-user opened the tool) vs active usage (end-user spent repeatedly using the tool)

      Our metric gathering service should be "scalable" enough to allow for tracking of the individual SOA features such as Drools, jBPM, Switchyard, Camel, etc in the future.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBIDE-16800 Add usage tracking for server creation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBDS-2732 Add usage tracking for installs from JBDS central

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Feature Request - Feature requests from customers and/or users JBIDE-17520 Usage tracking for servers created via runtime detection

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-17232 Usage Stats for used wizards

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users JBIDE-17305 Usage stats for visual page editor/preview/browsersim

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users JBIDE-17320 Usage stats for cordovasim launches

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users JBIDE-16906 Track successful/unsuccessful installations from JBoss Central

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Task - Represents a small unit of work that is not end-user facing. JBIDE-17260 Review what we track via usage component

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. JBIDE-17233 Add usage tracking for the WS Tester

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-17458 Usage stats for browsersim/cordovasim: webkit vs JavaFX

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              alexeykazakov Alexey Kazakov
              bsutter@redhat.com Burr Sutter
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: