Mantis Bug Tracker - Forums

For forum readers, this issue seems to have been resolved via this bug

I meant your first case, clone the database, and delete what you don't need in each one. Yes, I think you will lose relationships between issues that end up in different databases, but what else would you expect? You can't have a "relationship" with something outside of your own instance. ...

1. No, each project has a defined workflow. You may create a sub-project with a different workflow though. 2. You can clone an existing issue. Is that what you're asking? 3. No, you would need to clone an issue and forward one of them to the second project. Although there are open issues asking for ...

Dump the database, restore into multiple databases, configure each Mantis instance to talk to its own DB, and delete extra projects in each.

See bug #10066. You probably have bugs becoming read-only in Resolved state, so most changes are prohibited.

Thks for ypur reply. i am using mantis 1.1.4 version .. I suggest upgrading to 1.1.6. 1. This is frequently receiving at the time of New user Login .ie when the user goes for activation. Probably bug #9713 2. At the time of posting the error(ie Report issue link) Probably bug #9754 or #9869

There were several bugs fixed recently related to this error. Make sure you're running version 1.1.6, or a recent snapshot of 1.2.0.

If you are, please describe exactly what version you have, under what conditions you get the error, and what browser you're using.

Bug #8572. I've added a note about your case.

In your Gmail, could you do "Show original" (from the message menu, top right), and cut & paste the Subject line here.

Go here and subscribe to mantisbt-announce mailing list. You may also "monitor" releases on Sourceforge (click on the envelope icon in the "Notes / Monitor" column).

My guess is you're looking at the Permissions Report page. You need to click another tab, in a new row of links at the top that opened up -- click on "E-mail Notifications". What version of Mantis are you using?

I think you're running into this bug.

Go into Manage Config -> E-mail Notifications, and the options you're looking for are there. For example, if you check the box for "Status changes to 'new'" under "Developer", all developers will get mail about new bugs.

Try setting $g_email_send_using_cronjob = OFF.

The instructions for upgrading are here. I suggest you get the latest stable version (currently 1.1.6) instead of 1.1.2. Then you access admin/upgrade.php to convert the database, then admin/install.php to finish the install.