Skip to content

fix(code): Fix resolution field error on Jira status transitions#1258

Merged
JCMOSCON1976 merged 3 commits intomainfrom
ASP-JCM-1
Mar 16, 2026
Merged

fix(code): Fix resolution field error on Jira status transitions#1258
JCMOSCON1976 merged 3 commits intomainfrom
ASP-JCM-1

Conversation

@JCMOSCON1976
Copy link
Contributor

@JCMOSCON1976 JCMOSCON1976 commented Jan 23, 2026

Problem

  • When transitioning a Jira issue to "Cancelled" status, JBI hardcoded setting resolution: "Invalid". Some Jira projects (e.g., SYNC) don't have the resolution field configured on their transition screen, causing:
    HTTP 400: Field 'resolution' cannot be set. It is not on the appropriate screen, or unknown.

Solution

  • Use the Jira transitions API with expand=transitions.fields to check if the resolution field is available on the target transition screen before including it in the request. If unavailable, the transition proceeds without setting resolution (the comment is still added).

Jira ticket

@JCMOSCON1976 JCMOSCON1976 requested a review from a team as a code owner January 23, 2026 22:00
@JCMOSCON1976 JCMOSCON1976 requested review from alexcottner and leplatrem and removed request for a team January 23, 2026 22:01
@JCMOSCON1976 JCMOSCON1976 added the python Pull requests that update Python code label Jan 23, 2026
Copy link
Contributor

@alexcottner alexcottner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems reasonable

@JCMOSCON1976 JCMOSCON1976 merged commit 7b593d3 into main Mar 16, 2026
5 checks passed
@JCMOSCON1976 JCMOSCON1976 deleted the ASP-JCM-1 branch March 16, 2026 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

python Pull requests that update Python code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants