test: drop labels of no longer expected issues

Author: LukasHirt

tests/acceptance/features/apiActivities/shareActivities.feature

@@ -1925,7 +1925,7 @@ Feature: check share activity
     When user "Brian" tries to list the activities of file "anotherTextfile.txt" from space "Personal" owned by user "Alice" using the Graph API
     Then the HTTP status code should be "403"
 
-  @issue-9676 @issue-10331
+  @issue-9676
   Scenario: user checks public activities of a link shared file
     Given using SharingNG
     And user "Alice" has created the following resource link share:
@@ -2061,7 +2061,7 @@ Feature: check share activity
       }
       """
 
-  @issue-9676 @issue-10331
+  @issue-9676
   Scenario: user checks public activities of a link shared folder
     Given using SharingNG
     And user "Alice" has created folder "/FOLDER"

tests/acceptance/features/apiAntivirus/antivirus.feature

@@ -92,7 +92,6 @@ Feature: antivirus
       | new              |
       | spaces           |
 
-  @issue-10331
   Scenario Outline: public uploads a file with the virus to a public share
     Given using <dav-path-version> DAV path
     And the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false" for "sharing" service
@@ -118,7 +117,6 @@ Feature: antivirus
       | spaces           | eicar.com     | virusFile1.txt |
       | spaces           | eicar_com.zip | virusFile2.zip |
 
-  @issue-10331
   Scenario Outline: public uploads a file with the virus to a password-protected public share
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -335,7 +333,7 @@ Feature: antivirus
       | new              |
       | spaces           |
 
-  @env-config @issue-10331
+  @env-config
   Scenario Outline: try to overwrite a file with the virus content in a public link share
     Given the config "OCIS_SHARING_PUBLIC_SHARE_MUST_HAVE_PASSWORD" has been set to "false" for "sharing" service
     And using <dav-path-version> DAV path

tests/acceptance/features/apiCollaboration/wopi.feature

@@ -925,7 +925,6 @@ Feature: collaboration (wopi)
     And as "Alice" file "testFolder/simple.odt" should not exist
     And as "Brian" file "Shares/testFolder/simple.odt" should not exist
 
-  @issue-10331
   Scenario Outline: public user with permission edit/upload/createOnly creates odt file inside public folder using wopi endpoint
     Given user "Alice" has created folder "publicFolder"
     And user "Alice" has created the following resource link share:
@@ -957,7 +956,7 @@ Feature: collaboration (wopi)
       | Upload           |
       | File Drop        |
 
-  @issue-10126 @issue-10331
+  @issue-10126
   Scenario: public user with permission view tries to creates odt file inside public folder using wopi endpoint
     Given user "Alice" has created folder "publicFolder"
     And user "Alice" has created the following resource link share:
@@ -1013,7 +1012,7 @@ Feature: collaboration (wopi)
       }
       """
 
-  @issue-8691 @issue-10331
+  @issue-8691
   Scenario Outline: public user with permission edit/upload/createOnly creates odt file inside folder of public space using wopi endpoint
     Given using spaces DAV path
     And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API
@@ -1048,7 +1047,7 @@ Feature: collaboration (wopi)
       | Upload           |
       | File Drop        |
 
-  @issue-8691 @issue-10126 @issue-10331
+  @issue-8691 @issue-10126
   Scenario: public user with permission view tries to create odt file inside folder of public space using wopi endpoint
     Given using spaces DAV path
     And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API

tests/acceptance/features/apiDepthInfinity/propfind.feature

@@ -70,7 +70,6 @@ Feature: PROPFIND with depth:infinity
       | new              |
       | spaces           |
 
-  @issue-10331
   Scenario: get the list of resources in a folder shared through public link with depth infinity
     Given using SharingNG
     And the following configs have been set:
@@ -120,7 +119,6 @@ Feature: PROPFIND with depth:infinity
       | new              |
       | spaces           |
 
-  @issue-10331
   Scenario: get the list of resources in a folder shared through public link with depth infinity when depth infinity is not allowed
     Given the following configs have been set:
       | service | config                                       | value |

tests/acceptance/features/apiLocks/lockFiles.feature

