Loading Profile...
Recent activity
Subscribe to this feed
Ashley Laing marked one of Jeremy Lecour's replies in Next Update as useful. Jeremy Lecour replied to the idea "Freeform tagging".
-
Ashley Laing replied on September 22, 2009 23:08 to the idea "Freeform tagging" in Next Update:
Free form tag would add a huge amount of flexibility to an already great application. I have a few client with various project that need different grouping of issues.
Free form tags, even something as simple as simple one of the many act_as_taggable variations.
Show the tags as filters would make working with Sifter ever easier, and allow issues to be group in very natural ways. -
Ashley Laing started following the idea "Freeform tagging" in Next Update.
-
Ashley Laing shared an idea in Next Update on September 20, 2009 20:33:
Filter Issues by Company NameWe often manage project that involve 4-5 companies and each company can have 5-50 people involved.
Often, as a manager of a project, you want to get a quick view of everything your team is working on for a given project. A filter on Company name would make this very easy.
Right now you have to filter by selecting the names of all team members. With a long list of 30-100 people on a single project this is a slow process. -
Ashley Laing started following the idea "Basecamp integration? Issue to To Do migration" in Next Update.
-
Ashley Laing replied on September 20, 2009 20:20 to the question "How do I close a milestone?" in Next Update:
I am having the same issue with milestones. I don't want to delete them because then I loose the grouping of issues, and thats no good as the milestones often tie back to releases.
Ability to closing a milestone would be perfect.
Another thing that would help is making the dashboard display more milestones. Currently the dashboard only displays stats at 2 levels:
- fully picture status
- current milestone (of 1st -by date- milestone listed)
It would be very helpfully if the dashboard included stats for all milestones that haven't been closed. Or give an option on each milestone to say "include this milestone on the dashboard" which is on by default. -
Ashley Laing shared an idea in Next Update on August 28, 2009 13:47:
Linking duplicate issues/bugs will help...During testing and QA of an application or site is common to have many people testing. And thus you often have 2 or more people find the same issue. We encourage our testers to search existing issues to see if their problem has already been reported, but inevitably some issues get reported more than once.
It would be great if Sifter had a quick may to indicate issue ABC is a duplicate of issue XYZ. Thus simplifying the process of linking duplicates and closing them all when a problem is resolved.
