Comments
Dropbox! Why must you inconsistently rotate my photos!
Backlog - great!
Apple (xcode) should have some quick drop-down implementation to make drop-down properties with slider-bars compatible.
Card attaching - in a card tree we have a card type hierarchy (Tasks below Stories). When in a Task Card at the bottom I can attach that Task Card to a Story Card, which uses a modal layer to bring up a list of Stories I can attach the Task to. This modal layer doesn't work on the ipad, which prevents it from being useful for adding cards.
Thank you both!
+1 Same feelings stated above.
My name is Sam and I agree that this request would be helpful.
We would also welcome this feature.
Jay - thanks for the tip! I'll try that next time I run into this issue.
Adam - thanks for fixing the bug in the community software - it seems to work better now.
Great, thanks! I look forward to upgrading soon!
Gotcha.
While on the subject, I just created a Table for a user because they couldn't create a Filter for what they wanted because the Filter they wanted needed access to Aggregate properties to be accurate.
Can you enable Aggregate properties for Filters? That would be great.
Here's a quick scenario:
Story->Task Tree.
User is the lead on a Project, and would like a Filter showing all incomplete Stories with only Completed Tasks under them.
Understandably, they want to see Stories that should be pushed through to completion, but for whatever reason were missed when the last of that Story's Tasks were signed off. (since we can't automate this, which is the issue above)
I can't create a Filter for this, but I can create a Table, using Aggregate Task properties on the Story level.
"Can't do in a Filter" is actually a pretty common reason I create Tables in Mingle. Users would generally rather have a Filter because they can customize it at will.
I would also like the ability to group Users into Teams.
I have 500+ Mingle users.
Some of our Projects have 100+ users.
It would be great if every user-dropdown field didn't include ALL of the users assigned to a Project.
Our company (& outsourcing) is large enough that not everyone knows everyone else's role. When looking to assign a QA resource to a role, we get a list of the 100 users attached to the Project. We have no way of knowing which ones are in QA.
Being able to assign users to a Team on their Profile page (then enabling that to be used within Projects) would be very useful.
(additional info on the user profile page would also be VERY helpful - which Projects they're part of, which cards are assigned to them, etc. Currently removing a user from the system is impossible, and even deactivating them is a huge chore)
Using this 'Team' aspect in Filters, drop-down options, wikis, etc. would all be very useful.
Man am I sick of writing these comments twice. Before upgrading Mingle, please upgrade your website. Why can I navigate to this page, compose a comment, click "Post Comment" all without being logged in?
Doing this re-directs to a Login page. Fine. And what happens after I login? I am NOT directed back to this comment page, so I'm stuck navigating back to this page & typing up this whole comment again. (similarly, hitting "Back" also does not give me my text back)
Here's another scenario (why do you need more scenarios?):
Card Tree: Story->Task.
When all Tasks below a Story have been Completed, it would be great if we could trigger the parent/story status to move forward if/when all Tasks below it are completed.
That works great for Tree View, if that was our favorite view (which it is not).
We could still really use the ability to Aggregate properties down the card tree for Grid View, List View, and Tables/Charts/Graphs.
(PS: this is my 3rd time writing this comment. while some fault may be on our network permissions, I question why I am able to get to this page and type a Reply Comment in this field without being asked to Sign In first. Upon sign-in, I am not re-directed back to this comment - I'm bumped back to the main community page, erasing what I had written. Not awesome.)
re: Trash:
Sounds like a good idea, if we were just starting to use Mingle.
Since I can't use a Transition to change a Card Type (sounds like another Feature Request to me!), we'd have to steer everyone from using the "Delete Story" Transition (which frankly makes sense), to selecting [Type] and changing to Trash.
I agree that this would remove my History Filter limitation issue in this instance, but this is not the only instance where we'd like expanded History filters, and as mentioned, I'm adverse to making our Mingle usability worse regarding Story deletion.
One example:
Currently, I have Email Subscriptions set up to send me an email when a Card is not included in a Tree (because, as mentioned in another request, I can't make a "Tree" Field required upon Card creation.
This works great, but I also get cards I'd like to filter out too, but can't. We allow users a "Soft Delete" (Status: Deleted) that still keeps the card until I make a backup before purging, but changes all it's Fields to [Not Set]. Having the ability to use a negative parameter (IS NOT Status=Deleted) would enable me to filter those cards out.
2.3