I was looking for different search methods and was on the Dr. Project site. Their ticketing system doesn’t need a search ability. Now that I think of it, unless the project has thousands of tickets, a search is not necessary. Then again, for a large project that might have many archived tickets, it might be convenient to go back and look through them if it’s necessary. This would also help searching through all the wiki pages as well. Perhaps we don’t need Search to be exclusively for the ticketing system.
I was also looking at what YouTube has in terms of a search. I like the auto completing (this may be a browser feature. I’m not sure). So if we do implement a Search for tickets, it might be useful to allow the user to start inputting a ticket topic and auto-complete it for them. That would be nifty. I was also looking at the tagging system. After talking to some users, they say that they don’t use them that often. I think that the search-bar with auto-complete is sufficient for our purposes.
I haven’t gotten a chance to talk to either Jason or Liz about the setting the number of tickets per page options yet. I’d like to discuss other options for that feature with them before I ask users to test it. Alone, I wasn’t able to come up with a better idea. So, hopefully, together we could come up with some.
There are several ways to display updates to users. It is still unclear which would be best. Again, waiting to talk to Jason and Liz this weekend.