After a logout/login I correctly see all bugs in list pane, so problem is less blocking than originally thought, but anyway... present before a logout/login process.

Hi tech,
Just a clarification. I see that now is possible to customize "Bug Status" and "Bug Type" scheme. Especially the second one seems very similar to what I suggested one year ago but not completely the same thing.

You are still continuing to think to "bug" concept, infact a user could "Report a bug" that by default could have different type (functional, usability, text, ...) even if finally customizable.

It's perfect but in my opinion still not enough general. As you can see, I suggested to be able to open "tickets" not "bugs", because generally this kind of platform are very useful to track not only extraordinary tasks (such as bugs) but also ordinary ones like simple "memo", "to do things", etc.

So I suggest to replace button "Report bug" with "Report Ticket", then there should be possibility to set "ticket type" such as ones I wrote last year in my original question (obviously, now could be customizable also these).
After selected "ticket type", for example "bug", obviously selection of current "Bug type" (I would rename it "Context" in a more general way) could further specify if is a bug/ticket related to a functional topic, or usability one, or others....

What do you think about it?

I completely agree. Often bugs are strongly related to test plans and generally more than one bug could be related to the same test plan (and viceversa even if less common)

I think that hyperlinks are surely useful but only the first step. In a long description, ability to highlight single words or sentences and insert code snippets (for example as reference) could be very useful. A simple real case that happened me: My customers asked to add a specific code snippet related to Analytics in website. He provided me the exact snippet, leaving me to insert it into html code. Ability to visually distinguish it in bug detail, should be perfect.

Hi Tech, If I correctly understood, in next update I'll be able to customize both "bug types" and "bug status", am I correct? If yes.... GREAT!!!!! :-)

Jira has a specific status "recorded" to differentiate this kind of tasks. When a user write and save a new bug, it becomes in "recorded" status and remain assigned to its reporter.
Only when he'll click a "publish" button, it will become visible to all others users, becoming "confirmed", and assigned to a specific one.

Surely custom statuses will make easier this kind of manage, but maybe a specific way to mantain bugs in a "staged" version before their publication, could be very useful.

It could be very useful also the ability to insert an estimation of time needed to complete task. Than time tracking could be more complete knowing if worked time is different from estimation.

More generally, it could be very useful be able to insert rich text in Bug Detail, having the possibility to visually format text, highlight words or sentences, and maybe insert pieces of code.

I agree and sometimes We can have a father task that is detailed and split in others sub-tasks. This possibility could be very interesting.

Any news about firefox one? thanks ;-)