What is the safest way to fix future commit date in git and what are the consequences?

The developer managed to fix some code with a future date - March 1, 2013, to be precise

git show --format=fuller <SHA>

AuthorDate: Fri Mar 1 17:28:26 2013 +0300
CommitDate: Fri Mar 1 17:29:38 2013 +0300

This (a) is misleading and (b) blocks Jira from searching for “new” commits that are marked with Jira's ticket numbers (since March 1, 2013 there have been no commits and will not be for 6 months so far)

I found usage examples git filter-branchfor adjusting the date, for example. http://git.661346.n2.nabble.com/date-change-of-commit-td3887606.html :

git filter-branch --env-filter ' 
  if [ $GIT_COMMIT = <sha1> ]; then 
    export GIT_AUTHOR_DATE="1112911993 -0700" 
    export GIT_COMMITTER_DATE="1112911993 -0700" 
  fi 
'

But they come with warnings about dire consequences. Answers to any one or more of the following questions would be appreciated.

• What is your experience using the above method to change the commit date?
• , ?
• ?
• ?