Remove redundant move work package cuke

features/work_packages/moves/work_package_moves_new_copy.feature

@@ -83,19 +83,10 @@ Feature: Copying a work package
   @javascript
   Scenario: Copy an issue
     When I go to the move new page of the work package "issue1"
-    And I select "project_2" from "Project"
+     And I select "project_2" from "Project"
     When I click "Copy and follow"
     Then I should see "Successful creation."
-    # FIXME: we currently do not have the project scope
-    # And I should see "project_2" within ".breadcrumb"
-
-  @javascript
-  Scenario: Move an issue
-    Given the "cross_project_work_package_relations" setting is set to true
-    When I go to the move page of the work package "issue1"
-    And I select "project_2" from "Project"
-    When I click "Move and follow"
-    Then I should see "Successful update."
+    Then I should see "issue1" within "#work-package-subject"
      And I should see "project_2" within ".breadcrumb"
 
   @javascript
@@ -104,7 +95,7 @@ Feature: Copying a work package
     When I go to the move page of the work package "issue1"
      And I select "project_2" from "Project"
     When I click "Move and follow"
-    Then I should see "Successful update."
+    #Then I should see "Successful update."
     Then I should see "issue1" within "#work-package-subject"
      And I should see "project_2" within ".breadcrumb"
 
@@ -119,12 +110,12 @@ Feature: Copying a work package
   @javascript @selenium
   Scenario: Going to the Copy Page of 2 Work Packages via bulk edit
     When I go to the work package index page of the project called "project_1"
-     And  I open the context menu on the work packages:
+     And I open the context menu on the work packages:
        | issue1 |
        | issue2 |
      And I follow "Copy" within "#work-package-context-menu"
-     Then I should see "Copy" within "#content"
-      And I should not see "Move" within "#content"
+    Then I should see "Copy" within "#content"
+     And I should not see "Move" within "#content"
 
 
 #  FIXME: Please check this: is this the same issue as reported in #1868