-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Integration][Jira] Adds teams kind #1227
Conversation
- Implement `get_paginated_users` method to fetch users from Jira API - Add `_get_paginated_users` helper method to retrieve user data
Co-authored-by: PagesCoffy <[email protected]>
- Extended `WEBHOOK_EVENTS` to include user lifecycle events - Updated `handle_webhook_request` to process user webhook events - Register user data when user-related events are received
…t-labs/ocean into PORT-11704-Jira-enhancements
…1704-Jira-enhancements
…1704-Jira-enhancements
- Generalized event processing using `startswith` for different event types. - Added error handling for unknown events and missing items. - Improved logging and ensured proper registration/unregistration of items.
…le different webhook event types (user, project, issue).
- Added `TEAM` to `ObjectKind` enum. - Introduced `on_resync_teams` for syncing teams - Enhanced `on_resync_users` to enrich users with associated team data
- Added `team` to the list of resource kinds in the spec. - Introduced `atlassianOrganisationId` as an optional configuration for teams support
- Added `_send_api_request` for centralized API request logic. - Implemented `_get_paginated_data` and `_get_cursor_paginated_data` for streamlined handling of paginated responses. - Replaced repetitive API calls with reusable helper methods. - Updated methods (`get_paginated_projects`, `get_paginated_issues`, etc.) to use new pagination utilities. - Improved logging for better traceability during data retrieval. - Simplified user and team data fetching with cursor-based pagination support.
- Introduced `jiraTeam` blueprint with properties: - `displayName`, `organizationId`, `teamType`, and `description`. - Added `members` relation linking `jiraTeam` to `jiraUser`. - Updated `jiraUser` blueprint: - Added `team` relation linking users to their teams.
- Introduced a new `team` resource to the configuration with a selector to map teams. - Updated `user` resource to include a `team` relation linking users to teams using `teamId`.
…1704-Jira-enhancements
…e effects. - Improved pagination logic by dynamically updating `start_at` based on fetched items.
…}` for clarity. - Ensured `params` defaults to `{}` when `None` is provided across methods.
…1704-Jira-enhancements
Co-authored-by: Tom Tankilevitch <[email protected]>
…t-labs/ocean into PORT-11704-Jira-enhancements
Co-authored-by: Tom Tankilevitch <[email protected]>
Co-authored-by: Tom Tankilevitch <[email protected]>
…1704-Jira-enhancements
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @shariff-6 !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
great job
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
What -
Added support for syncing Jira teams to Port.
Why -
Enhance the Jira integration by providing team-level information and context.
Enable users to track and manage Jira teams within their Port catalog.
How -
Added new methods in
jira/client.py
to fetch teams and team members.Updated
main.py
to include team synchronization logic.Modified configuration files to support team resource kind.
Implemented team enrichment for users through team mapping.
Type of change
Please leave one option from the following and delete the rest:
All tests should be run against the port production environment(using a testing org).
Core testing checklist
Integration testing checklist
examples
folder in the integration directory.Preflight checklist
Screenshots
Include screenshots from your environment showing how the resources of the integration will look.
API Documentation
Provide links to the API documentation used for this integration.