Unfortunately, not as each issue is updated and therefore revised....

The problem is that after batch update is changed default order of issues in the list. It confuse users.

Hi there, I'm asking again: Is there any way to batch update issues without affecting the revised field?

My task is to assign versions to thousands of issues (we didn't use versions and we want to use them for existing issues). I need to only change the version field. No others. Any chance?

Unfortunately, no. Batch update will always update the revised field.
The only way to do this is directly from SQL.

OK. Thanks for the info. Could you please provide some info about Gemini database stucture. What tables and what fields to edit? I just need to set versions to issues. Thank you.

You need to update the field fixedinversionid in the geminiissues table (filter on issueid).
Update it to a value from the geminiversions (versionid).

Thank you. Last question: How to change affected versions?

insert issueid and versionid to the gemini_affectedversions table.

[quote user="MarkWing"]Unfortunately, no. Batch update will always update the revised field.
The only way to do this is directly from SQL.
[/quote]
And what about from Web Service? Also touch the revised field?

Yes.

OK. Thanks.