feat: add jira issue management components#4784
Merged
Merged
Conversation
- Introduced new components: On Issue trigger, Delete Issue, Get Issue, and Update Issue. - Enhanced documentation for Jira integration, detailing use cases, configuration, and example data for each component. - Implemented OAuth authentication for Jira API interactions, replacing previous email and API token method. - Added tests for new components to ensure functionality and error handling. This update significantly expands the capabilities of the Jira integration, allowing for comprehensive issue management within workflows. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
|
👋 Commands for maintainers:
|
superplane-policy-bot
Bot
requested review from
forestileao,
lucaspin and
shiroyasha
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
…ndling - Updated the Jira documentation to simplify the content and improve clarity, removing unnecessary sections and consolidating instructions. - Enhanced the metadata handling in the create, update, and delete issue mappers by introducing utility functions for project and issue key metadata. - Improved the configuration details for creating issues, including optional status management. This refactor aims to provide a clearer user experience and better maintainability of the codebase. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Integrated new utility functions `addIssueKeyMetadata` and `addProjectMetadata` to streamline the addition of project and issue key metadata in the Jira issue mapper. - Removed redundant code for metadata handling, improving code clarity and maintainability. This update aims to simplify the metadata management process within the Jira integration. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Introduced an optional `assignee` field in the `CreateIssueSpec` and `CreateIssueFields` structures to allow assignment of issues to specific users. - Updated the `requireProject` function to accept an HTTP context for improved project retrieval. - Enhanced the issue creation and update processes to handle the new assignee field, including corresponding tests to validate functionality. - Adjusted configuration and documentation to reflect the addition of the assignee field. This update aims to improve user experience by enabling direct assignment of issues during creation and updates. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Introduced a new `getIssueUrl` utility function to generate the issue URL based on the issue key and self link. - Updated the `createIssueMapper`, `getIssueMapper`, and `updateIssueMapper` to include the new "Issue URL" field in their execution details. - Enhanced corresponding test cases to validate the inclusion of the issue URL in the output details. This update improves the visibility of issue links directly within the application, enhancing user navigation and experience. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Introduced an optional `expand` field in the `GetIssueSpec` structure to allow users to specify additional fields to retrieve from Jira. - Updated the documentation for the Get Issue component to include the new expand field and its usage. - Enhanced the execution logic to utilize the expand parameter when fetching issue details. This update improves the flexibility of the Get Issue component by enabling users to retrieve more detailed information as needed. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Simplified the documentation for the Issue Key across multiple components (Create, Get, Update, Delete) by removing references to expressions resolving to the key. - Changed the type of the Issue Key field in the Delete Issue component from `FieldTypeExpression` to `FieldTypeString` for clarity. - Enhanced the execution logic in the Create Issue component to improve readability. This update aims to provide clearer documentation and improve the handling of issue keys within the Jira integration. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Added a new test case to verify behavior when the HTTP context is missing in the ListResources function for priorities, ensuring it returns an empty resource list without errors. - Updated the listPriorities function to return an empty list when the HTTP context is nil, improving robustness against missing context. This enhancement ensures that the integration gracefully handles scenarios where the HTTP context is not provided, improving overall stability. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
… functions - Added checks for nil HTTP context in the listIssueTypes, listIssueStatuses, and listAssignees functions to ensure they return an empty resource list without errors when the context is missing. - This enhancement improves the robustness of the Jira integration by gracefully handling scenarios where the HTTP context is not provided. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
- Updated the example output JSON for creating a Jira issue to include detailed fields such as summary, status, priority, issue type, project information, assignee, reporter, labels, and timestamps. - This enhancement provides a more comprehensive representation of the expected output, improving clarity for users implementing the Jira integration. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 24bad51. Configure here.
…ields - Enhanced the example output JSON for Jira issue creation to include detailed fields such as assignee, created date, issue type, labels, priority, project information, reporter, status, summary, and updated date. - This update provides a more comprehensive representation of the expected output, improving clarity for users implementing the Jira integration. Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
forestileao
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes: #4755
What changed
This extends the Jira integration by adding the following issue management components:
jira.updateIssuejira.deleteIssuejira.getIssueWhy
SuperPlane should support issue management in full. We already have issue creation but we do not support the full management cycle.
Notes