Mantis Bug Tracker - Forums

I want to insert data into user table, v1.1.7, how to deal with token field , please ?
What is this cookie_string (e.g.86bfcc681dc24bc4969babbd00df1d07a11149a90fcba520a42de0ecd534a1b0) actually doing once the user (not brand new) inserted into database ?

we have faced some issues during data ...

I did try on different version, see tags in one field, separated by ','

Thank you very much!
It's not easy to setup a testing environment to 'mirror' what we have for 1.1.7 actually.

Is there a quick way to add tags into csv_export ?
We have specific tag to identify issues.
Version 1.1.7
Because we don't have testing environment, the change on configuration has to be precisely listed as steps, then I follow these steps to make the change.

correction: as screenshot, that's our platform (v1.3) for mantis, still working okay after switching back to previous database, but not the one from v1.1.7.

we delete all from token table, but still same error.
is it okay we just use the database from old site for a new site? or we must import table by table , even so, different version of mantis, the schema different.

Hi,
Good news: data from 1.1.7 imported into 2.8.0 without problem. site can be launched, but
Bad news: although we have 2.8.0 site, login error still.

forum link schema[185] where should I go , please ?

running v1.1.7, view issues, there is a release dropdown list, which field we should go check in DB , please ?

are those values really used by issues logged in mantis ? or just for dropdown list display ? kind of confused as there are others:
fix_in_version
version
etc

there must be a field for ...

I will see how it goes on my end to follow your steps. Thank you very much!

yes!
but
XML feature not in v1.1.7 unfortunately, we only see PRINT REPORTS, CSV EXPORT when viewing issues.
XML feature okay in 2.8.0 we can see like
Viewing Issues (0 - 0 / 0) [ Print Reports ] [ CSV Export ] [ Excel Export ] [ XML Export ]

the situation here :
sql file will be available, but not ...

what we have had is a sql file from 1.1.7 and a site running 2.8.0 , what we need :
step by step based on what we have to see whether we can see data from 1.1.7 in 2.8.0.

agree with you!

our mantis 1.1.7 for production use actually, I cannot touch, but the database dump sql can be imported into 2.8.0 structure, or cannot ?
As you said, some schema changed on database level, I don't think that would be a simple task just import sql (whole 1.1.7 data) into current ...

we consider 'upgrade', but run into some troubles as 1.1.7 very old, some platform not supported. we are seeking for a successful case from a mantis lower than 1.1.8 , upgraded to current version, perhaps, which is ideal for us.

YES, those tags (id list) not attached to any issue :
SELECT distinct id FROM MANTIS_TAG_TABLE A LEFT JOIN MANTIS_BUG_TAG_TABLE B ON A.ID=B.TAG_ID WHERE B.TAG_ID IS NULL

Thank you!