Loading Profile...
Design (formatting) suggestions for the Project Pages
I think the dashboard page is really really clear. Neat and well done.
However when you go into a project page the opposite is true. It's really confusing.
You lose the ability to scan down the list in the same way.
the extra fields on this page are
- Category
- Comments
- Assigned by / Opened by
I would suggest keeping the assigned by and opened by as you have done it, but moving the "Last comment by" under this.
I don't think the exact details of when the last comment were made need to be shown. You're more interested if this was recently, or a while a go, or a long while ago.
You could do this by having it as red if ti was within the last day or two. orange in the alst week, and grey if it's older than that.
The rest you could lay out like the normal dashboard and squeezing in the category flag.
I find this page very difficult to read, yet the dashboard page very easy.
Just my 2c.
However when you go into a project page the opposite is true. It's really confusing.
You lose the ability to scan down the list in the same way.
the extra fields on this page are
- Category
- Comments
- Assigned by / Opened by
I would suggest keeping the assigned by and opened by as you have done it, but moving the "Last comment by" under this.
I don't think the exact details of when the last comment were made need to be shown. You're more interested if this was recently, or a while a go, or a long while ago.
You could do this by having it as red if ti was within the last day or two. orange in the alst week, and grey if it's older than that.
The rest you could lay out like the normal dashboard and squeezing in the category flag.
I find this page very difficult to read, yet the dashboard page very easy.
Just my 2c.
I’m happy making suggestions
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
The best point from the company
-
I'm glad you like the dashboard. We've still got plenty of improvements that we can make, and it will inevitably evolve over time.
This is something that's difficult. You wouldn't believe the number of issue summary layouts that I've explored. It's impossible to fit everything on one line without making the page cramped. The content invariably wraps to two lines. As a result, the current configuration is the one that came out on top. It's not ideal, but it makes the fewest compromises.
While category and the comment meta data could arguably be considered superfluous for some people, the remaining information would still too much to fit on one line comfortably.
There are likely ways that we could optimize the comment information, and I'll definitely give that some more thought. I'm not sure color is the way to do it because it would be competing with the status and priority for attention, but I'm sure I can come up with something.
The details of who made the last comment are actually relevant in a lot of scenarios. I find myself regularly looking to see who made the last comment because that lets me know whether I've read the latest on every issue.
The issue listing page definitely have room for improvement. I won't argue with that, but until we redesign the whole page (a low priority relative to features that we have yet to implement) it's unlike that we'll make any significant changes due to the lack of horizontal space.
That said, this is definitely good to know and keep in mind, so thanks for taking the time to share. In the meantime, I'll see if I can't tidy up the meta data under the subject.
I’m appreciative of the feedback
The company thinks
this is one of the best points
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?I'm glad you like the dashboard. We've still got plenty of improvements that we can make, and it will inevitably evolve over time.
This is something that's difficult. You wouldn't believe the number of issue summary layouts that I've explored. It's impossible to fit everything on one line without making the page cramped. The content invariably wraps to two lines. As a result, the current configuration is the one that came out on top. It's not ideal, but it makes the fewest compromises.
While category and the comment meta data could arguably be considered superfluous for some people, the remaining information would still too much to fit on one line comfortably.
There are likely ways that we could optimize the comment information, and I'll definitely give that some more thought. I'm not sure color is the way to do it because it would be competing with the status and priority for attention, but I'm sure I can come up with something.
The details of who made the last comment are actually relevant in a lot of scenarios. I find myself regularly looking to see who made the last comment because that lets me know whether I've read the latest on every issue.
The issue listing page definitely have room for improvement. I won't argue with that, but until we redesign the whole page (a low priority relative to features that we have yet to implement) it's unlike that we'll make any significant changes due to the lack of horizontal space.
That said, this is definitely good to know and keep in mind, so thanks for taking the time to share. In the meantime, I'll see if I can't tidy up the meta data under the subject.
I’m appreciative of the feedback
The company thinks
this is one of the best points
-
Inappropriate?All fair points.
Some simplier suggestions then:
The priority and state get hard to scan and glance down a list. Priority doesn't have to be a word but can just be a letter in the styles you do the words or even a coloured circle (various shades of red perhaps). This would give space to then put this on the right.
I find it very hard to find a ticket number on this page. I'd rather have it more squashed up between the state and the title (even if it's smaller) than where it is now. It's impossible to find as it's never in the same place.
I think you could add a third line to the layout.
Having a space between the title and the Catagory / Age would make the page easier to read and then allow you to put the comment information IN FULL under the Assigned by / Opened by area, where it would be more relevant.
I’m thankful
-
Inappropriate?Unfortunately, it's just not that simple. Making priority just a letter decreases the learnability of the system, and our single most important goal is to have something that non-technical people can get in and use without feeling alienated or confused. I even contemplated and explored using symbols for communicating priority, but
The ticket number problem is a valid point, but we felt that the subject is more important than the ticket number. It actually used to be on the left of the subject, but then it interfered with the ability to scan the subject, so it was relegated to a less important location.
Adding a third line actually makes a significant negative impact on things because it decreases the amount of issues that fit on the screen (or a printed page) significantly. It ends up creating a lot of wasted white space without dramatically improving anything.
I promise, we've tried a lot of different things (including almost all of these recommendations), but the dynamic nature and varying length of the subject, category, and people's names makes it very difficult to successfully rearrange things.
I'm not disagreeing that there's room for improvement. :) I just know from trying it that it's not easy. I won't give up, though. I'll certainly explore some of these things to see if there are tweaks I can make so that it works better. -
Inappropriate?Yeah totally understand and all valid points.
Just trying to show how I use the system and what I would find useful. Know it's not that easy or simple to find the best solution.
One thing I'll add is whilst the titles are more useful to identify a ticket, the numbers are useful to refer to in an email/ skype chat / commit message / other ticket. And so if they are hard to find it's a real pain.
Perhaps a solution would be to have a toggle that shifts the display between dashboard mode and detail mode?
-
Inappropriate?The real solution for the issue numbers is an undocumented feature. You can type an issue number in the search box, and you'll go straight to it.
Hope that helps. (And I probably need to find a way to make that more obvious.)
I’m thankful
-
Inappropriate?I didn't know that, and it's useful.
However doesn't solve the issue of trying to find which number I'm talking about in a Skype chat with our developers who are in Poland (we are in London).
We have lots of skype chats that go,
"And wrt. to ticket #13, I mean #17, no it's ticket #13" etc
Same in emails, and on commit messages "This solves bug #12" etc
-
Inappropriate?Yeah, that makes sense. That's why it's highly visible on the issue detail page. Maybe there's something I can do to punch it up a bit without drowning out the other info.
-
Inappropriate?Yeah. We have a 'project' for each major release of work rather than 1 project with lots of stuff in it.
As a project gets done that will get closed and we'll start a new one.
So when working with or testing a particular project I shift off the dashboard.
-
Inappropriate?Sound like another vote for us to get to work on Milestones. (Sub-projects within projects.) The current plan is to add that in after the API which is on our plate right now.1 Comment Add a comment
This is one of the best points
-
Well that would also make it interesting to how much I need Basecamp as well as then.
Although we tend to use Basecamp for speccing out a work unit and Sifter for solving bugs with the work unit during testing.
EMPLOYEE
