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

QE serverless logic feature verification for first iteration of the tooling

    XMLWordPrintable

Details

    • QE serverless logic #1 - feature verifcation
    • False
    • None
    • False
    • To Do
    • 100
    • 100% 100%
    • ---
    • ---

    Description

      Collection of tasks required for complete feature verification for development preview number one. See links.

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

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. SRVLOGIC-16 [use case] Local developer experience for writing, testing, and troubleshooting workflows

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

          Task - Represents a small unit of work that is not end-user facing. SRVLOGIC-27 [deliverable] Serverless workflow editor MVP in VS Code

          • 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.
          • 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-7732 QE serverless logic tasks for second iteration of the tooling

          • Critical - To be worked on immediately following BLOCKER issues.
          • 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-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

          Activity

            People

              dhanak@redhat.com Dominik Hanak
              dhanak@redhat.com Dominik Hanak
              Tomas David Tomas David
              Tomas David Tomas David
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: