Business Requirement
Our release processes require Jira issues to be moved from "Resolved" to "Closed" status directly from XLR workflow automation. Currently, this is not possible because Jira requires a Resolution field during the transition to Closed status.
Current Limitation
XLR Jira plugin can transition issues to "Resolved".
Transition from "Resolved" to "Closed" is not supported when Jira workflows require Resolution input.
Resolution values cannot be configured or mapped in the Jira task.
Organizations must implement custom webhooks or custom development to achieve this functionality.
Requested Enhancement
Enhance Jira task/plugin to support:
Resolution field mapping.
Dynamic selection of Resolution values.
Jira workflow transition screens requiring mandatory fields.
Allow users to configure:
Resolution Reason
Additional mandatory Jira fields
Custom field mappings during transitions.
Support generic Jira workflow configurations without requiring custom JSON webhooks.
Business Benefit
Enables end-to-end Jira ticket lifecycle automation.
Eliminates dependency on custom webhook implementations.
Reduces operational effort and maintenance costs.
Improves integration between XLR and Jira across enterprise environments.
Expected Outcome
Users should be able to close Jira tickets directly from XLR while providing mandatory Resolution values and other required fields as part of the Jira task configuration.
These descriptions should be detailed enough for submission to the Digital.ai Ideas Portal while clearly explaining the business need, current gap, requested enhancement, and expected outcome.
by: nirupa B. | about a day ago | Integrations

Comments
Thank you for the suggestion. To better understand the use case, we have a few questions:
- Are you using Jira Cloud or Jira Data Center, and which version?
- Besides Resolution, which mandatory fields do your transition screens require today? Are any of them custom fields?
- Could you share the payload your current webhook sends to close an issue? This helps us see the exact fields and value formats you need.
- How many issues does a typical release close, and do you transition them one at a time or in bulk?