Issue #2919 was marked as a duplicate of this issue.
Not being able to read the title makes the screen pretty useless. This has made it almost impossible to search for issues.
The issue's impact could be reduced if we had a way to choose which columns display ( #2922 ). Or if the window width was not fixed, so I could enlarge the browser window.
Personally I would like to see each row containing ONLY title/status/type/date and then all the other details could appear on :hover or something with a nice little popup (similar to hovering on the issue number in Google Code's tracker)
Sorry for the trouble. In our initial rollout of the change we did not realize how squashed the summary was going to be for some users.
We have rolled out an update that we feel is a much better experience. We hope you like the new look.
Is there a way to add back the version and component fields?
We decided, @shyrahnama, that there's simply not enough room to devote columns to these. Keep in mind, though, that it's still possible to include these data in custom queries, and they are displayed when viewing individual issues.
Thanks for the clarification David.
It would be sweet if that were configurable in project admin.. ..managing 2-week sprints on a project, it's helpful to see what's now and what's next using the version and component.
@David -- Our process is to tightly limit the scope of each version so as to release-early-and-release-often, and as a result we have a whole bunch of versions queued up way in advance. In order to prioritize which issue is worked on next, we must be able to see which issues have been assigned to which versions.
As you might guess, removing the version column from the Issue Tracker without giving us a way to restore it throws a huge wrench into our workflow and requires us to inspect each issue one-by-one. It also makes it pretty much impossible to get a "big picture" of what's coming up down the road.
Can you please reconsider you decision to remove the version column without providing a way to restore it? If that's not possible, how about giving us the ability to "group by" version and displaying a header for each version? That would give us the ability to see version assignments without taking up horizontal space on the table.
“[…] how about giving us the ability to "group by" version and displaying a header for each version? That would give us the ability to see version assignments without taking up horizontal space on the table.”
This is a fantastic idea. As you say, it would allow issues to be grouped by component, milestone, or version without necessitating a reduction in the width of any of the columns. Moreover, it's arguably a better means of grouping since it removes redundancy.
Thanks for the highly constructive feedback. I'm excited about this suggestion, and look forward to discussing it with the rest of the team tomorrow.
p.s. I'm closing this issue to avoid confusion, since Friday's release did address the concern raised by the OP.