-
Notifications
You must be signed in to change notification settings - Fork 81
chore: update JIRA automation #387
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
Conversation
Pull Request Test Coverage Report for Build 16449784595Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
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.
Pull Request Overview
Updates the GitHub Actions workflow to enhance JIRA automation by adding support for manual JIRA creation via labels and changing the issue type from Story to Bug.
- Adds trigger for labeled events to allow manual JIRA creation with 'create-jira' label
- Changes JIRA issue type from Story to Bug
- Implements automatic cleanup of the 'create-jira' label after processing
issuetype: Story | ||
description: "This ticket tracks the following GitHub issue: ${{ github.event.issue.html_url }}." | ||
components: MCP | ||
issuetype: Bug |
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.
The removal of the description and components fields may result in incomplete JIRA tickets. Consider adding these back to provide better context and organization in JIRA.
issuetype: Bug | |
issuetype: Bug | |
description: ${{ github.event.issue.body || 'No description provided.' }} | |
components: ${{ github.event.label.name || 'Default Component' }} |
Copilot uses AI. Check for mistakes.
components: MCP | ||
issuetype: Bug | ||
|
||
- name: Show result |
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.
The indentation is incorrect for this step. It should be aligned with other steps at the same level (6 spaces), not as a sub-item of the previous step (8 spaces).
Copilot uses AI. Check for mistakes.
@@ -3,32 +3,59 @@ name: Create JIRA ticket for new issues | |||
|
|||
on: | |||
issues: | |||
types: [opened] | |||
types: [opened, labeled] |
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.
Why are you adding the label feature? For old issues?
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.
yes, if we want to trigger jira creation we can
Co-authored-by: Filipe Constantinov Menezes <filipe.menezes@mongodb.com>
Co-authored-by: Filipe Constantinov Menezes <filipe.menezes@mongodb.com>
Co-authored-by: Filipe Constantinov Menezes <filipe.menezes@mongodb.com>
Proposed changes
Checklist