{"action":"created","issue":{"url":"https://api.github.com/repos/XX-net/XX-Net/issues/568","labels_url":"https://api.github.com/repos/XX-net/XX-Net/issues/568/labels{/name}","comments_url":"https://api.github.com/repos/XX-net/XX-Net/issues/568/comments","events_url":"https://api.github.com/repos/XX-net/XX-Net/issues/568/events","html_url":"https://github.com/XX-net/XX-Net/issues/568","id":92979447,"number":568,"title":"关于状态页的顺序设计","user":{"login":"yfdyh000","id":1769875,"avatar_url":"https://avatars.githubusercontent.com/u/1769875?v=3","gravatar_id":"","url":"https://api.github.com/users/yfdyh000","html_url":"https://github.com/yfdyh000","followers_url":"https://api.github.com/users/yfdyh000/followers","following_url":"https://api.github.com/users/yfdyh000/following{/other_user}","gists_url":"https://api.github.com/users/yfdyh000/gists{/gist_id}","starred_url":"https://api.github.com/users/yfdyh000/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yfdyh000/subscriptions","organizations_url":"https://api.github.com/users/yfdyh000/orgs","repos_url":"https://api.github.com/users/yfdyh000/repos","events_url":"https://api.github.com/users/yfdyh000/events{/privacy}","received_events_url":"https://api.github.com/users/yfdyh000/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-04T06:48:50Z","updated_at":"2015-07-04T08:16:33Z","closed_at":null,"body":"将版本信息放在前面我觉得是很奇怪的设计，版本信息基本不会变动的，也就不必有关注的需要。\r\n而用户最关注的应该是“状态”信息，其次是appid、设置。\r\n我认为将版本信息放在最后是比较好的方式。或者，用某种方式折叠起来，但允许它被复制。\r\n\r\n再或者，弄一个一键复制状态（乃至近期日志）的按钮，也省的用户自己复制日志了。\r\n\r\nhttps://github.com/XX-net/XX-Net/issues/new?title=123&body=1%0A1 似乎是可用的方式。或许会超出URL允许长度？不过好像没问题，听说IE的限制是2048，其他无限制。但特别的系统（比如某些代理）就不一定了。以及，issue或许会爆满，那样只能开另一个库的issue作为非开发反馈系统。"},"comment":{"url":"https://api.github.com/repos/XX-net/XX-Net/issues/comments/118484142","html_url":"https://github.com/XX-net/XX-Net/issues/568#issuecomment-118484142","issue_url":"https://api.github.com/repos/XX-net/XX-Net/issues/568","id":118484142,"user":{"login":"xxnet","id":10395528,"avatar_url":"https://avatars.githubusercontent.com/u/10395528?v=3","gravatar_id":"","url":"https://api.github.com/users/xxnet","html_url":"https://github.com/xxnet","followers_url":"https://api.github.com/users/xxnet/followers","following_url":"https://api.github.com/users/xxnet/following{/other_user}","gists_url":"https://api.github.com/users/xxnet/gists{/gist_id}","starred_url":"https://api.github.com/users/xxnet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xxnet/subscriptions","organizations_url":"https://api.github.com/users/xxnet/orgs","repos_url":"https://api.github.com/users/xxnet/repos","events_url":"https://api.github.com/users/xxnet/events{/privacy}","received_events_url":"https://api.github.com/users/xxnet/received_events","type":"User","site_admin":false},"created_at":"2015-07-04T08:16:33Z","updated_at":"2015-07-04T08:16:33Z","body":"同意你的观点，这里只做一个整理，对于顺序并不理想。\r\n\r\n我们先把问题梳理一遍：\r\n\r\n1. 这里有一个是逻辑顺序\r\n  像写文章一样，先说明什么。\r\n  如果是汇报bug，一般先说清楚版本，再列设置、状态。\r\n\r\n2. 从用户角度，平时关注多的是状态、设置\r\n\r\n3. 从保护隐私角度，在报告错误时，appid应该隐藏\r\n\r\n4. 一键复制状态，这个很有用，自动把appid给隐藏掉。\r\n  可以做成一键生成报告页面，让用户把这个报告页面 反馈到issue中。\r\n  把状态、日志、如果有部署日志、也把部署日志放进去\r\n\r\n5. URL 自动跳转的方式，长度超出允许长度\r\n  GAE代理是限制的，长度限制是1024\r\n  因此如果是状态页没有问题，如果加上日志就不够了。\r\n  这个方案很方便，缺乏的日志部分，能否通过其他方法弥补？\r\n  比如提示引导？\r\n\r\n5. issues爆满\r\n  暂时也不用担心\r\n  只要不是自动触发的，需要手动操作的，不会太多。很多非技术用户还没有github帐号呢。\r\n\r\n最后方案要进一步讨论\r\n\r\n在 2015年7月4日 下午2:48，YFdyh000 <notifications@github.com>写道：\r\n\r\n> 将版本信息放在前面我觉得是很奇怪的设计，版本信息基本不会变动的，也就不必有关注的需要。\r\n> 而用户最关注的应该是“状态”信息，其次是appid、设置。\r\n> 我认为将版本信息放在最后是比较好的方式。或者，用某种方式折叠起来，但允许它被复制。\r\n>\r\n> 再或者，弄一个一键复制状态（乃至近期日志）的按钮，也省的用户自己复制日志了。\r\n>\r\n> https://github.com/XX-net/XX-Net/issues/new?title=123&body=1%0A1\r\n> 似乎是可用的方式。或许会超出URL允许长度？不过好像没问题，听说IE的限制是2048，其他无限制。但特别的系统（比如某些代理）就不一定了。以及，issue或许会爆满，那样只能开另一个库的issue作为非开发反馈系统。\r\n>\r\n> —\r\n> Reply to this email directly or view it on GitHub\r\n> <https://github.com/XX-net/XX-Net/issues/568>.\r\n>\r\n"}}