Bug 1330630

Summary: Planner: Immovable planning entities for chained variables
Product: [Retired] JBoss BRMS Platform 6 Reporter: Geoffrey De Smet <gdesmet>
Component: OptaPlannerAssignee: Geoffrey De Smet <gdesmet>
Status: CLOSED EOL QA Contact: Jiri Locker <jlocker>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0CC: lpetrovi
Target Milestone: ---   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:05:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Geoffrey De Smet 2016-04-26 15:37:22 UTC
Immovable planning entities are critical for continuous planning.
However, the combination of immovable planning entities and chained variables has been broken for year and it's one of OptaPlanner's hotests bugs in the community jira:
  https://issues.jboss.org/browse/PLANNER-239

I've found a way to fix it for 7.0 and I can backport it to 6.4.x (= BRMS 6.3) if this is triaged.

This issue is critical for task assigning that uses the chained through time pattern (2 customers do this).

Comment 1 Geoffrey De Smet 2016-04-27 11:39:06 UTC
Once I have the ok to backport this to optaplanner 6.4.x, I need to cherry pick (and deal with the guaranteed merge conflict) these 2 commits:
  https://github.com/droolsjbpm/optaplanner/commit/b8ae184146e16fd83cb8294317c3da2e8587fb5d
  https://github.com/droolsjbpm/optaplanner/commit/78adf0690a4efd8d3e570b790459a756e57210a2

I don't care if it makes BRMS 6.3.0 or 6.3.1 (both should be fine for the customer I presume), as long as I can backport it sooner rather than later while it's still fresh in my memory to deal with the merge conflicts efficiently.