Fix #144: Proper changeset processing order
When commiting changesets that resolve an issue, the changeset data
should be saved to the database before beginning to modify the issue
data.  This is to fix a problem of generating an email with a change
history that did not show the attached changesets, which could be
confusing in certain cases.
1 parent 0320678 commit 49276d8b46754309129a7afee669494fa0d83a6d
@John Reese John Reese authored on 22 Apr 2010
Showing 1 changed file
View
Source/Source.API.php