Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-4416

[Stunner] Connectors usability improvements

    XMLWordPrintable

Details

    • Connectors usability issues
    • False
    • False
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, User Experience
    • Done
    • 100
    • 100% 100%
    • Undefined
    • ---
    • ---

    Description

      Goals

      This epic's main goal is to improve the editors' usability and end user experience when dealing with connectors, also fix some known issues as well.

      This epic contains links for each for the enhancement, feature requrest or issue, in scope (see incorporates linked tickets).

      Main areas to focus on: 

      • 1) Line splicing - KOGITO-5274
      • 2) Additional issues - See other incorporated tickets

      Scope

      Targeting both BPMN and DMN editors, on all existing kogito channels.

      BC editors not in scope.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-5091 VSCode DMN, BPMN editor - creating connection can't be cancelled easily

          • 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

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. KOGITO-5274 Stunner - Line splicing

          • 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

          Bug - A problem that impairs or prevents the functions of the product. RHPAM-2600 Stunner - Connector lines can obscure icons

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              romartin@redhat.com Roger Martinez
              mfentane@redhat.com Myriam Fentanes
              Dominik Hanak Dominik Hanak
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: