attachment upload to DISK into directories by ticket number

[michaelgeorge]

I am testing attachment uploads in our MantisBT installation and putting those uploads onto an NFS file system.

Since this is open-source software and our attachments could be needed for audits for up to three years, I have been asked what we would do if something happened and MantisBT was not able to properly associate uploaded documents to our changes for some reason. Currently, MantisBT creates separate directories for each Project, but then uses a unique file name across all the tickets. I am not able to determine how I can determine the bug/ticket number from the file name.

As such, we are hesitant to trust MantisBT to handle all of our Compliance documents.

Am I overlooking a setting or some mapping method that would allow tracing from the file names to the associated ticket?

[cas]

You can do that with a simple query using a tool like phpmyadmin.
I you have issues with that, I canhelp you to creatde such a query

[michaelgeorge]

We have returned to testing on this issue. In our test-instance the attachments are now going into the g_absolute_path_default_upload_folder directory, not into subdirectories by Project.

cas, I believe you are saying that in order to map uploads to tickets, we would run a (read-only) query against the database in order to gather that information. Is that correct?

We did figure that with a bit of investigation we could do it that way. I am hoping for something more straightforward. Apparently, though, the location and naming of the attachment files does not separate by Project or ticket number.

[atrol]

cas, I believe you are saying that in order to map uploads to tickets, we would run a (read-only) query against the database in order to gather that information. Is that correct?

Sad news concerning Cas, see viewtopic.php?t=33894