[tests-only][full-ci] Remove remaining ocis/reva scenario tags

tests/acceptance/features/apiAuthWebDav/webDavMKCOLAuth.feature

@@ -30,7 +30,7 @@ Feature: create folder using MKCOL
       | /remote.php/dav/files/%username%/PARENT/parent.txt |
     Then the HTTP status code of responses on all endpoints should be "401"
 
-  @skipOnOcV10 @issue-ocis-reva-197
+  @skipOnOcV10
   Scenario: send MKCOL requests to another user's webDav endpoints as normal user
     Given user "Brian" has been created with default attributes and without skeleton files
     When user "Brian" requests these endpoints with "MKCOL" including body "" about user "Alice"
@@ -41,7 +41,7 @@ Feature: create folder using MKCOL
       | /remote.php/dav/files/%username%/PARENT/parent.txt |
     Then the HTTP status code of responses on all endpoints should be "404"
 
-  @skipOnOcV10 @issue-ocis-reva-197
+  @skipOnOcV10
   Scenario: send MKCOL requests to non-existent user's webDav endpoints as normal user
     Given user "Brian" has been created with default attributes and without skeleton files
     When user "Brian" requests these endpoints with "MKCOL" including body "" about user "non-existent-user"

tests/acceptance/features/apiAuthWebDav/webDavPOSTAuth.feature

@@ -34,7 +34,7 @@ Feature: get file info using POST
       | /remote.php/dav/files/%username%/PARENT/parent.txt |
     Then the HTTP status code of responses on all endpoints should be "401"
 
-  @issue-ocis-reva-179
+
   Scenario: send POST requests to another user's webDav endpoints as normal user
     When user "Brian" requests these endpoints with "POST" including body "doesnotmatter" about user "Alice"
       | endpoint                                           |

tests/acceptance/features/apiAuthWebDav/webDavPROPPATCHAuth.feature

@@ -34,7 +34,7 @@ Feature: PROPPATCH file/folder
       | /remote.php/dav/files/%username%/PARENT/parent.txt |
     Then the HTTP status code of responses on all endpoints should be "401"
 
-  @issue-ocis-reva-197
+
   Scenario: send PROPPATCH requests to another user's webDav endpoints as normal user
     When user "Brian" requests these endpoints with "PROPPATCH" to set property "favorite" about user "Alice"
       | endpoint                                           |

tests/acceptance/features/apiCapabilities/capabilitiesWithNormalUser.feature

@@ -5,9 +5,9 @@ Feature: default capabilities for normal user
     Given using OCS API version "1"
     And user "Alice" has been created with default attributes and without skeleton files
 
+
   # adjust this scenario after fixing tagged issues as its just created to show difference
   # in the response items in different environment (core & ocis-reva)
-  @issue-ocis-reva-175 @issue-ocis-reva-176
   Scenario: getting default capabilities with normal user
     When user "Alice" retrieves the capabilities using the capabilities API
     Then the OCS status code should be "100"

tests/acceptance/features/apiFavorites/favorites.feature

@@ -13,7 +13,7 @@ Feature: favorite
     And user "Alice" has created folder "/PARENT"
     And user "Alice" has uploaded file with content "some data" to "/PARENT/parent.txt"
 
-  @issue-ocis-reva-276
+
   Scenario Outline: Favorite a folder
     Given using <dav_version> DAV path
     When user "Alice" favorites element "/FOLDER" using the WebDAV API
@@ -29,7 +29,7 @@ Feature: favorite
       | old         |
       | new         |
 
-  @issue-ocis-reva-276
+
   Scenario Outline: Unfavorite a folder
     Given using <dav_version> DAV path
     And user "Alice" has favorited element "/FOLDER"
@@ -46,7 +46,7 @@ Feature: favorite
       | old         |
       | new         |
 
-  @smokeTest @issue-ocis-reva-276
+  @smokeTest
   Scenario Outline: Favorite a file
     Given using <dav_version> DAV path
     When user "Alice" favorites element "/textfile0.txt" using the WebDAV API
@@ -62,7 +62,7 @@ Feature: favorite
       | old         |
       | new         |
 
-  @smokeTest @issue-ocis-reva-276
+  @smokeTest
   Scenario Outline: Unfavorite a file
     Given using <dav_version> DAV path
     And user "Alice" has favorited element "/textfile0.txt"

