Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-8500

PIM doesn't account for different source and target process id

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Critical
    • None
    • 7.22.0.Final
    • Migration
    • NEW
    • NEW

    Description

      Currently it seems that PIM service doesn't account for a Migration Plan with different source and target process ids.

      There are a few things to consider:

      • That already reveals a disconnect between UI and service, because in UI such plan can be created at least (further usage of such plan is subject of some of the linked issues).
      • This way we're preventing following use cases:
        • possibility to rename project/deployment and then migrate the instances
        • rename a process and then migrate the instances
        • possible combination of both (e.g. moving from legacy project to a new implementation)

      I understand that in case of an implicit migration (either during product upgrade or when using the service alone) this is understandable limitation. But with addition of UI, where such information can be tracked and presented, I see this as a serious limitation of scope of use cases.

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8498 PIM UI - Migration Plan edit puts incorrect data into edit form

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8475 PIM UI - migration plan listing lacks Source Process Id column

          • 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. JBPM-8476 PIM UI - migration plan can be executed on non-matching process

          • 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. JBPM-8499 PIM UI - can't execute migration plan when project names differ

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

          Bug - A problem that impairs or prevents the functions of the product. JBPM-8498 PIM UI - Migration Plan edit puts incorrect data into edit form

          • 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

              rhn-support-rromerom Ruben Romero Montes
              jstastny@redhat.com Jan Stastny
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: