Fix jira config bug

Author: Half-Shot

spec/jira.spec.ts

@@ -106,7 +106,6 @@ describe('JIRA', () => {
     }, E2ESetupTestTimeout);
 
     afterAll(() => {
-        console.log('tear down');
         return testEnv?.tearDown();
     });
 
@@ -156,6 +155,5 @@ describe('JIRA', () => {
         // And await the notice.
         const { body } = (await webhookNotice).data.content;
         expect(body).toContain('Test User created a new JIRA issue [TP-8](https://example.org/browse/TP-8): "Test issue"');
-        console.log("Test over");
-    }, { timeout: 20000 });
+    });
 });

src/Connections/JiraProject.ts

@@ -529,7 +529,7 @@ export class JiraProjectConnection extends CommandConnection<JiraProjectConnecti
 
     public async provisionerUpdateConfig(userId: string, config: Record<string, unknown>) {
         // Apply previous state to the current config, as provisioners might not return "unknown" keys.
-        config = { ...config, ...this.state };
+        config = { ...this.state, ...config };
         const validatedConfig = validateJiraConnectionState(config);
         if (!validatedConfig.id) {
             await this.updateProjectId(validatedConfig, userId);