{"action":"closed","issue":{"url":"https://api.github.com/repos/reportportal/reportportal/issues/304","repository_url":"https://api.github.com/repos/reportportal/reportportal","labels_url":"https://api.github.com/repos/reportportal/reportportal/issues/304/labels{/name}","comments_url":"https://api.github.com/repos/reportportal/reportportal/issues/304/comments","events_url":"https://api.github.com/repos/reportportal/reportportal/issues/304/events","html_url":"https://github.com/reportportal/reportportal/issues/304","id":284802461,"number":304,"title":"Extra true/false option for Fixed/Not fixed failures","user":{"login":"dmitryyu","id":11774103,"avatar_url":"https://avatars1.githubusercontent.com/u/11774103?v=4","gravatar_id":"","url":"https://api.github.com/users/dmitryyu","html_url":"https://github.com/dmitryyu","followers_url":"https://api.github.com/users/dmitryyu/followers","following_url":"https://api.github.com/users/dmitryyu/following{/other_user}","gists_url":"https://api.github.com/users/dmitryyu/gists{/gist_id}","starred_url":"https://api.github.com/users/dmitryyu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dmitryyu/subscriptions","organizations_url":"https://api.github.com/users/dmitryyu/orgs","repos_url":"https://api.github.com/users/dmitryyu/repos","events_url":"https://api.github.com/users/dmitryyu/events{/privacy}","received_events_url":"https://api.github.com/users/dmitryyu/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2017-12-27T21:53:43Z","updated_at":"2018-03-13T13:53:25Z","closed_at":"2018-03-13T13:53:25Z","author_association":"NONE","body":"After investigation of a failure, I can understand that's reason of it is Automation Bug.\r\nI can add the defect type: \"Automation Bug\" or any other custom defect type.\r\nBut it's really not always possible to fix the issue on \"the fly\", so such failures can be  \"Fixed/Not Fixed\".\r\n\r\nI have tried to use a custom defect type like \"Fixed. Automation Bug.\" and for all fixed tests i added the label with a real reason of a fail and what's fixed. But for the next run I am forced to manually change all \"Fixed. Automation Bug\" statuses which were automatically detected and categorized. (For instance, pre-staged test-data for a user has been added, but another user doesn't have the test-data)\r\n\r\nThus, **it would be cool to have an extra option (for example, \"Fixed\" ) which can be set to any failed case, which was fixed.** \r\n\r\n**Pros:**\r\n1. Manual team has a possibility to mark the fail as automation bug - but automation fix will be done later (by automation team). \r\n2. Automation team can apply quick fixes on the fly by setting the option on, and complex fixes can be done later (probably by other QA). And having a filter by the option will allow to find \"Not fixed\" failures.\r\n3. The option should not be set during Auto analysis. (but in case of the same fail reason - it would be cool to add something like \"this failure have been marked as \"Fixed\" in prev. launch\".\r\n4. Also it's possible for other defect types. For example, System issue - Investigation can be done by QA Engineers, but fixes for it - by devops (and as usually after some days).\r\n\r\nThanks.\r\n"}}
{"actor":{"display_login":"evjlobanova"}}