Skip to content

chore: add JIRA issue automation - [MCP-3] #376

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 2 commits into from
Jul 15, 2025
Merged

chore: add JIRA issue automation - [MCP-3] #376

merged 2 commits into from
Jul 15, 2025

Conversation

blva
Copy link
Collaborator

@blva blva commented Jul 15, 2025 •
edited
Loading

Proposed changes

  • Adds automation to create an MCP project JIRA ticket for triage

Checklist

@blva blva changed the title chore: add JIRA issue automation chore: add JIRA issue automation - [MCP-3] Jul 15, 2025
@blva blva marked this pull request as ready for review July 15, 2025 15:30
@Copilot Copilot AI review requested due to automatic review settings July 15, 2025 15:30
@blva blva requested a review from a team as a code owner July 15, 2025 15:30
Copilot
Copilot AI reviewed Jul 15, 2025
View reviewed changes
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Adds a GitHub Actions workflow to automatically create an MCP JIRA ticket and comment on newly opened GitHub issues.

  • Introduce .github/workflows/jira-issue.yml to trigger on issue opens
  • Use a permissions monitor and the create-jira action to create a Story in the MCP project
  • Post a comment back on the GitHub issue with the new JIRA ticket link
Comments suppressed due to low confidence (3)

.github/workflows/jira-issue.yml:25

  • [nitpick] The abbreviation n. in the summary may be unclear; consider using a more standard format like No. or # for the issue number.
          summary: "HELP: GitHub Issue n. ${{ github.event.issue.number }}"

.github/workflows/jira-issue.yml:13

  • [nitpick] Casing of 'Jira' is inconsistent with the workflow name (which uses 'JIRA'); consider using 'JIRA' for consistency.
    name: Create Jira issue

.github/workflows/jira-issue.yml:18

  • Ensure that PERMISSIONS_CONFIG is defined in repository variables under Settings > Variables, or document its expected structure so the permissions monitor step functions correctly.
          config: ${{ vars.PERMISSIONS_CONFIG }}

@coveralls
Copy link
Collaborator

coveralls commented Jul 15, 2025 •
edited
Loading

Pull Request Test Coverage Report for Build 16297548841

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.3%) to 77.581%
Totals Coverage Status
Change from base Build 16297368178: 0.3%
Covered Lines: 2836
Relevant Lines: 3611
💛 - Coveralls

@gagik
Copy link
Collaborator

gagik commented Jul 15, 2025

we would need someone to set the secret I'd think?

@fmenezes
Copy link
Collaborator

we would need someone to set the secret I'd think?

I can see JIRA_API_TOKEN added in the repo settings

@fmenezes fmenezes merged commit fd3f2a4 into main Jul 15, 2025
21 checks passed
@fmenezes fmenezes deleted the track-issues branch July 15, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

Copilot code review Copilot Copilot left review comments

@fmenezes fmenezes fmenezes approved these changes

@gagik gagik gagik approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@blva @coveralls @gagik @fmenezes