This is by design for performance reasons. You can simply update both parents (eg get and update) to set the revised date.

I am not sure this solves my problem.

The situation I need to handle is when a user moves sub-issues in Gemini. I need to know that the sub-issues have changed so I can reflect these changes in the tool I am integrating with.

Got you. Don't think there is an easy way to do this. I presume you store the Gemini issue ids so you could check if the parent is the same.

Yes. When I do a forced synchronize which checks every issue it works fine.

The problem is that the plugin is designed to update almost real-time - so we cannot afford to check every issue all the time. Hence we only check the updated issues - but we can check this every 30 seconds.

Our internal system has over 10,000 issues so it takes quite some time to process all the issues - and I imagine some of our customers have many more issues. So the force synchronize is a last resort if the 2 systems get out of sync.

I don't think this is the biggest deal in the world - because I imagine that users will not generally be moving sub-issues between parent issues very often.

Would you consider a solution to this problem in a future release?

Sure, feel free to add it to our list: http://gemini.countersoft.com/default.aspx?GEM
I presume the easiest solution for you is setting the revised date, correct?

Thanks I will add it today.

Yes, the easiest solution from my point of view is if the child issue revised date is updated when it is moved to a different parent issue.

But if it makes more sense for you guys then I can easily code around it if you want to update the parent issue revised date instead of the child.

We will probably update both parent and child revised.