tests/acceptance/features/apiMain/checksums-TestOc10Issue38835.feature

@@ -5,7 +5,7 @@ Feature: checksums
     Given user "Alice" has been created with default attributes and without skeleton files
 
   # this is a bug demo scenario for https://github.com/owncloud/core/issues/38835
-  # Once this scenario is fixed Delete this file and remove @skipOnOcV10 tag from tests/acceptance/features/apiMain/checksums.feature:132
+  # Once this scenario is fixed Delete this file and remove @skipOnOcV10 tag from tests/acceptance/features/apiMain/checksums.feature:158
   @files_sharing-app-required @skipOnStorage:ceph @skipOnStorage:scality
   Scenario: Sharing and modifying a file should return correct checksum in the propfind using new DAV path
     Given the administrator has set the default folder for received shares to "Shares"

tests/acceptance/features/apiMain/checksums.feature

@@ -13,7 +13,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @smokeTest @issue-ocis-reva-196
+  @smokeTest
   Scenario Outline: Uploading a file with checksum should return the checksum in the propfind
     Given using <dav_version> DAV path
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
@@ -36,7 +36,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @issue-ocis-reva-196
+
   Scenario Outline: Moving a file with checksum should return the checksum in the propfind
     Given using <dav_version> DAV path
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
@@ -61,7 +61,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @issue-ocis-reva-196
+
   Scenario Outline: Uploading a chunked file with checksum should return the checksum in the propfind
     Given using <dav_version> DAV path
     And user "Alice" has uploaded chunk file "1" of "3" with "AAAAA" to "/myChecksumFile.txt" with checksum "MD5:45a72715acdd5019c5be30bdbb75233e"
@@ -116,7 +116,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @issue-ocis-reva-196
+
   Scenario Outline: Copying a file with checksum should return the checksum in the propfind using new DAV path
     Given using <dav_version> DAV path
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
@@ -138,7 +138,7 @@ Feature: checksums
       | dav_version |
       | new         |
 
-  @files_sharing-app-required @issue-ocis-reva-196
+  @files_sharing-app-required
   Scenario Outline: Sharing a file with checksum should return the checksum in the propfind using new DAV path
     Given the administrator has set the default folder for received shares to "Shares"
     And auto-accept shares has been disabled
@@ -154,23 +154,21 @@ Feature: checksums
       | dav_version |
       | new         |
 
-  @files_sharing-app-required @issue-ocis-reva-196 @skipOnOcV10
-  Scenario Outline: Modifying a shared file should return correct checksum in the propfind using new DAV path
+  @files_sharing-app-required @skipOnOcV10
+  Scenario: Modifying a shared file should return correct checksum in the propfind using new DAV path
     Given the administrator has set the default folder for received shares to "Shares"
     And auto-accept shares has been disabled
-    And using <dav_version> DAV path
+    And using new DAV path
     And user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file "filesForUpload/textfile.txt" to "/myChecksumFile.txt" with checksum "MD5:d70b40f177b14b470d1756a3c12b963a"
     And user "Alice" has shared file "/myChecksumFile.txt" with user "Brian"
     And user "Brian" has accepted share "/myChecksumFile.txt" offered by user "Alice"
     When user "Brian" uploads file with checksum "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399" and content "Some Text" to "/Shares/myChecksumFile.txt" using the WebDAV API
     Then the HTTP status code should be "204"
-    And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "<checksum>"
-    Examples:
-      | dav_version | checksum                                                                                            |
-      | new         | SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a |
+    And as user "Alice" the webdav checksum of "/myChecksumFile.txt" via propfind should match "SHA1:ce5582148c6f0c1282335b87df5ed4be4b781399 MD5:56e57920c3c8c727bfe7a5288cdf61c4 ADLER32:1048035a"
+
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Upload new DAV chunked file where checksum matches
     Given using new DAV path
     And user "Alice" has created a new chunking upload with id "chunking-42"
@@ -179,7 +177,7 @@ Feature: checksums
     And user "Alice" moves new chunk file with id "chunking-42" to "/myChunkedFile.txt" with checksum "SHA1:5d84d61b03fdacf813640f5242d309721e0629b1" using the WebDAV API
     Then the HTTP status code of responses on all endpoints should be "201"
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Upload new DAV chunked file where checksum does not match
     Given using new DAV path
     And user "Alice" has created a new chunking upload with id "chunking-42"
