Your description is somewhat confusing (e.g. what do you mean by "All Projects screen" ?), and you are not providing much details either (e.g. error messages, logs...)

Anyway your problem sounds like https://mantisbt.org/docs/master/en-US/Admin_Guide/html-desktop/#admin.troubleshooting.errors.2800, so most likely a system configuration issue and not a bug in Mantis.

Example:

1. Mantis is idle on "All Projects" (see A in the attached picture)
2. I use the drop down shown the picture to select another project (see B in the attached picture as an example)
3. Now Mantis shows project "B" as selected
4. I click on Report Issue while (I assume) I am "in project B"
5. I create an issue and click on Save - at that moment Mantis returns to "All Projects" (see A) and the default view - the Issue is not saved at all, there is no trace of it, there is no error message

This has been going on since I had Mantis installed on AWS through Bitnami.

image.png (85,794 bytes)   

image.png (85,794 bytes)   

I am not able to reproduce your problem.

When you select a project as per your screenshot, you're indeed setting it as default so you are indeed "in project B". Any issue you create will be in this project.
Upon submission of the New Issue report form, you should see a confirmation page with 2 buttons, allowing you to either view the newly created issue, or go to View Issues page.
There is no returning to "All Projects"

Maybe this is something Bitnami does.

My sysadmin tells me out Mantis install is the same as the regular distribution so I assume it's not Bitnami.
This keeps happening no matter what we do. It is driving me NUTS.
The "report issue: process loses focus and then nothing gets saved. The timeout limits we have set are huge so that is probably not that.
I am so fed up I am about to stop using it which sucks because the entire tam depends on it.

I am hoping I find someone really knowledgeable about Mantis on AWS who I can pay to resolve this issue.

Sorry to hear that, but not having a clear understanding of the problem or being able to reproduce the issue, I really can't help you.

About your sysadmin: not sure what "the same as the regular distribution" is supposed to mean, or what "timeout limits" you are referring to... Anyway did you check your session.gc_* settings in php.ini, as indicated in the link I posted before in 0029046:0065821 ?

Is there anyone here who can fix my installation? I am willing to pay for the effort.

At this point I am a free-weekend away from ditching MantisBT as a failed experiment. It is just too frustrating to use. We first use the Bitnami installation, then we installed it completely from scratch. Same issue. It seems to have problems with browser cache. Sometimes I cannot switch to a project I want to use. Sometimes it will refuse to focus on a specific issue I select. If I clear the browser cache it MAY help alleviate these problems or it may not. Sometimes I have to clear the cache AND switch browsers. I know,; it sounds insane and just because you have never seen this behavior doesn't make it any less real for me.

I created a new user account for myself as it appears that these issue only happen for my login.
Will see what happens with the new login.

The issue persists in all browsers. About 50% of the time I am kicked back to All Projects when I try to view issues for any particular project. Or, when I try to add a new issue to any project. Ten I must clear the cache and THEN I can do what I need to, for a short time. Then the same thing starts. This happens to me on all 3 of my computers.

IS THERE ANYONE HERE BRAVE ENOUGH TO HELP ME WITH THIS MANTIS BUG?

Considering that you still have not provided any useful information that would help reproducing the issue, I fail to see how I or anyone would be able to help with what may, or may not, be a bug in MantisBT.

@dregad Please stop responding to this ticket as clearly you are unable to understand it. I found a developer outside of this community who gave me some useful pointers that I expect will help. If you represent this forum then I feel there is little hope.

I found a developer outside of this community who gave me some useful pointers that I expect will help.

Please add a note with the useful pointers you got, as this might help other MantisBT users that are affected by similar issues.

@andyetc1000

I strongly resent your implication that I am unable to understand, when the actual problem is that you did not provide sufficient information for me to do so.

You come here asking for help, so the least you could do is show some basic courtesy and spare your derogatory comments to the people who take the time to respond to your request. And keep in mind that you're getting it for free, too.

Like it or not, considering that I have been voluntarily developing MantisBT and actively supporting this community for more than 10 years - on my spare time, I might add - I believe I do somewhat represent it... So if you are not happy with the support you're getting here, you are more than welcome to go look for it elsewhere. If you intend to stay, then please show some respect.

Best regards

@atrol This is a short version of the advice I received. I would credit the person but I am not sure if He would want me to.

"It sounds more like something with the sessions on the server. What I see as odd in your issue is that when it occurs you end up in the "All Projects" page. When you select a project in the dropdown that project will be the default project and stored as a cookie in the browser: MANTIS_PROJECT_COOKIE with the project id as the content. "All projects" is probably your default project in your account. It is usually the default setting. To me it sounds like the PHP session times out and also that the MANTIS_PROJECT_COOKIE might not be set correctly in your browser. You can check the cookies in your browser and what cookies are set and the content they have.
The settings that I think could affect this - this is from my php.ini:
session.cookie_lifetime = 0
session.gc_maxlifetime = 1440"

I checked and my settings were:
cookie_lifetime set to 0
gc_maxlifetime set to 7200

So unfortunately this was not the solution.

The problem persists.

One new observation..

Let' say I select a project from the drop down list and I see Mantis hesitate for 2-3 seconds.. if I do nothing, it will just go to "All Projects" (same as "All Projects" in this forum interface). But if, during those 2-3 seconds I click on the browser's refresh icon, it will actually go to that project.

Same will happen if, when with a project selected, I click on View Issues and it hesitates.

In Firefox, when I observe this behavior, I can also try Cntrl-Shift-Del to invoke the popup below, clear the checked items, and then Mantis will work OK for some time.

image-2.png (27,598 bytes)   

image-2.png (27,598 bytes)   

@dregad I am sure you know everything there is to know about MantisBT. That is not my issue. My problem with your posts here is that all you keep repeating is "not enough information". I drew you a picture for Pete's sake.

I was also not able to reproduce (tried different versions, servers, operating systems, ...)

Did you check that

• MANTIS_PROJECT_COOKIE is set right after changing the project
• there are not any errors or warnings in browser console
• there are not any errors or warnings in server logs (web server, PHP, database)
• any browser plugins you might have installed are disabled / uninstalled
• there is not any proxy or firewall sitting between the browser you use and the server

Thank you for the ideas. The cookie does change wen I select a new/different project. Also seeing this on Submit Issue

!function(a,b){"object"==typeof module&&"object"==typeof module.exports?module.exports=a.document?b(a,!0):function(a){if(!a.document)throw new Error("jQuery requires a window with a document");return b(a)}:b(a)}("undefined"!=typeof window?window:this,function(a,b){var c=[],d=a.document,e=c.slice,f=c.concat,g=c.push,h=c.indexOf,i={},j=i.toString,k=i.hasOwnProperty,l={},m="2.2.4",n=function(a,b){return new n.fn.init(a,b)},o=/^[\s\uFEFF\xA0]+|[\s\uFEFF\xA0]+$/g,p=/^-ms-/,q=/-([\da-z])/gi,r=function(a,b){return b.toUpperCase()};n.fn=n.prototype={jquery:m,constructor:n,selector:"",length:0,toArray:function(){return e.call(this)},get:function(a){return null!=a?0>a?this[a+this.length]:this[a]:e.call(this)},pushStack:function(a){var b=n.merge(this.constructor(),a);return b.prevObject=this,b.context=this.context,b},each:function(a){return n.each(this,a)},map:function(a){return this.pushStack(n.map(this,function(b,c){return a.call(b,c,b)}))},slice:function(){return this.pushStack(e.apply(this,arguments))},first:function(){return this.eq(0)},last:function(){return this.eq(-1)},eq:function(a){var b=this.length,c=+a+(0>a?b:0);return this.pushStack(c>=0&&b>c?[this[c]]:[])},end:function(){return

image-4.png (36,037 bytes)   

image-4.png (36,037 bytes)   

image-3.png (66,873 bytes)   

image-3.png (66,873 bytes)   

Why are you pausing on caught exceptions ? That does not make any sense.

See https://github.com/jquery/jquery/issues/3551