convore.json/groups/github/new-issues-management-system/messages.json

[{"user_id": 16254, "stars": [], "topic_id": 18353, "date_created": 1302431238.926543, "message": "Cool, but it would be better if we could manually close milestones, and link them to tags.", "group_id": 591, "id": 608805}, {"user_id": 9896, "stars": [], "topic_id": 18353, "date_created": 1302434826.177736, "message": "how do I delete a milestone though if I added it accidentally?", "group_id": 591, "id": 609097}, {"user_id": 9896, "stars": [{"date_created": 1303387277.6610899, "user_id": 28606}], "topic_id": 18353, "date_created": 1302434869.4267211, "message": "also what would be super cool is: Merging several issues (duplicates...) into one", "group_id": 591, "id": 609100}, {"user_id": 16254, "stars": [], "topic_id": 18353, "date_created": 1302460428.322618, "message": "Yep... Also, the remaining issues counter in the milestones seems to be wrong (may be cache ?)", "group_id": 591, "id": 612143}, {"user_id": 28592, "stars": [], "topic_id": 18353, "date_created": 1302471454.8707399, "message": "hello guys!", "group_id": 591, "id": 614186}, {"user_id": 25106, "stars": [], "topic_id": 18353, "date_created": 1302478718.070354, "message": "I wonder, now that GitHub has a real issue system, if the lack of issue \"resolution\" (ie. \"fixed\", \"wontfix\", \"worksforme\") is an intentional omission. Having just switched from Trac to Redmine, setting issue resolution has become too cumbersome to be worth it. Is this type of feature on its way out? Are labels / tags supposed to work as a substitute?", "group_id": 591, "id": 615656}, {"user_id": 3617, "stars": [{"date_created": 1302701758.090863, "user_id": 8391}], "topic_id": 18353, "date_created": 1302478958.2873671, "message": "@ramen I never saw 'resolution' status as terribly useful. When you close an issue, just state why. I don't really see searching for 'wontfix' tickets as terribly useful.", "group_id": 591, "id": 615683}, {"user_id": 9896, "stars": [{"date_created": 1302544845.4534891, "user_id": 25106}, {"date_created": 1302545879.01247, "user_id": 5928}, {"date_created": 1302564875.955369, "user_id": 2009}, {"date_created": 1302701768.5988319, "user_id": 8391}], "topic_id": 18353, "date_created": 1302518842.9436989, "message": "Finally used the new issue tracker with milestones for some real work, I hope you github guys now how epically #winning this finally useable issue tracker is!", "group_id": 591, "id": 622845}, {"user_id": 28647, "stars": [], "topic_id": 18353, "date_created": 1302624546.316577, "message": "The new issue tracker is amazing!! You guys just need to update the screenshots on the static page about issue tracking ;)", "group_id": 591, "id": 644532}, {"user_id": 13919, "stars": [], "topic_id": 18353, "date_created": 1302630913.444767, "message": "After assigning completed tasks to a Milestone I can't assign incomplete issues because it things the Milestone is closed. How do I assign issues to a closed milestone?", "group_id": 591, "id": 646733}, {"user_id": 13919, "stars": [], "topic_id": 18353, "date_created": 1302630999.966213, "message": "And the new tracker is great BTW. Good work! :)", "group_id": 591, "id": 646778}, {"user_id": 3, "stars": [], "topic_id": 18353, "date_created": 1302633558.3706639, "message": "@sethvargo what static page", "group_id": 591, "id": 647401}, {"user_id": 1167, "stars": [], "topic_id": 18353, "date_created": 1302634317.7537479, "message": "@defunkt I guess it's https://github.com/features/projects/issues", "group_id": 591, "id": 647554}, {"user_id": 28647, "stars": [], "topic_id": 18353, "date_created": 1302636986.9208219, "message": "@defunkt - https://github.com/features/projects/issues. It still shows the old issues screen shot", "group_id": 591, "id": 648254}, {"user_id": 3, "stars": [{"date_created": 1303987944.670089, "user_id": 28606}], "topic_id": 18353, "date_created": 1302644472.774153, "message": "@judofyr yes", "group_id": 591, "id": 651294}, {"user_id": 3, "stars": [], "topic_id": 18353, "date_created": 1302644482.553869, "message": "the SHA", "group_id": 591, "id": 651296}, {"user_id": 3, "stars": [], "topic_id": 18353, "date_created": 1302644904.0138271, "message": "whoops, thanks @brutasse and @sethvargo", "group_id": 591, "id": 651381}, {"user_id": 3, "stars": [], "topic_id": 18353, "date_created": 1302644484.743161, "message": "(full sha)", "group_id": 591, "id": 651297}, {"user_id": 3, "stars": [], "topic_id": 18353, "date_created": 1302644912.29828, "message": "our asset caching may be a tad bit aggressive", "group_id": 591, "id": 651389}, {"user_id": 3, "stars": [], "topic_id": 18353, "date_created": 1302644930.5636599, "message": "@judofyr i see - don't think there's a way to do that yet", "group_id": 591, "id": 651395}, {"user_id": 1516, "stars": [], "topic_id": 18353, "date_created": 1302644542.824568, "message": "I just got a pretty link: https://github.com/rtomayko/tilt/issues/69 (the \"Some cleanup\" comment)", "group_id": 591, "id": 651310}, {"user_id": 1516, "stars": [], "topic_id": 18353, "date_created": 1302644561.3234961, "message": "not the \"referenced this issue from a commit\" as here: https://github.com/rtomayko/tilt/issues/74", "group_id": 591, "id": 651313}, {"user_id": 1516, "stars": [], "topic_id": 18353, "date_created": 1302644447.0337999, "message": "is there a way to reference commits in an issue (just like the commit msg included the issue ID)? I often forget to tag the commit msgs", "group_id": 591, "id": 651290}, {"user_id": 4935, "stars": [], "topic_id": 18353, "date_created": 1302680675.714627, "message": "pretty sweet! added a milestone for a little OSS project of mine (as of now it's just me): https://github.com/jsonista/jsonista/issues?milestone=2&state=open", "group_id": 591, "id": 661085}, {"user_id": 1516, "stars": [], "topic_id": 18353, "date_created": 1302687482.8795061, "message": "oh, and I can't seem to add a new issue to a milestone that's closed. I actually had to manually find the milestone ID, and modify the issue[milestone_id] when I created the issue.", "group_id": 591, "id": 662137}, {"user_id": 14243, "stars": [], "topic_id": 18353, "date_created": 1302701560.540817, "message": "It would be awesome if I had 'status' to the issues. Like 'assigned' 'started' 'finished' 'delivered' 'accepted' 'rejected'", "group_id": 591, "id": 665024}, {"user_id": 960, "stars": [], "topic_id": 18353, "date_created": 1302701627.1421871, "message": "@aseba what about using tags for those?", "group_id": 591, "id": 665038}, {"user_id": 14243, "stars": [], "topic_id": 18353, "date_created": 1302707500.5406239, "message": "@undefined yep, i've used that and it goes well thanks :)", "group_id": 591, "id": 666078}, {"user_id": 14243, "stars": [], "topic_id": 18353, "date_created": 1302707526.3821969, "message": "something that bothers me, is that everyone gets emails. Even if the issue is not assigned to you", "group_id": 591, "id": 666081}, {"user_id": 14243, "stars": [], "topic_id": 18353, "date_created": 1302707552.361793, "message": "other thing, the creator of the issue doesn't get an email when the issue is closed", "group_id": 591, "id": 666083}, {"user_id": 19, "stars": [{"date_created": 1302825012.7622311, "user_id": 4149}, {"date_created": 1302833705.408823, "user_id": 3617}, {"date_created": 1302846284.0350389, "user_id": 8391}, {"date_created": 1302877387.7351019, "user_id": 1516}, {"date_created": 1303103497.064153, "user_id": 10411}, {"date_created": 1303241350.3014901, "user_id": 25106}], "topic_id": 18353, "date_created": 1302824800.0255821, "message": "@ramen I've always found that real text is the solution for those problems. \"I'm not going to fix this because I don't think it's a bug \u2014 let me explain\" <-- way higher value than generically tagging something \"wontfix\"", "group_id": 591, "id": 692573}, {"user_id": 30526, "stars": [], "topic_id": 18353, "date_created": 1303385846.2803121, "message": "I can't find the interface to create new labels with!  Where'd it go?", "group_id": 591, "id": 768748}, {"user_id": 19, "stars": [{"date_created": 1303517498.032655, "user_id": 8391}], "topic_id": 18353, "date_created": 1303420054.0977521, "message": "http://share.kyleneath.com/captures/Issues_-_github_github_-_GitHub-20110421-140726.png", "group_id": 591, "id": 775757}, {"user_id": 19, "stars": [], "topic_id": 18353, "date_created": 1303420056.753056, "message": "At the bottom of the labels list", "group_id": 591, "id": 775758}, {"user_id": 26038, "stars": [], "topic_id": 18353, "date_created": 1303747922.989193, "message": "@defunkt There's also a bug on that static page: the link at the bottom says \u201cBack to Integrated Issue Tracking\u201d but that's the page you're already on. Guessing it should be \u201cBack to Git Powered Wikis\u201d.", "group_id": 591, "id": 804755}, {"user_id": 28606, "stars": [], "topic_id": 18353, "date_created": 1303763772.6815751, "message": "The new issue mgmt system rocks! Been using it a lot lately.", "group_id": 591, "id": 807046}, {"user_id": 28606, "stars": [], "topic_id": 18353, "date_created": 1303764187.5433581, "message": "It would be nice if people can upvote issues (features, bugs, etc.) to get a feeling of how important is a feature/etc. to the users. That can be used as an input signal for prioritization.", "group_id": 591, "id": 807142}, {"user_id": 19, "stars": [], "topic_id": 18353, "date_created": 1303765972.2716999, "message": "I think we ran the numbers and something like 0.1% of issues had more than 1 vote", "group_id": 591, "id": 807385}, {"user_id": 19, "stars": [], "topic_id": 18353, "date_created": 1303765927.5874121, "message": "@fcarriedo: We actually used to have that feature \u2014 almost no one used it at all", "group_id": 591, "id": 807378}, {"user_id": 19, "stars": [], "topic_id": 18353, "date_created": 1303765944.811554, "message": "I think it's a social problem... project maintainers want users to vote on issues, but the truth is no one does in practice", "group_id": 591, "id": 807381}, {"user_id": 28606, "stars": [], "topic_id": 18353, "date_created": 1303766437.9880519, "message": "=(", "group_id": 591, "id": 807450}, {"user_id": 4156, "stars": [], "topic_id": 18353, "date_created": 1303783416.399919, "message": "Maintainer-set priorities > voting IMO. having zero way to sort issues priority-wise is a big pain point. Labels don't solve that problem well.", "group_id": 591, "id": 809018}, {"user_id": 2320, "stars": [], "topic_id": 18353, "date_created": 1303828180.958564, "message": "@bitprophet How would you do improve it in a way that's not easily achievable through labels?", "group_id": 591, "id": 814980}, {"user_id": 4156, "stars": [], "topic_id": 18353, "date_created": 1303839881.1518481, "message": "Main idea is that I'm hoping there is a way to implement some method of sorting issues which can stay within Github's design/UI constraints.", "group_id": 591, "id": 817043}, {"user_id": 4156, "stars": [], "topic_id": 18353, "date_created": 1303839790.8566141, "message": "@catsby There'd need to be some way to assign weights to labels so they could be sorted.  Or add a new priority field. I'm assuming a \"Github-like\" way of doing this might involve a hardcoded set of ordered priorities (eg low, normal, high, blocker -- etc), possibly with a way for individual repos to override the names if they wanted.", "group_id": 591, "id": 817027}, {"user_id": 19, "stars": [], "topic_id": 18353, "date_created": 1303842320.092207, "message": "http://www.43folders.com/2009/04/28/priorities is very relevant", "group_id": 591, "id": 817400}, {"user_id": 19, "stars": [{"date_created": 1303843484.171593, "user_id": 141}, {"date_created": 1303870145.4036191, "user_id": 2320}, {"date_created": 1303910007.650588, "user_id": 19952}, {"date_created": 1304746451.7638791, "user_id": 8391}], "topic_id": 18353, "date_created": 1303842350.023042, "message": "In my experience, things are either a priority or they are not. Which is why labels work so great for that action. You can have \"blockers\" or you can have \"nicetohaves\"", "group_id": 591, "id": 817405}, {"user_id": 1767, "stars": [], "topic_id": 18353, "date_created": 1303844529.810909, "message": "@kneath But prioritizing is not sorting. I think that's @bitprophet's main idea. I'm totally fine with labels, but some people are used to have sortable issue attributes.", "group_id": 591, "id": 817715}, {"user_id": 4156, "stars": [], "topic_id": 18353, "date_created": 1303854262.9360509, "message": "Though I definitely acknowledge Merlin's post on the subject. It's just very hard to change old habits :(", "group_id": 591, "id": 819252}, {"user_id": 4156, "stars": [], "topic_id": 18353, "date_created": 1303853992.284744, "message": "Pretty much what @koraktor said. It's a workflow I and a lot of other people are very used to, and it makes the idea of migrating to Github that much harder to sell. Which is a shame given the rest of the upgrades to Issues.", "group_id": 591, "id": 819203}, {"user_id": 2320, "stars": [], "topic_id": 18353, "date_created": 1303870726.493721, "message": "@bitprophet I agree with @kneath, things are a priority or they are not.  If you have so many items that are priority such that you need another attribute with which to sort them, then IMO you have failed to actually prioritize. You've simple added another layer in the name of organization, at the cost of actually doing something.", "group_id": 591, "id": 820918}, {"user_id": 16204, "stars": [], "topic_id": 18353, "date_created": 1304448439.032342, "message": "I would really like it if assigning a ticket to somebody issued a notification in GH Issues. Just adding my +1.", "group_id": 591, "id": 901644}, {"user_id": 5794, "stars": [{"date_created": 1304630998.821414, "user_id": 4156}], "topic_id": 18353, "date_created": 1304630783.2842679, "message": "I'd say the thought that \"it's either priority or it's not\" falls down when you start adding in milestones. Something that is a priority for one milestone that's 1.0 has nothing to do priority wise with a milestone 2.0. So why would I want to see everything that's labelled as a blocker for a release that I'm not even thinking about yet?", "group_id": 591, "id": 934796}, {"user_id": 19, "stars": [], "topic_id": 18353, "date_created": 1304709353.481653, "message": "@morganiangoose: I can't say I understand what you mean at all. You can show all issues labeled blocker in a particular milestone pretty easily (just add a milestone filter).  Ex: https://github.com/sinatra/sinatra/issues?labels=release&sort=created&direction=desc&state=open&page=1&milestone=7", "group_id": 591, "id": 945080}, {"user_id": 2320, "stars": [{"date_created": 1304975682.7388141, "user_id": 8391}, {"date_created": 1305006999.017375, "user_id": 28370}], "topic_id": 18353, "date_created": 1304947022.100383, "message": "@morganiangoose To me that sounds more like *organization* and not *prioritization*.", "group_id": 591, "id": 971362}]