@@ -190,7 +188,7 @@ Feature: checksums
     And user "Alice" should not see the following elements
       | /myChunkedFile.txt |
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Upload new DAV chunked file using async MOVE where checksum matches
     Given using new DAV path
     And the administrator has enabled async operations
@@ -206,7 +204,7 @@ Feature: checksums
       | fileId | /^[0-9a-z]{20,}$/ |
     And the content of file "/myChunkedFile.txt" for user "Alice" should be "BBBBBCCCCC"
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Upload new DAV chunked file using async MOVE where checksum does not match
     Given using new DAV path
     And the administrator has enabled async operations
@@ -224,7 +222,7 @@ Feature: checksums
     And user "Alice" should not see the following elements
       | /myChunkedFile.txt |
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Upload new DAV chunked file using async MOVE where checksum does not match - retry with correct checksum
     Given using new DAV path
     And the administrator has enabled async operations
@@ -340,7 +338,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @issue-ocis-reva-196
+  @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224
   Scenario Outline: Uploading a file with invalid SHA1 checksum overwriting an existing file
     Given using <dav_version> DAV path
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
@@ -353,7 +351,7 @@ Feature: checksums
       | old         |
       | new         |
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Upload overwriting a file with new chunking and correct checksum
     Given using new DAV path
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"
@@ -364,7 +362,7 @@ Feature: checksums
     Then the HTTP status code of responses on each endpoint should be "201, 201, 204" respectively
     And the content of file "/textfile0.txt" for user "Alice" should be "BBBBBCCCCC"
 
-  @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @newChunking @issue-ocis-1321
+  @skipOnStorage:ceph @skipOnStorage:scality @files_primary_s3-issue-224 @newChunking
   Scenario: Upload overwriting a file with new chunking and invalid checksum
     Given using new DAV path
     And user "Alice" has uploaded file with content "ownCloud test text file 0" to "/textfile0.txt"

tests/acceptance/features/apiMain/main.feature

@@ -1,7 +1,7 @@
 @api
 Feature: Other tests related to api
 
-  @issue-ocis-reva-100
+
   Scenario: robots.txt file should be accessible
     When a user requests "/robots.txt" with "GET" and no authentication
     Then the HTTP status code should be "200"

tests/acceptance/features/apiMain/quota.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-reva-101 @skipOnGraph
+@api @skipOnGraph
 Feature: quota
 
   Background:
@@ -12,7 +12,7 @@ Feature: quota
     When user "Alice" uploads file "filesForUpload/textfile.txt" to filenames based on "/testquota.txt" with all mechanisms except new chunking using the WebDAV API
     Then the HTTP status code of all upload responses should be "201"
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Uploading a file as owner having enough quota (new chunking)
     Given the quota of user "Alice" has been set to "10 MB"
     And using new DAV path
@@ -26,7 +26,7 @@ Feature: quota
     Then the HTTP status code of all upload responses should be "507"
     And as "Alice" the files uploaded to "/testquota.txt" with all mechanisms except new chunking should not exist
 
-  @smokeTest @newChunking @issue-ocis-1321
+  @smokeTest @newChunking
   Scenario: Uploading a file as owner having insufficient quota (new chunking)
     Given the quota of user "Alice" has been set to "10 B"
     And using new DAV path
@@ -41,7 +41,7 @@ Feature: quota
     When user "Alice" overwrites from file "filesForUpload/textfile.txt" to file "/testquota.txt" with all mechanisms except new chunking using the WebDAV API
     Then the HTTP status code of all upload responses should be between "201" and "204"
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Overwriting a file as owner having enough quota (new chunking)
     Given user "Alice" has uploaded file with content "test" to "/testquota.txt"
     And the quota of user "Alice" has been set to "10 MB"
@@ -57,7 +57,7 @@ Feature: quota
     Then the HTTP status code of all upload responses should be "507"
     And the content of file "/testquota.txt" for user "Alice" should be "test"
 
-  @newChunking @issue-ocis-1321
+  @newChunking
   Scenario: Overwriting a file as owner having insufficient quota (new chunking)
     Given user "Alice" has uploaded file with content "test" to "/testquota.txt"
     And the quota of user "Alice" has been set to "10 B"
@@ -78,7 +78,7 @@ Feature: quota
     When user "Brian" uploads file "filesForUpload/textfile.txt" to filenames based on "/testquota/testquota.txt" with all mechanisms except new chunking using the WebDAV API
     Then the HTTP status code of all upload responses should be "201"
 
-  @files_sharing-app-required @newChunking @issue-ocis-1321
+  @files_sharing-app-required @newChunking
   Scenario: Uploading a file in received folder having enough quota (new chunking)
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/testquota"
@@ -100,7 +100,7 @@ Feature: quota
     Then the HTTP status code of all upload responses should be "507"
     And as "Brian" the files uploaded to "/testquota/testquota.txt" with all mechanisms except new chunking should not exist
 
-  @files_sharing-app-required @newChunking @issue-ocis-1321
+  @files_sharing-app-required @newChunking
   Scenario: Uploading a file in a received folder having insufficient quota (new chunking)
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/testquota"
@@ -123,7 +123,7 @@ Feature: quota
     When user "Brian" overwrites from file "filesForUpload/textfile.txt" to file "/testquota/testquota.txt" with all mechanisms except new chunking using the WebDAV API
     Then the HTTP status code of all upload responses should be between "201" and "204"
 
-  @files_sharing-app-required @newChunking @issue-ocis-1321
+  @files_sharing-app-required @newChunking
   Scenario: Overwriting a file in received folder having enough quota (new chunking)
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/testquota"
@@ -147,7 +147,7 @@ Feature: quota
     Then the HTTP status code of all upload responses should be "507"
     And the content of file "/testquota/testquota.txt" for user "Alice" should be "test"
 
-  @files_sharing-app-required @newChunking @issue-ocis-1321
+  @files_sharing-app-required @newChunking
   Scenario: Overwriting a file in received folder having insufficient quota (new chunking)
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has created folder "/testquota"
@@ -172,7 +172,7 @@ Feature: quota
     When user "Brian" overwrites from file "filesForUpload/textfile.txt" to file "/testquota.txt" with all mechanisms except new chunking using the WebDAV API
     Then the HTTP status code of all upload responses should be between "201" and "204"
 
-  @files_sharing-app-required @newChunking @issue-ocis-1321
+  @files_sharing-app-required @newChunking
   Scenario: Overwriting a received file having enough quota (new chunking)
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "test" to "/testquota.txt"
@@ -194,7 +194,7 @@ Feature: quota
     Then the HTTP status code of all upload responses should be "507"
     And the content of file "/testquota.txt" for user "Alice" should be "test"
 
-  @files_sharing-app-required @newChunking @issue-ocis-1321
+  @files_sharing-app-required @newChunking
   Scenario: Overwriting a received file having insufficient quota (new chunking)
     Given user "Brian" has been created with default attributes and without skeleton files
     And user "Alice" has uploaded file with content "test" to "/testquota.txt"

tests/acceptance/features/apiMain/userSync.feature

@@ -1,4 +1,4 @@
-@api @issue-ocis-1241
+@api
 Feature: Users sync
 
   Background:

tests/acceptance/features/apiShareCreateSpecialToShares1/createShareExpirationDate.feature

@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-ocis-1328 @issue-ocis-1250
+@api @files_sharing-app-required
 Feature: a default expiration date can be specified for shares with users or groups
 
   Background:

tests/acceptance/features/apiShareCreateSpecialToShares1/createShareUniqueReceivedNames.feature

@@ -11,7 +11,7 @@ Feature: resources shared with the same name are received with unique names
       | Brian    |
       | Carol    |
 
-  @smokeTest @issue-ocis-2131
+  @smokeTest
   Scenario Outline: unique target names for incoming shares
     Given user "Alice" has created folder "/foo"
     And user "Brian" has created folder "/foo"

tests/acceptance/features/apiShareCreateSpecialToShares2/createShareDefaultFolderForReceivedShares.feature

@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-ocis-1327
+@api @files_sharing-app-required
 Feature: shares are received in the default folder for received shares
 
   Background:

tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWhenShareWithOnlyMembershipGroups.feature

@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-ocis-1328
+@api @files_sharing-app-required
 Feature: cannot share resources outside the group when share with membership groups is enabled
 
   Background:

tests/acceptance/features/apiShareCreateSpecialToShares2/createShareWithDisabledUser.feature

@@ -1,4 +1,4 @@
-@api @files_sharing-app-required @issue-ocis-1328
+@api @files_sharing-app-required
 Feature: share resources with a disabled user
 
   Background: