Not against.

Consistency is a great thing.

One of the new CMS features I like a lot is the "search tools" button that hides the search and filter fields. Should be possible to implement something similar ?

It is possible. Can we postpone "search tools" to 1.x ? This task can be done together with the personal query filters.

So, what should the order be? I think the Status column is redundant (covered by the toggle button), but there is a drop-down also referred to as - status -. I think - status - could be renamed Workflow or Stage.

I think when you are looked at Open issues you should only see the created date and when you are looking at Closed issues you should only see the closed date.

The order should be Priority - Status - Newest (date)

I think the Status column is redundant (covered by the toggle button)

May be, but the toggle button covers only two statuses and if you reset the status filter then you will not understand the current issue status. IMO this column should stay. Renaming - status - to Stage will confuse, cause it does not match column name.

I think when you are looked at Open issues you should only see the created date and when you are looking at Closed issues you should only see the closed date.

This is a point for discussion. Personally I voting to leave Opened date with the Closed filter.

Renaming - status - to Stage will confuse, cause it does not match column name.

So which filter element is the Status column mapped to? State in Github land is only Open or Closed (that's your toggle button). The other is more like what stage of the bug processing workflow you are in. No?

To be honest I'd prefer the layout that Github users for the issues list. Status toggle (Open | Closed) and list order on top. Put all other filters to the left. Ultimately we will want "Assigned to me" etc and so on so that layout would scale well.

The other is more like what stage of the bug processing workflow you are in. No?

After rethinking I have to agree with you. Toggle button currently does not represent the status - it represents the stage. So in terms of filters these are two different states, because every stage has it's own open or closed status (closed column in the #__status table). Will fix it also. Thanks. And yes, column should be renamed to the Stage accordingly :)

BTW we have #6 with a proposal to extend the current workflow.

Put all other filters to the left.

I was thinking about it too, but I am not a great designer, you know If someone can draw issues layout this would be very helpful

The toggle button between open and closed status and the stage filter/column serve (or should serve) different purposes.

If this really is to replace our current joomlacode tracker and not just be a clone of github (why would we do that) then its essential to see the stage in the bug tracking workflow that an issue is at.

I'm sorry but right now this is just a clone of github and doesnt resolve the issues we have managing the bug process that we have on github.
You may blame the J!Tracker Application for transmitting this comment.

I'm sorry but right now this is just a clone of github and doesnt resolve the issues we have managing the bug process that we have on github.

Can you list those problems or are the already somewhere where I can take a look? (serious question, not trying to be smart because everyone will have a different take on what the problems are)

I plan to do that today. I did spend a lot of time with David Hurley a few weeks ago explaining/reviewing this but I guess with other things this may have got lost.

I think the g+ group is probably the best place for me to post that ?

I think the g+ group is probably the best place for me to post that ?

Thanks. I don't think it matters where.

@brianteeman there are some thoughts in #6 also (in case you missed that).

Just a notice for me - also fix #205 along with this.