Bug 1265471 - Can't restore version of a process
Can't restore version of a process
Status: VERIFIED
Product: JBoss BRMS Platform 6
Classification: JBoss
Component: Rule Flow Designer (Show other bugs)
6.1.0
Unspecified Unspecified
high Severity unspecified
: ER4
: 6.2.0
Assigned To: Tihomir Surdilovic
Kirill Gaevskii
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-22 23:06 EDT by William Antônio
Modified: 2015-10-19 09:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Adding a simple video that shows this issue. (1.24 MB, application/ogg)
2015-09-22 23:06 EDT, William Antônio
no flags Details

  None (edit)
Description William Antônio 2015-09-22 23:06:47 EDT
Created attachment 1076072 [details]
Adding a simple video that shows this issue.

Description of problem:

A rule flow versions are not listed unless we close and reopen it. Once it is listed, and we click on a version, it fails to restore that version with message "Process contains no changes since last save."


Version-Release number of selected component (if applicable):
n/a

How reproducible:
always

Steps to Reproduce:
1. Create a rule flow process;
2. Make a few changes to it and save;
3. make a few other changes and save;
4. The versions will not be listed when clicking on "Latest Version" drop button, so close it and open again;
5. Click in one of the listed version and the click on the "restore" button.

Actual results:
message "Process contains no changes since last save."

Expected results:
It should restore the selected version.

Additional info:

It also happen if we try to restore some of the version listed on the Overview tab.

An attached screencast show this issue.
Comment 2 Kirill Gaevskii 2015-10-19 09:48:18 EDT
Verified but bug 1273056 and bug 1273061 was reported.

Note You need to log in before you can comment on or make changes to this bug.