Impacted versions:
9.0 Community & 9.0 Enterprise

Steps to reproduce:
- Open up a V9 Enteprise Runbot
- Go to projects and open up the issues for the project 'Data Import/Export Plugin'
- Click on 'Create' to create a new issue. You will see the following form:
  ![image](https://cloud.githubusercontent.com/assets/6352350/13873556/8f826fbc-ecf2-11e5-95aa-e5cd7965b976.png)
  Notice how the Contact is filled in with the name 'Delta PC' and that no e-mail is filled in. When you open up this contact its form you will see he has an e-mail filled in:
  ![image](https://cloud.githubusercontent.com/assets/6352350/13873580/afd81f0a-ecf2-11e5-960f-91e14a999578.png)
- Remove the contact on the issue, click somewhere else and now fill in the contact again. The moment you add the contact again the onchange function goes off and the e-mail is filled in automatically:
  ![image](https://cloud.githubusercontent.com/assets/6352350/13873605/d0884068-ecf2-11e5-8892-5fcd0fc692b2.png)

Current behavior:
When clicking on 'Create' for creating a new issue on a project the customer its e-mail is not automatically filled in because the onchange does not seem to have an effect on the record.

Expected behavior:
When click on 'Create' for creating a new issue on a project the customer his e-mail is filled in automatically (provided there is one).

addons/project_issue/project_issue.py
" * Normal is the default situation\n"
                                              " * Blocked indicates something is preventing the progress of this issue\n"
                                              " * Ready for next stage indicates the issue is ready to be pulled to the next stage",
                                         required=False),
        'email_from': fields.char('Email', size=128, help="These people will receive email.", select=1),
        'email_cc': fields.char('Watchers Emails', size=256, help="These email addresses will be added to the CC field of all inbound and outbound emails for this record before being sent. Separate multiple email addresses with a comma"),
        'date_open': fields.datetime('Assigned', readonly=True, select=True),
        # Pr
        'date_closed': fields.datetime('Closed', readonly=True, select=True),
        'date': fields.datetime('Date'),
        'date_last_stage_update': fields.datetime('Last Stage Update', select=True),
        'channel': fields.char('Channel', help="Communication channel."),
        'categ_ids': fields.many2many('project.category', string='Tags'),
        'priority': fields.selection([('0','Low'), ('1','Normal'), ('2','High')], 'Priority', select=True),
        'version_id': fields.many2one('project.issue.version', 'Version'),
        'stage_id': fields.many2one ('project.task.type', 'Stage',
                        track_visibility='onchange', select=True,
                        domain="[('project_ids', '=', project_id)]", copy=False),
        'project_id': fields.many2one('project.project', 'Project', track_visibility='onchange', select=True),
        'duration': fields.float('Duration'),
        'task_id': fields.many2one('project.task', 'Task', domain="[('project_id','=',project_id)]"),
        'day_open': fields.function(_compute_day, string='Days to Assign',
                                    multi='compute_day', type="float",
                                    store={'project.issue': (lambda self, cr, uid, ids, c={}: ids, ['date_open'], 10)}),
        'day_close': fields.function(_compute_day, string='Days to Close',
                                     multi='compute_day', type="float",
                                     store={'project.issue': (lambda self, cr, uid, ids, c={}: ids, ['date_closed'], 10)}),
        'user_id': fields.many2one('res.users', 'Assigned to', required=False, select=1, track_visibility='onchange'),
        'working_hours_open': fields.function(_compute_day, string='Working Hours to assign the Issue',
                                              multi='compute_day', type="float",