-
Bug
-
Resolution: Done
-
Critical
-
7.7.0.GA
-
Documentation (Ref Guide, User Guide, etc.), Release Notes
-
-
-
-
-
-
CR1
-
Workaround Exists
-
- Click on canvas.
- Click on Rule flow Group drop-down menu again.
-
-
2020 Week 31-33 (from Jul 27), 2020 Week 34-36 (from Aug 17), 2020 Week 37-39 (from Sep 7)
Rule flow group is not populated when it should be.
It should be populated with all rule-flow groups defined in the project.
- is duplicated by
-
JBPM-9267 Stunner - Rule flow group is not populated
- Resolved
- is related to
-
RHPAM-3179 Stunner - Called element and Rule flow group properties are not updated after deleting assets
- Backlog
-
RHPAM-3194 Stunner - Edited Rule flow group is not reflected in Business rule task's property
- Backlog
-
RHPAM-3195 Stunner - A new Rule flow group is not reflected in Business rule task's property
- Backlog
-
JBPM-8876 Stunner - Ruleflow group not loaded (DROOLS-3727 merge)
- Resolved
-
RHPAM-2536 Stunner - gateways default route dropdown options are not populated after gateway created
- Closed
- relates to
-
JBPM-9110 Stunner - [BPMN] On deleting a project which defines ruleflow groups, business rule tasks cannot be configured properly
- Resolved
-
RHDM-1277 Rule flow group is not populated
- Closed
-
RHPAM-2760 Stunner - Called element in Reusable sub-process is not populated
- Closed
-
RHPAM-2910 When selecting Rule Flow Group in the Properties for a Business Rule Task in a Process, it should use show from which project ruleflow group is loaded.
- Closed