{"action":"created","issue":{"url":"https://api.github.com/repos/dreditor/dreditor/issues/4","repository_url":"https://api.github.com/repos/dreditor/dreditor","labels_url":"https://api.github.com/repos/dreditor/dreditor/issues/4/labels{/name}","comments_url":"https://api.github.com/repos/dreditor/dreditor/issues/4/comments","events_url":"https://api.github.com/repos/dreditor/dreditor/issues/4/events","html_url":"https://github.com/dreditor/dreditor/issues/4","id":172767973,"number":4,"title":"\"Clone issue\" button should not clone status or \"Triaged D8 critical\" tag, and possibly not \"critical\" priority","user":{"login":"subhojit777","id":1435641,"avatar_url":"https://avatars.githubusercontent.com/u/1435641?v=3","gravatar_id":"","url":"https://api.github.com/users/subhojit777","html_url":"https://github.com/subhojit777","followers_url":"https://api.github.com/users/subhojit777/followers","following_url":"https://api.github.com/users/subhojit777/following{/other_user}","gists_url":"https://api.github.com/users/subhojit777/gists{/gist_id}","starred_url":"https://api.github.com/users/subhojit777/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/subhojit777/subscriptions","organizations_url":"https://api.github.com/users/subhojit777/orgs","repos_url":"https://api.github.com/users/subhojit777/repos","events_url":"https://api.github.com/users/subhojit777/events{/privacy}","received_events_url":"https://api.github.com/users/subhojit777/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2016-08-23T18:11:06Z","updated_at":"2016-08-23T18:11:16Z","closed_at":null,"body":"_From @xjm on February 1, 2015 20:33_\n\nRecently, there have been a lot of issues posted as critical by mistake because contributors use the \"Clone issue\" button to create followups for criticals. This is especially problematic when the issue has been marked as \"Triaged D8 critical\" by the branch maintainers and the button clones that tag, which is for maintainer use only. Creating issues with this tag completely defeats the purpose.\r\n\r\nAlso, in general, I think cloned issues should be created as \"Active\", which is normal for a new issue. It's very unlikely that you want to clone a new issue that has exactly the status of its parent.\n\n_Copied from original issue: unicorn-fail/dreditor#245_"},"comment":{"url":"https://api.github.com/repos/dreditor/dreditor/issues/comments/241823179","html_url":"https://github.com/dreditor/dreditor/issues/4#issuecomment-241823179","issue_url":"https://api.github.com/repos/dreditor/dreditor/issues/4","id":241823179,"user":{"login":"subhojit777","id":1435641,"avatar_url":"https://avatars.githubusercontent.com/u/1435641?v=3","gravatar_id":"","url":"https://api.github.com/users/subhojit777","html_url":"https://github.com/subhojit777","followers_url":"https://api.github.com/users/subhojit777/followers","following_url":"https://api.github.com/users/subhojit777/following{/other_user}","gists_url":"https://api.github.com/users/subhojit777/gists{/gist_id}","starred_url":"https://api.github.com/users/subhojit777/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/subhojit777/subscriptions","organizations_url":"https://api.github.com/users/subhojit777/orgs","repos_url":"https://api.github.com/users/subhojit777/repos","events_url":"https://api.github.com/users/subhojit777/events{/privacy}","received_events_url":"https://api.github.com/users/subhojit777/received_events","type":"User","site_admin":false},"created_at":"2016-08-23T18:11:14Z","updated_at":"2016-08-23T18:11:14Z","body":"_From @markcarver on February 3, 2015 17:45_\n\nIIRC, the original concept was mainly to clone just some of the basic stuff that are actually relevant. Over time things have been added and I think that we're starting to see the adverse effects of doing so.\r\n\r\nFrom my experience, I think the only things that really should be cloned are as follows:\r\n\r\n* Project\r\n* Category\r\n* Version\r\n* Component\r\n\r\nThe reason I did not include title, tags or issue summary is because those really __should__ be unique to the issue and must be filled out properly. Not cloning them forces people to actually fill them out.\r\n\r\nRegarding priority:\r\nJust because the parent/related issue is anything other than normal, doesn't mean we the cloned issue should also get the same priority. For instance, a critical issue gets fixed, but it's soon realized that some documentation or minor verbiage needs to be addressed so a follow-up is created. Obviously it shouldn't get the same critical status as it doesn't actually break anything.\r\n\r\nRegarding tags:\r\nWhen cloning an issue, there's usually a 50/50 changes that all the tags are really accurate anyway. Usually it's used to create a follow-up. For instance, an issue that has been mostly front-end JavaScript work may need a cloned related issue for the back-end (PHP) side of things. In which case \"JavaScript\" doesn't apply. Furthermore, there is a slew of \"Needs ....\" whatever tags that really shouldn't be cloned either. I personally think we should just avoid cloning them all together. Adding a \"blacklist\" will only make this 10x more complicated and highly unmaintainable."}}
{"actor":{"display_login":"subhojit777"}}