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

QE serverless logic tasks for second iteration of the tooling

    XMLWordPrintable

Details

    • QE serverless logic #2
    • False
    • None
    • False
    • In Progress
    • 100
    • 100% 100%
    • ---
    • ---

    Description

      Summary
      Collection of tasks required for complete feature verification for development preview number two.

      Include any issue & task related to the milestone.
      Include &Link found bugs;

      Examine links.
      Blocked requirements are considered verified once this EPIC is DONE.

      Acceptance criteria
      Underlying Tasks are DONE/RESOLVED.
      Linked BUGS are fixed, unfixed issues need to be grouped under engineering epic for further fixing.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. SRVLOGIC-34 [deliverable] Serverless logic DevUI DP2 improvements

          • 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 - Capability or a well-defined set of functionality that delivers business value. Features can include additions or changes to existing functionality. Features can easily span multiple teams, and potentially multiple releases. SRVLOGIC-1 [core] New visualization of workflows in editor

          • 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
          is related to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-7117 QE serverless logic infrastructure for first iteration of the tooling

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-7121 QE serverless logic feature verification for first iteration of the tooling

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

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. KOGITO-8059 QE serverless logic tasks for third iteration of the tooling

          • 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.
          • Resolved

          Activity

            People

              dhanak@redhat.com Dominik Hanak
              dhanak@redhat.com Dominik Hanak
              Barbora Siskova Barbora Siskova
              Barbora Siskova Barbora Siskova
              Barbora Siskova, Jan Stastny, Lubomir Terifaj, Tomas David, Zbynek Drapela
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: