Make a Copy of Record Before Deletion

Get help from other users here.

Moderators: Developer, Contributor

Post Reply
asiflalani
Posts: 3
Joined: 26 May 2014, 11:09

Make a Copy of Record Before Deletion

Post by asiflalani »

Help Required to make a copy of a selected record with history before deletion to a specific table, which can only be used by Manager OR Administrator for references.
paul
Posts: 43
Joined: 11 Mar 2005, 11:18

Re: Make a Copy of Record Before Deletion

Post by paul »

a) do you actually want to delete the issue - remember if an issue is closed it doesn't appear in the default filters so is 'hidden'

b) if you do want to delete the issue, I'd probably be inclined to say you'd need to create a custom plugin to mantis to do this (That hooks the delete event) and performs some export of the data before then processing the deletion.
Would you be interested in testing support for non-mysql backends for MantisBT? if yes, please email paul@mantisforge.org
asiflalani
Posts: 3
Joined: 26 May 2014, 11:09

Re: Make a Copy of Record Before Deletion

Post by asiflalani »

Thanks Paul.

But is there any Plugin already available, which works accordingly with the same practice ?
I don't know Mantis much deeply.

Further, for workout process i prepared one Project with the name: Deleted/Archived
Where instead of deletion of record i am transferring it to the above named project.

But here the problem is, if i wanted to know from which Main Project that record was been transferred i am unable to get in CSV / Excel Based Report.
Is there any other way to show up the Previous Project Name & Current Project Name in such cases of movement of Issues. ?
atrol
Site Admin
Posts: 8553
Joined: 26 Mar 2008, 21:37
Location: Germany

Re: Make a Copy of Record Before Deletion

Post by atrol »

I would create a private project where just managers and administrators have access to.
Move the issue to that project.
Please use Search before posting and read the Manual
paul
Posts: 43
Joined: 11 Mar 2005, 11:18

Re: Make a Copy of Record Before Deletion

Post by paul »

What about creating multiple private sub-projects (as atrol / yourself seem to have worked out) - one for each main project?

- Project A
- Project B
- Archives
-- Archive A
-- Archive B

This would at least let you keep the issues separate.

If you could outline the reason you are doing this a bit more (trying to get an understanding of how many projects and why you actually need to move the issues rather then just leave them as closed), it could be we could try and get a plugin created that allows the issues to get moved automatically to the archive project(s).

Atrol; I'm thinking at first glance to keep this tidy for end users, the concept of having "hidden" subprojects could be good - where they exist, but do not appear in the project selector on the top right (but do appear in the project selector when filtering/reporting)
Would you be interested in testing support for non-mysql backends for MantisBT? if yes, please email paul@mantisforge.org
Post Reply