@@ -421,7 +421,7 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
-  @issue-7641 @issue-10331
+  @issue-7641
   Scenario Outline: try to lock a folder as anonymous user
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -466,7 +466,6 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
-  @issue-10331
   Scenario Outline: lock a file inside a folder shared by a link as anonymous user with edit permission
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -489,7 +488,6 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
-  @issue-10331
   Scenario Outline: try to lock a file inside a folder shared by a link as anonymous user with read permission
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -512,7 +510,6 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
-  @issue-7790 @issue-10331
   Scenario Outline: lock a file shared by a link as anonymous user with edit permission
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -534,7 +531,7 @@ Feature: lock files
       | spaces           | shared     |
       | spaces           | exclusive  |
 
-  @issue-7790 @issue-10331
+  @issue-7790
   Scenario Outline: try to lock a file shared by a link as anonymous user with read permission
     Given using <dav-path-version> DAV path
     And using SharingNG

tests/acceptance/features/apiLocks/unlockFiles.feature

@@ -21,7 +21,7 @@ Feature: unlock locked items
       | new              |
       | spaces           |
 
-  @issue-7761 @issue-10331
+  @issue-7761
   Scenario Outline: public tries to unlock a file in a share that was locked by the file owner
     Given using <dav-path-version> DAV path
     And using SharingNG
@@ -298,7 +298,6 @@ Feature: unlock locked items
     And using new DAV path
     And user "Brian" should be able to upload file "filesForUpload/lorem.txt" to "Shares/textfile.txt"
 
-  @issue-10331
   Scenario Outline: unlock a file as an anonymous user
     Given using <dav-path-version> DAV path
     And using SharingNG

tests/acceptance/features/apiSharingNgDriveLinkShare/updateDriveLinkShare.feature

@@ -6,7 +6,7 @@ Feature: Update a link share for a resource
       | username |
       | Alice    |
 
-  @env-config @issue-9724 @issue-10331
+  @env-config
   Scenario: set password on a existing link share of a project-space drive using root endpoint
     Given the following configs have been set:
       | service | config                                       | value |
@@ -38,7 +38,6 @@ Feature: Update a link share for a resource
       """
     And the public should be able to download file "textfile.txt" from the last link share with password "%public%" and the content should be "to share"
 
-  @issue-9724 @issue-10331
   Scenario: update password on a existing link share of a project-space drive using root endpoint
     And using spaces DAV path
     And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API

tests/acceptance/features/apiSharingNgItemLinkShare/createLinkShareWithoutPasswordEnforce.feature

@@ -84,7 +84,6 @@ Feature: Link share without enforcing password
       | Edit             | edit                   |
       | Secure View      | blocksDownload         |
 
-  @issue-9724 @issue-10331
   Scenario: set password on existing file link share
     Given user "Alice" has uploaded file with content "other data" to "textfile1.txt"
     And user "Alice" has created the following resource link share:
@@ -187,7 +186,6 @@ Feature: Link share without enforcing password
       | Edit             | edit                   |
       | Secure View      | blocksDownload         |
 
-  @issue-9724 @issue-10331
   Scenario: set password on a existing file link share inside project-space
     Given using spaces DAV path
     And the administrator has assigned the role "Space Admin" to user "Alice" using the Graph API

tests/acceptance/features/apiSharingNgLinkShareManagement/updateItemLinkShare.feature

@@ -205,7 +205,6 @@ Feature: Update a link share for a resource
       }
       """
 
-  @issue-9724 @issue-10331
   Scenario: update password of a file's link share using permissions endpoint
     Given user "Alice" has uploaded file with content "other data" to "textfile1.txt"
     And user "Alice" has created the following resource link share:
@@ -283,7 +282,7 @@ Feature: Update a link share for a resource
       | password        |
       | ownCloud        |
 
-  @env-config @issue-9724 @issue-10331
+  @env-config
   Scenario: set password on a existing link share of a folder inside project-space using permissions endpoint
     Given the following configs have been set:
       | service | config                                       | value |

tests/acceptance/features/apiSpaces/editPublicLinkOfSpace.feature

@@ -21,7 +21,6 @@ Feature: A manager of the space can edit public link
     And user "Alice" has uploaded a file inside space "edit space" with content "some content" to "test.txt"
     And using SharingNG
 
-  @issue-9724 @issue-10331
   Scenario Outline: manager of the space can edit public link.
     Given using OCS API version "2"
     When user "Alice" updates the last public link share using the sharing API with