Hide Forgot
+++ This bug was initially created as a clone of Bug #1315671 +++ Description of problem: This is a follow up to bug # 1305057 After creating new managed repository in Administration perspective with option "Automatically Configure Branches" enabled, the branches dev & release are created, but they are not initially listed in the dropdown for switching the branches. Attached video with steps to reproduce (this video is recorded using 6.2.2 patch, but the issue is the same in 6.3.0.DR2). The issue is visible in 0:22 after repo is created - only master branch is shown. I need to leave perspective - return to perspective to actually see other branches there. Version-Release number of selected component (if applicable): BPM Suite 6.3.0 DR2 How reproducible: Always Steps to Reproduce: 1. Login with user who has role kiemgmt (needed to be able to create managed repository) 2. Go to Administration persp., Repositories > New Repository 3. Fill in name and check "manage repository", click next and make sure Automatically configure branches (master/dev/release) is selected and click Finish 4. Check the main panel on the right (Repository edito) contains the newly created repo Actual results: The dropdown for selecting branches only contains "master" option. But when I navigate to different perspective (e.g. authoring) and then get back to Administration, then the select contains all the branches (master/dev/release) Expected results: The dropdown in Administration > Repository Editor should contain all the branches after Managed repo is created with "Automatically configure branches" option. --- Additional comment from Jan Hrcek on 2016-03-08 07:05 EST --- --- Additional comment from Kris Verlaenen on 2016-03-16 11:10:03 EDT --- Adding blocker flag for 6.3.0 since this is also requested for 6.2.3 --- Additional comment from Walter Medvedeo on 2016-03-22 12:06:09 EDT --- PR in the 6.4.x branch is in the waiting queue. --- Additional comment from Walter Medvedeo on 2016-03-22 12:09:00 EDT --- Just for record here's the pointer to the mentioned PR https://github.com/droolsjbpm/guvnor/pull/296 --- Additional comment from Walter Medvedeo on 2016-03-22 13:34:15 EDT --- PR was merged into 6.4.x and the fix will be available for the 6.4-CR2 and product 6.3 https://github.com/droolsjbpm/guvnor/pull/296/commits/f560a63b51d00eebc6d1b03c627d740182bb3ef0 --- Additional comment from Walter Medvedeo on 2016-03-23 09:44:11 EDT --- PR in master in the waiting queue --- Additional comment from Walter Medvedeo on 2016-03-23 12:08:24 EDT --- PR was also merged into master https://github.com/droolsjbpm/guvnor/commit/718e97231c1a80cad41ed0c47f8d733b293c804b So now both master and 6.4.x has the fix. --- Additional comment from Alessandro Lazarotti on 2016-04-15 10:17:40 EDT --- this bz is for 6.3.0, a new one with the commit to 6.2.3 (branch 6.3.x) should be created. i am removing the flag: brms-rollup-3-6.2.x
Hello, I've been looking at this issue and due to the differences between 6.3.x and 6.4.x/master branches it's not factible to cherry-pick the fix provided for 6.4.x/master into 6.3.x. i.e. there has been refactorings, bs3, etc., in the middle and it's not direct to port the fix into 6.3.x. I presume a fix should be written independelly of the alreadly provided for 6.4.x should be written. So the question is if we proceed rewriting a new fix for this case?
Fix will be only delivered in product 6.3.z as agreed with engineering team - so closing it