Hi all,
One of my users (with admin level access) accidentally deleted an issue. I have backups. But others have made other changes to the database since.
Is it possible to restore just the single deleted issue (without a PhD in SQL)?
Otherwise, is it possible to create a new issue but change it ...
Search found 20 matches
- 08 Dec 2025, 19:58
- Forum: Help
- Topic: Restoring a single deleted issue from backup?
- Replies: 1
- Views: 67
- 11 Aug 2021, 14:34
- Forum: Help
- Topic: Some issues no longer accessible (error #1100), or deleted?
- Replies: 5
- Views: 3779
Re: Some issues no longer accessible (error #1100), or deleted?
OK thanks, I'll check those avenues.
So I have a mysql dump from some time ago that contains the deleted issues, and I have a test server I can copy-paste the text and attachments out of, but if I recreate the issues on the production server they will of course have different numbers. Is there a ...
So I have a mysql dump from some time ago that contains the deleted issues, and I have a test server I can copy-paste the text and attachments out of, but if I recreate the issues on the production server they will of course have different numbers. Is there a ...
- 10 Aug 2021, 19:28
- Forum: Help
- Topic: Some issues no longer accessible (error #1100), or deleted?
- Replies: 5
- Views: 3779
Re: Some issues no longer accessible (error #1100), or deleted?
Thanks so much, that was helpful! It confirms the issues in question are definitely deleted. Now, is there any way I can determine how/why/when they were deleted? Do mantis or mysql log such things?
- 09 Aug 2021, 19:25
- Forum: Help
- Topic: Some issues no longer accessible (error #1100), or deleted?
- Replies: 5
- Views: 3779
Some issues no longer accessible (error #1100), or deleted?
Hi all,
Some coworkers did the following:
- created a new project ("Foo")
- moved some existing issues into the new project
- confirmed in 'view issues' that the issues were there
- made the new project ("Foo") a subproject of another project ("Bar")
Then all the issues that were members of "Foo ...
Some coworkers did the following:
- created a new project ("Foo")
- moved some existing issues into the new project
- confirmed in 'view issues' that the issues were there
- made the new project ("Foo") a subproject of another project ("Bar")
Then all the issues that were members of "Foo ...
- 15 Jun 2021, 17:54
- Forum: General Plugin Discussion
- Topic: public examples of gitlab integration?
- Replies: 0
- Views: 36876
public examples of gitlab integration?
Hi all,
I know MantisBT's own tracker uses the github integration:
https://mantisbt.org/bugs/my_view_page.php
but I'm wondering if there are any public Mantis servers (for some open source project for example) that uses the gitlab integration. I've started using the gitlab integration, and am ...
I know MantisBT's own tracker uses the github integration:
https://mantisbt.org/bugs/my_view_page.php
but I'm wondering if there are any public Mantis servers (for some open source project for example) that uses the gitlab integration. I've started using the gitlab integration, and am ...
- 11 May 2021, 20:07
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
We've just found a second occurrence, so it's probably not cosmic rays. 
If it would help, and if you're willing, I can share the full headers of the emails that got misfiled. But not on this public forum. I could email you at the address you make your git commits from, if that's ok with you?
If it would help, and if you're willing, I can share the full headers of the emails that got misfiled. But not on this public forum. I could email you at the address you make your git commits from, if that's ok with you?
- 10 May 2021, 20:58
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
I have those two settings as 'strict' and 'yes', respectively.
The first email in the thread was titled "Problème avec la mise à jour à l'Université Laval". It created ticket 11183. My boss replied, and that got attached to 11183. The customer replied twice, and both those emails got attached. My ...
The first email in the thread was titled "Problème avec la mise à jour à l'Université Laval". It created ticket 11183. My boss replied, and that got attached to 11183. The customer replied twice, and both those emails got attached. My ...
- 10 May 2021, 19:18
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
So this has all been working pretty well for me for a few weeks now, but just spotted a case of an email reply getting attached to the wrong ticket in mantis. How do I troubleshoot that? Upon examining a new email, how does it decide which existing ticket (if any) to attach it to? Does it look at ...
- 23 Feb 2021, 20:50
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
That worked, thanks!
- 19 Feb 2021, 18:11
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
So I've confirmed what's happening.
The parse_from_field() function uses the following regex:
/^(?:(?P<name>.*)<|)(?P<email>(?P<local>[a-zA-Z0-9.!#$%&'*+\/=?^_`{|}~-]+)@(?P<domain>[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*))(?:>|)$/u
against ...
The parse_from_field() function uses the following regex:
/^(?:(?P<name>.*)<|)(?P<email>(?P<local>[a-zA-Z0-9.!#$%&'*+\/=?^_`{|}~-]+)@(?P<domain>[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\.[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?)*))(?:>|)$/u
against ...
- 16 Feb 2021, 04:37
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
Yup, I can redirect the cron output, just wanted to make sure your plugin doesn't already have some log functionality built-in.
Thanks for the hint re: email_is_valid(). I've looked through the code a bit. I'll add some print statements and see if I can be sure exactly what's happening...
Thanks for the hint re: email_is_valid(). I've looked through the code a bit. I'll add some print statements and see if I can be sure exactly what's happening...
- 15 Feb 2021, 18:29
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
So is there no log file of the results of running each cron job?
Anyway, I disabled my cron job, used 'redirect' to send another message, and ran "bug_report_mail.php" manually, and looked at the output. Seems the problem is:
2021-02-15 12:36 EST MAIL_VERBOSE email_api.php:141 email_is_valid ...
Anyway, I disabled my cron job, used 'redirect' to send another message, and ran "bug_report_mail.php" manually, and looked at the output. Seems the problem is:
2021-02-15 12:36 EST MAIL_VERBOSE email_api.php:141 email_is_valid ...
- 12 Feb 2021, 20:56
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
SL-Gundam, I've noticed something else... sometimes customers will write to employees personally, for example to sean@example.com, instead of to the managed support@example.com address. When this occurs, our current workflow is for employess to use 'redirect' (not 'forward') to redirect the message ...
- 06 Feb 2021, 16:30
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
Thanks for your reply.
I already have:
- $g_bug_readonly_status_threshold = CLOSED;
- Use Message-ID in Mail header to identify notes = yes
- What kind of search should be used to find the issue id in the subject = strict
But I'm not sure that last one is so relevant for me, since subject never ...
I already have:
- $g_bug_readonly_status_threshold = CLOSED;
- Use Message-ID in Mail header to identify notes = yes
- What kind of search should be used to find the issue id in the subject = strict
But I'm not sure that last one is so relevant for me, since subject never ...
- 04 Feb 2021, 19:11
- Forum: EmailReporting
- Topic: Help with customer suport use case: how to reply to created tickets?
- Replies: 27
- Views: 115817
Re: Help with customer suport use case: how to reply to created tickets?
So I've found a workflow that works reasonably well for us so far:
Our public support@example.com is actually a mailman list. I created a new IMAP email account foobar@example.com. I subscribed that account to the mailman list. EmailReporting uses IMAP to check the foobar@example.com account. Our ...
Our public support@example.com is actually a mailman list. I created a new IMAP email account foobar@example.com. I subscribed that account to the mailman list. EmailReporting uses IMAP to check the foobar@example.com account. Our ...