Skip to content

Conversation

@shahargl
Copy link
Member

close #5121

@vercel
Copy link

vercel bot commented Jun 30, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
keep ⬜️ Ignored (Inspect) Visit Preview Jun 30, 2025 1:18pm

@dosubot dosubot bot added size:L This PR changes 100-499 lines, ignoring generated files. Bug Something isn't working labels Jun 30, 2025
cursor[bot]

This comment was marked as outdated.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Bug: HTTPS Validation Conflict with Runtime Support

The host field in JiraonpremProviderAuthConfig was updated to HttpsUrl, enforcing HTTPS-only validation. However, the associated validation metadata still specifies "any_http_url", and the provider's runtime logic is designed to support both HTTP and HTTPS. This inconsistency causes valid HTTP Jira host configurations, which the provider is designed to handle, to be rejected during validation.

keep/providers/jiraonprem_provider/jiraonprem_provider.py#L23-L31

host: HttpsUrl = dataclasses.field(
metadata={
"required": True,
"description": "Jira Host",
"sensitive": False,
"hint": "jira.onprem.com",
"validation": "any_http_url",
}

Fix in Cursor


Was this report helpful? Give feedback by reacting with 👍 or 👎

@shahargl shahargl merged commit a33c4f8 into main Jun 30, 2025
18 checks passed
@shahargl shahargl deleted the bugfix/jiraupdate branch June 30, 2025 13:25
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Jun 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Bug Something isn't working lgtm This PR has been approved by a maintainer size:L This PR changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[🐛 Bug]: Updating custom fields using the Jira provider returns an error

2 participants