Post posted March 4, 2011 by Anshul Garg, last edited February 9, 2012
1069 Views, 15 Comments
Topic:
Configurable Pagination for List View
Body:
Hi,
Currently, the list view is restricted to 25 cards per page (and the number is not configurable). Is it possible to make this number configurable. Also there should be an option to list all the cards.
Some examples:
I’ve got projects with more than 25 cards to consider when they plan their next sprint and it would be easier if you could see all in one list instead of clicking next page.
If you want to set a property on all cards you’ve got to do that several times instead of just once by choosing “All”.
If you use a property like “Importance” it’s nice to sort by importance and also to se all cards (have the right one the highest and the right one the lowest number).
So in my ideal world a configurable list view (all or 25 perhaps) would be perfect.
I believe you both mention bulk update and having to repeat this across pages. There is an option to select "All" which means all cards across all the pages as well as "All" on this page. Have you seen this option? I think it will help you bulk update more easily.
Hi Suzie,
Yes, we've seen the "All" option but it's not really useful if you want to update 3 cards on page one and then 2 on the second and... I think you understand what I mean. Show all would solve this easily
Agree with what Lisa has mentioned. Mostly this is for viewing more than 25 cards.
Examples:
Need to set properties for cards. List view is helpful in this as I can add columns to it like estimates, iterations etc and then select some cards based on those properties and edit them. But having only 25 cards restricts me and forces me to go to next page and doing the repeat of my actions.
Also the list view helps in quickly finding the card by using "Find" (Ctrl/Command + f) from the browser and entering some keyword. This is only partially possible in grid view as the complete text for the story name is not rendered.
While managing stories, I find list view more helpful and powerful to use as I can select the columns that I need to see. I can sort the cards based on the columns and also it gives me the full text for the story name which gives me more context. And hence would like not to be restricted to 25 cards.
Sometimes you can get around this limitation by using other views.
If you want to set a property, you can often use a grid view. In the estimates example that Anshul gave, if you group the cards by estimate, you can drag the cards to the appropriate lane to set the card estimate. In this usage, estimation sessions are generally an exercise of moving cards from "not set" to a specific estimate lane.
If you just want to see a bunch of cards, and those cards are in a tree, the hierarchy view is a good option, as there is no pagination on that page.
Comment
You'll get my vote on this!
Please add till the next release.
/Lisa
I'm interested in why you both like this. What tasks can't you do with 25 cards? Do you want to see more or less cards? Why?
- Suzie
Hi Suzie,
Some examples:
I’ve got projects with more than 25 cards to consider when they plan their next sprint and it would be easier if you could see all in one list instead of clicking next page.
If you want to set a property on all cards you’ve got to do that several times instead of just once by choosing “All”.
If you use a property like “Importance” it’s nice to sort by importance and also to se all cards (have the right one the highest and the right one the lowest number).
So in my ideal world a configurable list view (all or 25 perhaps) would be perfect.
I’m sure Anshul has more examples.
/Lisa
Hi Lisa and Anshul
I believe you both mention bulk update and having to repeat this across pages. There is an option to select "All" which means all cards across all the pages as well as "All" on this page. Have you seen this option? I think it will help you bulk update more easily.
Let me know what you think
- Suzie
Hi Suzie,
Yes, we've seen the "All" option but it's not really useful if you want to update 3 cards on page one and then 2 on the second and... I think you understand what I mean. Show all would solve this easily
/Lisa
Hi Suzie,
Agree with what Lisa has mentioned. Mostly this is for viewing more than 25 cards.
Examples:
Need to set properties for cards. List view is helpful in this as I can add columns to it like estimates, iterations etc and then select some cards based on those properties and edit them. But having only 25 cards restricts me and forces me to go to next page and doing the repeat of my actions.
Also the list view helps in quickly finding the card by using "Find" (Ctrl/Command + f) from the browser and entering some keyword. This is only partially possible in grid view as the complete text for the story name is not rendered.
While managing stories, I find list view more helpful and powerful to use as I can select the columns that I need to see. I can sort the cards based on the columns and also it gives me the full text for the story name which gives me more context. And hence would like not to be restricted to 25 cards.
Thanks
Anshul
Hi,
I know its not a fix but I use Google Chrome for Mingle and an extension called FastestChrome.
This will load the next pages quickly and then has the bonus of being able to search all the pages at once using (Cntl +F)
Hope this helps
Russ
Hi,
Chrome is not an option here, so hopefully we can have a >25 card list in the next release.
/Lisa
I've added this request to the Mingle backlog.
Sometimes you can get around this limitation by using other views.
If you want to set a property, you can often use a grid view. In the estimates example that Anshul gave, if you group the cards by estimate, you can drag the cards to the appropriate lane to set the card estimate. In this usage, estimation sessions are generally an exercise of moving cards from "not set" to a specific estimate lane.
If you just want to see a bunch of cards, and those cards are in a tree, the hierarchy view is a good option, as there is no pagination on that page.
My name is Sam and I agree that this request would be helpful.
Hi,
Any news if this will be a part of next release?
/Lisa
Hi, I'd really like this feature too because I can not delete cards via the mingle API.
So when I need to delete over 300 cards, it means I have to page twelve times. It's not fun.
Even better perhaps, I'd to be able to delete cards via the mingle api.
Michelle
Hi,
Any news if this will be a part of next release?
/Lisa
Hi,
Please, could this be a part of the next release?
/Lisa
Hi,
Since this request is now added to the Mingle backlog, have you planed it in any release yet?
/Lisa