{"action":"created","issue":{"url":"https://api.github.com/repos/taigaio/taiga-front/issues/866","repository_url":"https://api.github.com/repos/taigaio/taiga-front","labels_url":"https://api.github.com/repos/taigaio/taiga-front/issues/866/labels{/name}","comments_url":"https://api.github.com/repos/taigaio/taiga-front/issues/866/comments","events_url":"https://api.github.com/repos/taigaio/taiga-front/issues/866/events","html_url":"https://github.com/taigaio/taiga-front/issues/866","id":132264148,"number":866,"title":"Sprint backlog becomes difficult to assign backlog tasks to sprints. ","user":{"login":"levibostian","id":2041082,"avatar_url":"https://avatars.githubusercontent.com/u/2041082?v=3","gravatar_id":"","url":"https://api.github.com/users/levibostian","html_url":"https://github.com/levibostian","followers_url":"https://api.github.com/users/levibostian/followers","following_url":"https://api.github.com/users/levibostian/following{/other_user}","gists_url":"https://api.github.com/users/levibostian/gists{/gist_id}","starred_url":"https://api.github.com/users/levibostian/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/levibostian/subscriptions","organizations_url":"https://api.github.com/users/levibostian/orgs","repos_url":"https://api.github.com/users/levibostian/repos","events_url":"https://api.github.com/users/levibostian/events{/privacy}","received_events_url":"https://api.github.com/users/levibostian/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-08T21:42:13Z","updated_at":"2016-02-14T22:10:52Z","closed_at":"2016-02-09T07:07:30Z","body":"This is an annoyance that I have encountered while being a user of Taiga. (Simply here to offer an improvement to this amazing platform. I want to thank you all so very much for creating Taiga. I have completely switched all of my scrum/agile projects over to Taiga and I am planning on using it for the distant future I am in love with it! I also recommend it to dozens of others.) \r\n\r\n---\r\n\r\nIn the sprint backlog screen I insert a bunch of user stories. Lets say, 4 dozen user stories. After creating this long scrollable list of user stories, I want to create sprints for all of these user stories and assign each user story to a sprint. \r\n\r\nSo I create sprints along the right hand side of the screen and then I drag user stories into each sprint. Everything technically works great. \r\n\r\nBut from a UX standpoint, it can be a bit of a pain. Lets say a user story on the very top of my backlog list goes into sprint 12 which is far down the screen, I need to drag my user story down the screen until I see sprint 10 to drag it inside of it. \r\n\r\nSure, I can collapse sprint's user stories but if I click on a user story and go back to the backlog, all of the sprints all uncollapse so I am back to square one. \r\n\r\nOne idea that I had, have the sprint backlog become 2 separate scrollable lists. So the backlog tasks can be scrolled up and down and the sprints list can be separately scrolled up and down. This would be very helpful and solve my issue I believe. "},"comment":{"url":"https://api.github.com/repos/taigaio/taiga-front/issues/comments/183990376","html_url":"https://github.com/taigaio/taiga-front/issues/866#issuecomment-183990376","issue_url":"https://api.github.com/repos/taigaio/taiga-front/issues/866","id":183990376,"user":{"login":"levibostian","id":2041082,"avatar_url":"https://avatars.githubusercontent.com/u/2041082?v=3","gravatar_id":"","url":"https://api.github.com/users/levibostian","html_url":"https://github.com/levibostian","followers_url":"https://api.github.com/users/levibostian/followers","following_url":"https://api.github.com/users/levibostian/following{/other_user}","gists_url":"https://api.github.com/users/levibostian/gists{/gist_id}","starred_url":"https://api.github.com/users/levibostian/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/levibostian/subscriptions","organizations_url":"https://api.github.com/users/levibostian/orgs","repos_url":"https://api.github.com/users/levibostian/repos","events_url":"https://api.github.com/users/levibostian/events{/privacy}","received_events_url":"https://api.github.com/users/levibostian/received_events","type":"User","site_admin":false},"created_at":"2016-02-14T22:10:52Z","updated_at":"2016-02-14T22:10:52Z","body":"Thanks again. I did not know that the doomline existed. I have never set the max points and/or number sprints in the admin settings as my projects do not have a max for either of these. My projects deadlines are set when the functionality of the software is complete. I still really like having an icebox to set aside user stories as things that are simply not very important and I will use in a different iteration of development. \r\n\r\nI *could* satisfy my needs with your suggestion by counting the number of points that are not in my icebox and set that in my admin settings but that seems like work I should not have to do. Wouldn't it be better if Taiga did this math for me by just labeling user stories as \"iceboxed\". \r\n\r\n---\r\n\r\nLet me explain that idea. The backlog has a section for the icebox for you to drag in user stories into it (don't know the UX for this yet but that is not important here). As I am creating user stories and assigning points to them, I can put user stories into the icebox as I go along. So in the end, I may/may not have user stories in my icebox, I have user stories in my backlog built up and I have a sprint created. Perfect now I am ready for my development iteration. \r\n\r\nNow, the icebox functionality is useful because it sets the maximum number sprints and/or maximum number points *for you* by summing up the points in each section (backlog and icebox) instead of having me do that math manually.\r\n\r\nThis would be great for people like me who do not have a set deadline for a project (determined by settings max number sprints/story points) but for people like you who still want to set a deadline you can still go into the admin settings and everything works as it doe already. \r\n\r\nWhat are your thoughts?"}}