Hi,

The website has been restored to working order.
SVN should be working again, Mantis has been updated to the latest version.

We're still working on some features, for example emails are not yet being sent.

Michael.

PM Michael Van Canneyt wrote

... Mantis has been updated to the latest version.

That's a bit of a shock.
It looks horrible to me ;-(

Oh, the new bugtracker skin is ... hmm, not so bad, but I'm rather conservative.  
Well, life is change. :-)
 
Vojtěch
 

So I am not alone (I chose more diplomatic words).  
Vojtěch

Vojtěch Čihák wrote

Oh, the new bugtracker skin is ... hmm, not so bad, but I'm rather conservative.   Well, life is change. :-)

It is the default skin of mantis.

The server has only just been updated.
Proposals for alternatives are always welcome.

Michael.

Knock yourself out with CSS. Maybe we should organize a contest :)

Michael.

I can (if needs must) get used to the look. Maybe this would help? https://github.com/mantisbt-plugins/MantisBT-Colorized

What I find more disturbing is the new "my view"
The "Timeline" seems of little use (it does not even have issue tittles..) Better to have the old sections. Not sure they can be set to the old layout. The only thing I found
https://mantisbt.org/forums/viewtopic.php?t=21189
But I wouldn't want any of them gone entirely.

No, you are not alone. Mantis and SVN: Yuch!

---- On Sat, 20 Apr 2019 18:35:22 -0400 Vojtěch Čihák via lazarus wrote ----

So I am not alone (I chose more diplomatic words).

Vojtěch

______________________________________________________________

On Sat, Apr 20, 2019 at 11:36 PM Michael Van Canneyt via lazarus

... Mantis has been updated to the latest version.

That's a bit of a shock.

It looks horrible to me ;-(

AM Martin Frb wrote

I can (if needs must) get used to the look. Maybe this would help? https://github.com/mantisbt-plugins/MantisBT-Colorized

Yes, I miss the colors.

What I find more disturbing is the new "my view" The "Timeline" seems of little use (it does not even have issue tittles..)

+1

Better to have the old sections.

I really dislike that all "blocks/tables" (assigned to me, unassigned etc) are now all below each other, much more scrolling needed.

I hid the timeline (folded it up).
Now that I re-visit the bugtracker I can only see "assigned to me" and " unsasigned" , all others are just gone

WTF?

Trying to access "my account" always gives me this message: "You are visiting a secure page, and your secure session has expired. Please authenticate yourself to continue."

DougC wrote

No, you are not alone. Mantis and SVN: Yuch!

Yes, yes, yes, we're looking into switching git.

Such things take time.

Michael.

Indeed.

Better to have the old sections. Not sure they can be set to the old layout. The only thing I found https://mantisbt.org/forums/viewtopic.php?t=21189 But I wouldn't want any of them gone entirely.

I switched to the old layout as much as possible.

There is a bug in mantis that makes it hard,
but I worked around it with the configuration :)

Michael.

On Sat, Apr 20, 2019 at 6:42 PM Martin Frb via lazarus <

wrote: I can (if needs must) get used to the look. Maybe this would help? https://github.com/mantisbt-plugins/MantisBT-Colorized

+1
It does worth installation.
perception of items is much more clear then the entire raw is colored to the status (as it used to be).
Rather than a small little square.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190420/5df8067a/attachment.html>

I only see
"assigned to me"
recent
unnasigned

what about
reported by me
and others?

When I open a report and scroll down to the "Activities" the width of the text column is much too narrow, hardly usable, while the width of the author/date/info column is much too wide. It looks to me as if these two column widths are interchanged.

And why the the note text in the "Activities" in bold?

Werner Pamler wrote

When I open a report and scroll down to the "Activities" the width of the text column is much too narrow, hardly usable, while the width of the author/date/info column is much too wide. It looks to me as if these two column widths are interchanged.

Looks OK here. But Jonas reported something similar.

And why the the note text in the "Activities" in bold?

No idea. I don't see this.

Michael.

Which issue did you open.

I tried https://bugs.freepascal.org/view.php?id=35339 in firefox, chrome, edge.
All ok (in respect to column width)

I added reported by me again.

Seeing that there is a bug in mantis (it only shows itself when you DON't want the timeline, which you don't want...) makes it hard.

Michael.

My last Mantis issue (about macOS dark theme) has lost the PNG attachment.

AT

This one?
https://bugs.freepascal.org/view.php?id=35426

How many images? I still see one image (snippet from the toolbar)

Thanks for the update! It is already MantisBT 2.20.0. I am OK with changed appearance. Life is about changes... I will study the details later.

Juha

Chrome and Edge ok, Firefox has the issue. I deactivated all my extensions one by one and found that the issue is due to VTZilla. Strangely enough the error remains gone when I activate VTZilla again.

Michael Van Canneyt wrote

, Mantis has been updated to the latest version.

There may be an issue with search being case sensitive https://forum.lazarus.freepascal.org/index.php/topic,45123.msg318408.html#msg318408

Oddly enough Mantis 2.21 was released on April 20th https://mantisbt.org/bugs/changelog_page.php?project=mantisbt&version=2.21.0

On Sun, Apr 21, 2019 at 6:52 AM Martin Frb via lazarus <

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190421/5f9e07dc/attachment.html>

Seriously ? You must be kidding me...

And it fixes just the bugs I was experiencing...

OK. will download and upgrade.

Michael.

Updated.

My View page is now indeed correctly responding to settings.

Michael.

Michael Van Canneyt wrote

Updated. My View page is now indeed correctly responding to settings.

Much better, but still missing "monitored by me"

PM Michael Van Canneyt wrote

My View page is now indeed correctly responding to settings.

I miss "Monitored by me"

I do have the rest back again though:
- Assigned to me
- Unassigned
- Reported by me
- Resolved
- Recently modified

Until we have something better, a very crude greasemonkey script (tested with firefox)

// ==UserScript==
// @name     mantis
// @version  1
// @grant    none
// @include https://bugs.freepascal.org/*
// @include http://bugs.freepascal.org/*
// ==/UserScript==
function GM_addStyle (cssStr) {
     var D               = document;
     var newNode         = D.createElement ('style');
     newNode.textContent = cssStr;
     var targ    = D.getElementsByTagName ('head')[0] || D.body ||
D.documentElement;
     targ.appendChild (newNode);
}
GM_addStyle (`
.my-buglist-id, .column-status, .bug-status {
   position: relative !important;
   z-index: 0 !important;
}
`);
GM_addStyle (`
.fa-status-box {
   width: 100% !important;
   height: 100% !important;
   position: absolute !important;
   top:  0px !important;
   left: 0px !important;
   z-index: -1 !important;
   font-size: 15em !important;
   overflow: hidden !important;
}
`);

PM Bart wrote

I miss "Monitored by me"

Martin beat me to that ;-(

Added.

Michael.

I added another solution suggested by florian,

https://www.ryadel.com/en/mantis-bt-2-enable-row-level-coloring-like-v1-jquery-javascript/

Michael.

The colors are different though...

And the background on bug-notes is far to dark now.

It's just colors. Knock yourself out on designing a theme.

I don't intend to spend another minute on it. I've been on this since days, anyone pronouncing the word mantis in my presence will get his keyboard inserted in a place where the sun usually doesn't shine.

Michael.

No problem, I solved it locally for me.

And I appreciate the time spent by you.

Martin Frb wrote

And the background on bug-notes is far to dark now.

For anyone who is interested, here is my latest greasemonkey (tested on firefox)

And screenshots:
https://i.imgur.com/PjGYpEb.png
https://i.imgur.com/Ffkuxq1.png
https://i.imgur.com/xakd2ag.png
https://i.imgur.com/uopHcxW.png

// ==UserScript==
// @name     mantis
// @version  1
// @grant    none
// @include https://bugs.freepascal.org/*
// @include http://bugs.freepascal.org/*
// @require
https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
// ==/UserScript==
   $(".fa-status-box").each(function() {
     var $this = $(this);
     var col = $this.css('color');
     $this.closest("td").css("background-color", col);
   });
function GM_addStyle (cssStr) {
     var D               = document;
     var newNode         = D.createElement ('style');
     newNode.textContent = cssStr;
     var targ    = D.getElementsByTagName ('head')[0] || D.body ||
D.documentElement;
     targ.appendChild (newNode);
}

GM_addStyle (`
.my-buglist-id, .column-status, .bug-status {
  position: relative !important;
  z-index: 0 !important;
}

.table-striped>tbody>tr:nth-of-type(odd) {
 background-color:#f9f9f9 !important;
}
.table-striped>tbody>tr:nth-of-type(even) {
 background-color:#fff !important;
}

.my-buglist-id .fa-status-box, .column-status .fa-status-box, .bug-status .fa-status-box {
  display: none !important;
}

th.category, td.category {
    background-color: #e8e8e8 !important;
}
td.bugnote-note {
    background-color: #f9f9f9 !important;
}
`);

PM Martin Frb wrote

The colors are different though...

I can't see the difference between closed, resolved and assigned. The only distinct colors I can see are for new and acknowledged. This getting to be a nightmare.

Not really, a nightmare is for example when you find yourself naked on top of El Castillo in Chichen Itza amidst a cheering crowd, while some priest with bloodshot eyes uses a stone knife to peel off your skin and cut out your heart, showing it triumphantly to foresaid crowd...

Then you wake up in your own cold sweat and with a sigh of relief realize we're no longer living in the age of the Mayas.

Now that definitely counts as a nightmare.

By contrast: Difficult to discern colors (sic) is a minor inconvenience.

I did some adjustments, please let me know whether this is better for you. Make sure you do a forced reload of the page.

Michael.

Well, today's fads of those "dark themes" or "flat look" are more a PITA than truly a nightmare

Only if you're a child back in those days, as an adult, you were pretty safe. But then today a lot of folks have problems growing up...

By contrast: Difficult to discern colors (sic) is a minor inconvenience.

That is a very personal experience. I had a customer who set up here computer is the most nausea inducing (for me) color scheme of pink, purple, neon green and yellow. I could not work on if for 2 minutes, but she was getting her job done each day of the week just fine.

But I have lots of clients complaining about all those "flat" menues in M$ Office and such, which makes it hard specially for older people to discern the different functionalities, because it all looks the same. A lot of "modern UX" folks should be taken out to the alley and stuck in a dumpster...

Ralf

---
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

If you fanatically believe in your sacrifice appeasing an otherwise angry deity.... Dream of a lifetime (not mine, though)

I did some adjustments, please let me know whether this is better for you. Make sure you do a forced reload of the page.

Better colors, but trouble to see the normal prior indicator on some of them.

If interested, the below should fix that:

.my-buglist-id .fa-lg {
  text-shadow: 0px 0px 1px #444;
}
.my-buglist-id .fa-paperclip {
  text-shadow: 0px 0px 0px #000;
}

And maybe also
grey the fixed field in the view issue page / though interrupts the color for state:

th.category, td.category {
    background-color: #e8e8e8 !important;
}

and  for prior symbols on the search results

.column-priority .fa-lg {
  text-shadow: 0px 0px 1px #444;
}

I’m testing on Safari (Mac) and all the links are red. Should I file a bug report? ;)

Regards,
Ryan Joseph

Ryan Joseph wrote

I’m testing on Safari (Mac) and all the links are red. Should I file a bug report? ;)

red background, red foreground?

Javascript enabled?

One more. If people have no JavaScript enabled

Drop the css
.my-buglist-id .fa-status-box, .column-status .fa-status-box, .bug-status .fa-status-box {
    display: none !important;
}

and add the js (inside the unnamed function in colorize.js)

   $(".my-buglist-id .fa-status-box").each(function() {
     var $this = $(this);
     $this.attr('style', 'display: none !important');
   });
   $(".column-status .fa-status-box").each(function() {
     var $this = $(this);
     $this.attr('style', 'display: none !important');
   });
   $(".bug-status .fa-status-box").each(function() {
     var $this = $(this);
     $this.attr('style', 'display: none !important');
   });

Red foreground. The background colors are properly colored based on status but the yellow dash icons are pretty hard to see now though.

JavaScript is on. All browsers are affected, Safari, Firefox and Chrome.

Regards,
Ryan Joseph

Ryan Joseph wrote

Red foreground. The background colors are properly colored based on status but the yellow dash icons are pretty hard to see now though.

red text, changing to blue when you hover. Same for me.  That seems to be the intend.
They were red before https://i.imgur.com/PjGYpEb.png  (The background color changed from the image)

I sent some bits of css, that I hope will get applied, to fix the "yellow dash" (and all other priority indicators).

On Apr 22, 2019, at 8:23 PM, Martin Frb via lazarus wrote: red text, changing to blue when you hover. Same for me. That seems to be the intend. They were red before https://i.imgur.com/PjGYpEb.png (The background color changed from the image)

The red text appeared after some changes so I don’t think it was intended. Looks pretty off also imo.

Regards,
Ryan Joseph

ehm...

Why would I want it in Javascript when it is better to have it in the CSS ?

Michael.

I applied it.

Michael.

I am slowly getting used to it.

Writing notes to some bug reports I noticed an annoying issue, though: While typing the text does not wrap any more when it becomes wider than the memo (after pressing "Add Note" the text is wrapped however). I considers this important to facilitate proof-reading the text before submission. BTW, are regular users (i.e. without developer status) able to edit their own text after uploading? As I remember from my non-developer days this was not possible. Therefore, it is even more important that the text is wrapped before sending. Otherwise we will be plagued with more and more unreadable submissions.

Werner

Sorry, but it appears some "trash" went into it

.my-buglist-id .fa-lg {

    text-shadow: 0px 0px 1px #444;

}
.my-buglist-id .fa-paperclip {

    text-shadow: 0px 0px 0px #000;

}

.column-priority .fa-lg {

    text-shadow: 0px 0px 1px #444;

}

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190423/b14a0ae6/attachment.html>

this may help, if added

textarea {
  white-space: pre-wrap;
}

Sorry for slightly off-topic: I use this addon: https://darkreader.org/ if I am not satisfied with default web page colors. It works pretty well but I prefer dark colors.

23. 4. 2019 v 11:56, Martin Frb via lazarus :

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190423/2f2108cc/attachment.html>

Trash is here "Â" ?

Michael.

Added, please test.

Michael.

This is in the css file, and prevents the entry from being processed.

Not all editors show the char. So it may be some invalid utf8 or such.

Changed, please test.

Michael.

Same extra trash char.

yes the yellow minus is ok now.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190423/9adfb6d9/attachment-0001.html>

Changed.

I do copy&paste from your mail, so somehow it ends up in your mails... &nbsp; or so ?

Michael.

On Apr 23, 2019, at 6:57 AM, Martin Frb via lazarus wrote: yes the yellow minus is ok now.

Nice, looks better. Is the red link color going to be changed? It doesn’t look , Ryan Joseph

Yes, it works. Thank you, Martin and Michael

AM Michael Van Canneyt wrote

I applied it.

Much better now.
Only the green for Resolved is so pale it hardly contrasts with Closed.

Bart

AM Werner Pamler wrote

BTW, are regular users (i.e. without developer status) able to edit their own text after uploading? As I remember from my non-developer days this was not possible.

Yes, they are.
I'm just reporter in fpc, but I can edit (and delete) my notes.

Bart

I made it darker.

Michael.

Michael Van Canneyt wrote

I made it darker.

If Bart agrees, and if it is not asking to much (I know its been a lot of mantis this week)

Can we go halfway between the new and the old green?

If you give me the RGB in hex, yes, sure.

My RGB hex is not so fluent that I can say
"A halfway between '#51efab' and '#cceedd', no sugar or milk, please"

Michael.

8EEFC4

Hi,
 
original appearance on Wayback machine: https://web.archive.org/web/20171104124226/https://bugs.freepascal.org/view_all_bug_page.php  
V.
______________________________________________________________

8EEFC4

Thanks. Applied, but I honestly don't see a lot of difference...

Michael.

Vojtěch Čihák wrote

Hi,   original appearance on Wayback machine: https://web.archive.org/web/20171104124226/https://bugs.freepascal.org/view_all_bug_page.php

That is #cceedd. The algorithm to apply the color to the row adds a 70% or 80% alpha to that, so you'd need to invert that to get the original color needed to get this color again...

Michael.

On Apr 23, 2019, at 6:05 PM, Michael Van Canneyt via lazarus wrote: to get this color again...

Looks better but it’s still pretty hard on the eyes. It may be possible that entire idea of using a background color is working against us?

The official demo looks much better in my opinion (https://mantisbt.org/bugs/my_view_page.php) and still maintains the color coding. Why not use that?

Regards,
Ryan Joseph

Hello Michael,

is the "Summary" in "Viewing Issues" table centered for a purpose? Could you make it aligned to the left?

https://bugs.freepascal.org/view_all_bug_page.php

Thanks
Ondrej

Done.

Michael.

Florian requested row coding, as it was in v 1.x.

Michael.

Seemingly not everybody:
https://forum.lazarus.freepascal.org/index.php/topic,45168.msg318748

Michael Van Canneyt wrote

I do copy&paste from your mail, so somehow it ends up in your mails... &nbsp; or so ?

When copying text from webpages, dev IDE's and emails to paste somewhere I always first paste in Notepad++ then re-copy the pasted text and copy into the target. (Your favorite text editor here)

Very often the copied original contains a bunch of unwanted fluff...

Thank you!

Ondrej

Bo Berglund wrote

When copying text from webpages, dev IDE's and emails to paste somewhere I always first paste in Notepad++

Some background info:

That's because the original content is considered "rich text". But any program worth using should have an option to paste in different formats (if the original clipboard content is considered "rich text"). So there really should be an option to "paste unformatted". Email clients however tend to automatically determine the format of the pasted text based on the current email formatting (is it an HTML email or Plain text email that you are writing).

Regards,
Graeme

Quite a lot of editors, web browsers and email clients support "Ctrl+Shift+V" for "paste unformatted".

Ondrej

PM Michael Van Canneyt wrote

I made it darker.

Thank you very much!

PM Martin Frb wrote

If Bart agrees, ..

;-)

I would vote for large contrast, especially for those who may have some degree of visual impediment.

PM Vojtěch Čihák wrote

original appearance on Wayback machine: https://web.archive.org/web/20171104124226/https://bugs.freepascal.org/view_all_bug_page.php

Colorscheme in those "ancient" days:

New: #ffa0a0
Acknowledged: # ffd850
Confirmed: # ffffb0
Assigned: #c8c8ff
Feedback: #ff50a8
Resolved: #cceedd
Closed: #e8e8e8

(According to the eyedropper of my FF)

AM Werner Pamler wrote

> Yes, they are. > I'm just reporter in fpc, but I can edit (and delete) my notes. Seemingly not everybody: https://forum.lazarus.freepascal.org/index.php/topic,45168.msg318748

As of today, as reporter, I cannot edit my own notes anymore, let alone delete or make private.
This should be fixed.

As developer, the buttons to edit etc. are hidden by default and only show upon hoovering.

Bart wrote

I would vote for large contrast, especially for those who may have some degree of visual impediment.

In that case I would recommend a separate stylesheet. Take Firefox web browser for example.... In the menu "View -> Page Style -> <select stylesheet here>"

If a website supports multiple stylesheets, they would appear in that menu.

Here is a live demo:

https://developer.mozilla.org/samples/cssref/altstyles/index.html

Here is MDN (Mozilla Developer Network) documentation on it:

https://developer.mozilla.org/en-US/docs/Web/CSS/Alternative_style_sheets

Regards,
Graeme

2019. 04. 20. 23:36 keltezéssel, Michael Van Canneyt via lazarus írta:

Mantis has been updated to the latest version. We're still working on some features

Hi!

I found a minor issue...

In the old version the issues reported by me were on the top-right. Now those are on the bottom-left and the page must be scrolled to see the list.
I think that the users (reporters) may like to see their own issues on the top.
Unfortunately there is no related option in the profile settings.

Please change the order of lists (divs) as it was in the old version (if you agree).

Thanks!

Developers on the other hand want to see things assigned to them first.

Unfortunately there is no related option in the profile settings. Please change the order of lists (divs) as it was in the old version (if you agree).

There is control over the order of the boxes, but there is no control over which column a box ends up in.

I already tried various settings, none is very convenient. Normally, I would expect this to be settable on a profile or user basis. For example, I personally only work with 'assigned to me' and 'unassigned', the rest is of no use to me.

But for a reporter the 'reported by me' is more important than 'assigned to me'. It's impossible to reconcile the 2 in 1 global setting.

Maybe you can submit a feature request in the mantisbt.

Michael.

Péter Gábor wrote

In the old version the issues reported by me were on the top-right. Now those are on the bottom-left and the page must be scrolled to see the list.

Interesting, I tested in different browsers, and always get

assigned | reported by me
unassigned | resolved
recent | monitored

But if you have greasemonkey, and assuming "assigned" is your top left, then this will help

// ==UserScript==
// @name     mantis
// @version  1
// @grant    none
// @include https://bugs.freepascal.org/*
// @include http://bugs.freepascal.org/*
// @require
https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js
// ==/UserScript==
$("#reported").insertBefore($("#assigned"));

2019. 04. 25. 11:52 keltezéssel, Martin Frb via lazarus írta:

Very interesting :)
Here the layout is:

Unassigned | Resolved
Recently modified | Monitored by Me
Reported by Me

Maybe different order is defined for developers and users?

Anyway, feature request posted on mantisbt.org:
https://www.mantisbt.org/bugs/view.php?id=25716

I hope they will be positive...

2019. 04. 25. 9:13 keltezéssel, Michael Van Canneyt via lazarus írta:

Maybe you can submit a feature request in the mantisbt.

Done.

https://www.mantisbt.org/bugs/view.php?id=25716

As you can see below a developer and a reporter has different order of boxes. The only difference that I think to be important is that a developer needs "Assigned" issues at the first position. All other boxes can/must be in the same order.

2019. 04. 25. 11:52 keltezéssel, Martin Frb via lazarus írta:

I tested in different browsers, and always get assigned | reported by me unassigned | resolved recent | monitored

2019. 04. 25. 12:30 keltezéssel, Péter Gábor via lazarus írta:

Maybe different order defined for developers and reporters?

2019. 04. 25. 9:13 keltezéssel, Michael Van Canneyt via lazarus írta:

Please take a look at https://www.mantisbt.org/bugs/view.php?id=6480#c33235 This can/may be a temporary solution until mantisbt team fixes it...

Péter Gábor wrote

As you can see below a developer and a reporter has different order of boxes. The only difference that I think to be important is that a developer needs "Assigned" issues at the first position. All other boxes can/must be in the same order.

Actually it looks like the same order, if you read it left top-down, then right top-down.
Only diff, is that you do not have "assigned". So therefore you have space for another item on the left.

the order is  (or for you starting 1 at unassigned) 1: assigned, 2 unassigned, 3 recent, 4 reported, 5 resolved, 6 monitored

The layout is
1 | 4
2 | 5
3 | 6

@Michael:
*IF* the order can be configured, then maybe

1: assigned, 2 reported, 3 resolved, 4 unassigned, 5 recent, 6 monitored

For developers that would mean
assigned | unassigned
reported | recent
resolved | monitored

4 and 5 can be swapped if you prefer

The important bit is to have resolved and monitored at pos 3 and 6 => so they go to the bottom. IMHO all others are more important to see at once. (3 and 6 can be swapped too)

Users would then see reported at top left.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20190427/981a94ae/attachment.html>

I changed it to this.

Michael.

@Peter:

As a reporter you should now have "reported by me" at top left.

The "monitored by me" will still be further down. And that can not be changed.
For developers it is more important to first see, what issues are new, active (recent), etc.

2019. 04. 27. 19:02 keltezéssel, Martin Frb via lazarus írta:

Now I see the following:

Reported by me | Recently Modified
Resolved | Monitored by Me
Unassigned

It's nearly okay, however I like to see the unassigned issues before the resolved ones.
Also I think that I figured out what is (maybe) identical to the old layout:

1: assigned or unassigned
2: unassigned or assigned 
3 recent
4: monitored
5: reported
6: resolved

This way developers will get

(un)assigned | monitored
(un)assigned | reported
recent | resolved

and reporters will get (the old layout)

unassigned | reported
recent | resolved
monitored | -

Anyway... I wont be aggressive...
Thanks!

That's not possible without destroying the view of developers.

To solve this, a personalized 'my view' is needed. So you better hope they implement that soon.

Maybe everyone can upvote your request in the mantisBT :)

Michael.

good

For the rest, I can sent you sample code for grease monkey, if you want