Could we finally have this in NoesisGUI 2.0.x or 2.1?
That really would allow us to simplify some complex cases by applying reusable behavior.

Oh, not that I mind with this issue, but can other reporters see my issues now? :)

And I agree with ai_enabled, proper behavior-support would simplify various things.

Scherub, I've earned a super-power to see all the reported issues :-).

Lucky you!

I will not consider myself really lucky as I've reported 64 issues here... :-)
It's good to have this super-power - I could easily check if the issue is already reported. Less duplicated issue reports.
But let's stop using Mantis as chat :-).

Mhm, I just realized that I've reported 117 issues. Do you mean you reported 64 that are duplicates of others?

I wish I had this super-power as well. Anyone here who can give them to me, too? :D

And does the 'private' checkbox hide my notes from others? It would be good to know.

Edit: I've posted a new private note as I can't set an existing one to private. Can you see it?

I have reported total 166 issues. I'm sure 117 is also pretty much :-).
64 is what displayed on my page, perhaps it's amount of still opened issues...

Try to make private your post about "117 issues" and I will tell you if I can see it.

Hey guys, sorry for the confusion. This was not on purpose. ai_enabled shouldn't have this power, but it seems that the upgrade we did to "updater" is providing that. I think I should fix it but at the same time I think this is better...

Should we make all the previous report "private" by default and start providing public visibility to everybody?

We are a bit concerned because many clients provide here "private" information about their game.

I think your mentioned approach would be way better as it would hopefully result in less work for everyone involved. Obviously I can't speak for everyone, but many of my reported issues don't really have that much information about the games I'm working on and I would presume it's similar to all other developers.

In case you're going to change it, it's important to notify everyone beforehand, probably even highlighting it on the 'new issue' page. You could also ask all devs before you change it. :)

@ai_enabled: I presume you weren't able to read my note 4555?

Hi Jesús!
I didn't abused my new "super-power" :-). But you're right - most customers don't expect that their issue reports might become public to anyone else outside of your team. The already reported issues should be kept private as they're very often contain links on private (often non-protected/obfuscated) builds and investigation requests.
But users should be able to make these issues public by editing them (it would be best if they will be able to edit the issue title and description as well).

During the creation of new issues it would be best to have an option of marking the issue report as private or public.
The feature requests (like this one) should be always public.

Another great feature - to avoid issues duplication - is displaying "similar issues" when you print the issue title for reporting - it displays the already reported issues with similar title. Thought it makes most sense when you have too many request every day and I'm not sure if there is a Mantis plugin for this feature...

The good example is the JetBrains issue tracker - see https://youtrack.jetbrains.com/issues/RSRP try create a new issue and write "Tree view" in the title - it will find similar issues. And almost all reported issues are public (you select "visible to" when create an issue). Also they're protecting the uploaded files - so they're accessible only by admins and the author. I know we could not upload our game builds here as it will inflate Mantis DB, but you might add some protection for posted URLs by default.

@Scherub, that's correct, I cannot see it.

Regards!