fix: Remove resolution field from staging/dev transitions to prevent … #28

kamio90 · 2025-11-19T20:04:48Z

…400 errors

Remove resolution field from 'Deployed to Staging' and 'Merged' status transitions
Resolution field can only be set on final states like 'Done', not intermediate states
This allows transitions to succeed and custom fields to be updated properly
Add utility scripts to verify and test custom field updates

Fixes issue where staging deployments failed with: 'Field resolution cannot be set. It is not on the appropriate screen'

Custom fields (Stage Release Timestamp, Production Release Timestamp, Release Environment) will now be updated correctly after successful transitions.

Note

Removes the resolution field from staging/dev transitions to prevent 400 errors and adds scripts to list, test, and verify Jira custom field updates.

Update Jira workflow (update_jira/index.js):
- Remove resolution from transitionFields for staging and dev (non-final states) while keeping production transitions unchanged.
Utilities:
- Add tmp/list-custom-fields.js to enumerate Jira custom fields and validate expected IDs.
- Add tmp/test-custom-fields.js to update/verify deployment-related custom fields on an issue, with optional rollback.
- Add tmp/verify-staging-flow.js to simulate and verify the staging deployment flow and custom field updates.

^{Written by Cursor Bugbot for commit 18a9e1d. This will update automatically on new commits. Configure here.}

…400 errors - Remove resolution field from 'Deployed to Staging' and 'Merged' status transitions - Resolution field can only be set on final states like 'Done', not intermediate states - This allows transitions to succeed and custom fields to be updated properly - Add utility scripts to verify and test custom field updates Fixes issue where staging deployments failed with: 'Field resolution cannot be set. It is not on the appropriate screen' Custom fields (Stage Release Timestamp, Production Release Timestamp, Release Environment) will now be updated correctly after successful transitions.

cursor

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on November 24

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

cursor · 2025-11-19T20:06:43Z

update_jira/index.js

    status: 'Merged',
    transitionFields: {
-      resolution: 'Done',
+      // No resolution field - "Merged" is not a final state


Bug: Deployment timestamps created at module load time, not deployment time

The statusMap object defines custom field timestamps using new Date() at module initialization time. This means all deployments will share the same timestamp (from when the module was first loaded), rather than capturing the actual deployment time. Timestamps should be created dynamically when deployments occur, not when the module is parsed.

Copilot

Pull Request Overview

This PR fixes a critical issue where Jira status transitions to intermediate states ("Deployed to Staging" and "Merged") were failing with 400 errors due to inappropriately setting the resolution field, which can only be set on final states like "Done".

Removes resolution field from staging and dev transition configurations in the status map
Adds three utility scripts for testing and verifying custom field updates in Jira

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 17 comments.

File	Description
update_jira/index.js	Removes resolution field from staging and dev transitions, replacing with explanatory comments
tmp/verify-staging-flow.js	Adds verification script to simulate staging deployment flow and verify custom field updates
tmp/test-custom-fields.js	Adds interactive test script for verifying custom field updates with rollback capability
tmp/list-custom-fields.js	Adds utility script to list and verify all custom fields in the Jira instance

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2025-11-19T20:10:27Z

tmp/verify-staging-flow.js

+ * Usage: node utils/verify-staging-flow.js [ISSUE_KEY]
+ * Example: node utils/verify-staging-flow.js DEX-36


The example path references utils/verify-staging-flow.js, but this file is located in tmp/. The path should be node tmp/verify-staging-flow.js DEX-36.

Suggested change

* Usage: node utils/verify-staging-flow.js [ISSUE_KEY]

* Example: node utils/verify-staging-flow.js DEX-36

* Usage: node tmp/verify-staging-flow.js [ISSUE_KEY]

* Example: node tmp/verify-staging-flow.js DEX-36

Copilot · 2025-11-19T20:10:28Z

tmp/test-custom-fields.js

+    process.exit(1)
+  }
+
+  console.log(`\n${  '='.repeat(80)}`)


The template literal has an extra space before '='.repeat(80). This should be \n${'='.repeat(80)} for consistent formatting.

Suggested change

console.log(`\n${ '='.repeat(80)}`)

console.log(`\n${'='.repeat(80)}`)

Copilot · 2025-11-19T20:10:28Z

tmp/test-custom-fields.js

+ *   node utils/test-custom-fields.js [ISSUE_KEY]
+ *
+ * Example:
+ *   node utils/test-custom-fields.js DEX-36


The usage path references utils/test-custom-fields.js, but this file is located in tmp/. The path should be node tmp/test-custom-fields.js [ISSUE_KEY].

Suggested change

* node utils/test-custom-fields.js [ISSUE_KEY]

*

* Example:

* node utils/test-custom-fields.js DEX-36

* node tmp/test-custom-fields.js [ISSUE_KEY]

*

* Example:

* node tmp/test-custom-fields.js DEX-36

Copilot · 2025-11-19T20:10:28Z

tmp/list-custom-fields.js

+
+    if (releaseFields.length > 0) {
+      console.log('\n🎯 RELEASE/DEPLOYMENT RELATED FIELDS:')
+      console.log('=' .repeat(100))


There's an extra space in '=' .repeat(100). This should be '='.repeat(100) for consistent formatting.

Suggested change

console.log('=' .repeat(100))

console.log('='.repeat(100))

Copilot · 2025-11-19T20:10:29Z

tmp/verify-staging-flow.js

+ * Usage: node utils/verify-staging-flow.js [ISSUE_KEY]
+ * Example: node utils/verify-staging-flow.js DEX-36


The usage path references utils/verify-staging-flow.js, but this file is located in tmp/. The path should be node tmp/verify-staging-flow.js [ISSUE_KEY].

Suggested change

* Usage: node utils/verify-staging-flow.js [ISSUE_KEY]

* Example: node utils/verify-staging-flow.js DEX-36

* Usage: node tmp/verify-staging-flow.js [ISSUE_KEY]

* Example: node tmp/verify-staging-flow.js DEX-36

Copilot · 2025-11-19T20:10:31Z

tmp/verify-staging-flow.js

+    console.log('  5. Release Environment will be set to "Staging" ✅')
+    console.log()
+    console.log('🎉 The pipeline WILL update custom fields correctly!')
+    console.log(`${'='.repeat(80)  }\n`)


The template literal has trailing spaces after '='.repeat(80). This should be ${'='.repeat(80)}\n for consistent formatting.

Suggested change

console.log(`${'='.repeat(80) }\n`)

console.log(`${'='.repeat(80)}\n`)

Copilot · 2025-11-19T20:10:31Z

tmp/test-custom-fields.js

+  console.log('='.repeat(80))
+  console.log(`Issue: ${issueKey}`)
+  console.log(`Jira URL: ${JIRA_BASE_URL}`)
+  console.log(`${'='.repeat(80)  }\n`)


The template literal has trailing spaces after '='.repeat(80). This should be ${'='.repeat(80)}\n for consistent formatting.

Suggested change

console.log(`${'='.repeat(80) }\n`)

console.log(`${'='.repeat(80)}\n`)

Copilot · 2025-11-19T20:10:32Z

tmp/test-custom-fields.js

+    // Step 6: Offer to rollback
+    console.log('='.repeat(80))
+    console.log('✅ ALL TESTS PASSED!')
+    console.log(`${'='.repeat(80)  }\n`)


The template literal has trailing spaces after '='.repeat(80). This should be ${'='.repeat(80)}\n for consistent formatting.

Suggested change

console.log(`${'='.repeat(80) }\n`)

console.log(`${'='.repeat(80)}\n`)

Copilot · 2025-11-19T20:10:32Z

tmp/test-custom-fields.js

+
+    console.log(`\n${  '='.repeat(80)}`)
+    console.log('🎉 Test completed successfully!')
+    console.log(`${'='.repeat(80)  }\n`)


The template literal has trailing spaces after '='.repeat(80). This should be ${'='.repeat(80)}\n for consistent formatting.

Suggested change

console.log(`${'='.repeat(80) }\n`)

console.log(`${'='.repeat(80)}\n`)

Copilot · 2025-11-19T20:10:32Z

tmp/test-custom-fields.js

+ *   node utils/test-custom-fields.js [ISSUE_KEY]
+ *
+ * Example:
+ *   node utils/test-custom-fields.js DEX-36


The example path references utils/test-custom-fields.js, but this file is located in tmp/. The path should be node tmp/test-custom-fields.js DEX-36.

Suggested change

* node utils/test-custom-fields.js [ISSUE_KEY]

*

* Example:

* node utils/test-custom-fields.js DEX-36

* node tmp/test-custom-fields.js [ISSUE_KEY]

*

* Example:

* node tmp/test-custom-fields.js DEX-36

kamio90 requested a review from Copilot November 19, 2025 20:04

Copilot started reviewing on behalf of kamio90 November 19, 2025 20:05 View session

cursor bot reviewed Nov 19, 2025

View reviewed changes

Copilot finished reviewing on behalf of kamio90 November 19, 2025 20:08

Copilot AI reviewed Nov 19, 2025

View reviewed changes

kamio90 merged commit 67e44df into main Nov 20, 2025
8 of 9 checks passed

kamio90 deleted the DEX-36/fix-jira-integration-part-2 branch November 20, 2025 08:13

		* Usage: node utils/verify-staging-flow.js [ISSUE_KEY]
		* Example: node utils/verify-staging-flow.js DEX-36

	console.log(`\n${ '='.repeat(80)}`)
	console.log(`\n${'='.repeat(80)}`)

	console.log(`${'='.repeat(80) }\n`)
	console.log(`${'='.repeat(80)}\n`)

fix: Remove resolution field from staging/dev transitions to prevent … #28

fix: Remove resolution field from staging/dev transitions to prevent … #28

Uh oh!

Conversation

kamio90 commented Nov 19, 2025 • edited by cursor bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cursor bot left a comment

Choose a reason for hiding this comment

This is the final PR Bugbot will review for you during this billing cycle

Uh oh!

cursor bot Nov 19, 2025

Choose a reason for hiding this comment

Bug: Deployment timestamps created at module load time, not deployment time

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull Request Overview

Reviewed Changes

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Copilot AI Nov 19, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

kamio90 commented Nov 19, 2025 •

edited by cursor bot

Loading