Uploaded image for project: 'Serverless logic'
  1. Serverless logic
  2. SRVLOGIC-129

Jobs Service features, fixes, and enhancements available in the technical preview.

    XMLWordPrintable

Details

    • False
    • None
    • False
    • 0
    • 0% 0%
    • 2023 Week 15-17 (from Apr 10), 2023 Week 18-20 (from May 1), 2023 Week 21-23 (from May 22), 2023 Week 27-29 (from Jul 3), 2023 Week 30-32 (from Jul 24), 2023 Week 33-35 (from Aug 14), 2023 Week 36-38 (from Sep 4), 2023 Week 24-26 (from Jun 12)

    Description

      As discussed in the kogito runtimes meeting the this JIRA links the all the new remarkable work around the jobs service that will be available as part of the Serverless Logic technical preview, even when the jobs service is still in community.

      Attachments

        Issue Links

          causes

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. KOGITO-9705 Create test scenarios involving Job Service, API and its features

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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-9007 StateBasedNodeInstance not working with multiple instances including timers

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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-7945 Service Task hangs infinitely in the active state if it is after a subprocess

          • 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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8513 A job that must be fired immediately fails

          • 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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8552 Fix test issues in the SwitchStateEventConditionBasedIT

          • 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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8827 Issues bumping Quarkus 2.16.4

          • 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

          Bug - A problem that impairs or prevents the functions of the product. KOGITO-8880 Issue creating a new workflow instance with startFromNode and correlation

          • 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

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7983 Newsletter subscription example updates

          • 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

          Task - Represents a small unit of work that is not end-user facing. KOGITO-8820 Fix references in timeout guide and create a new section for timers and job service

          • 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

          Task - Represents a small unit of work that is not end-user facing. KOGITO-7984 Loan broker example updates

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

          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) KOGITO-8487 JodIdResolver factory

          • 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

              tdolphin-1 Tiago Dolphine
              wmedvede@redhat.com Walter Medvedeo
              Dominik Hanak Dominik Hanak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: