OSOE-722: Migrate away from deprecated gajira* actions to using the Jira API directly

[Piedone]

OSOE-722
Fixes #275

[coderabbitai]

Walkthrough

Walkthrough

The changes involve migrating away from deprecated gajira* actions to direct interactions with the Jira RESTful API using PowerShell scripts. This includes automating the transition and creation of Jira issues from GitHub actions, updating issue details, and eliminating the need for login steps by handling authentication within the scripts. The modifications ensure a seamless integration with Jira for issue management directly from GitHub repositories.

Changes

File Path	Change Summary
.github/actions/auto-resolve-done-jira-issue/Update-JiraIssue.ps1, auto-transition-jira-issue/Set-JiraIssueStatus.ps1	Scripts for fetching PR details, determining Jira issue keys, and transitioning Jira issues.
.github/actions/auto-resolve-done-jira-issue/action.yml, .github/actions/create-jira-issues-for-community-activities/action.yml, .github/actions/auto-transition-jira-issue/action.yml	Updated action steps to use new scripts with parameters. Removed "Login to Jira" steps. Added "Transition Jira Issue" and "Create Jira Issue" functionalities.
.github/actions/create-jira-issues-for-community-activities/Add-JiraIssue.ps1, create-jira-issues-for-community-activities/Initialize-IssueDetails.ps1	Automates creation and linking of Jira issues with updated variable names for consistency.
Scripts/Invoke-JiraApiGet.ps1, Scripts/Invoke-JiraApiPost.ps1, Scripts/Invoke-JiraApiRequest.ps1	New scripts introduced for making GET, POST, and general API requests to Jira.
.github/workflows/spelling-this-repo.yml, .github/workflows/post-pull-request-checks-automation.yml	Updated workflow configurations, including spelling checks and JIRA-related environment variables.
Docs/Actions.md, Docs/Workflows/Productivity/CreateJiraIssuesForCommunityActivities.md	Documentation updates reflecting the new action functionalities and workflow setups for Jira integration.

Assessment against linked issues

Objective	Addressed	Explanation
Migrate away from deprecated gajira* actions (OSOE-722)	✅
Use API Key Manager for Jira for restricted API access (#277)	❓	The changes do not explicitly mention the API Key Manager but address the need for secure API access.
Eliminate "Login to Jira" steps (#277)	✅
Document setup in MD files (#277)	❓	Documentation updates are mentioned, but the specifics of API Key Manager setup are not detailed.

Related issues

• Migrate auto-resolve-done-jira-issue and create-jira-issues-for-community-activities to use API Key Manager for Jira (OSOE-726) #277: The objectives regarding migration to API Key Manager for Jira, eliminating login steps, and documentation improvements appear to be partially addressed. The explicit use of API Key Manager is not detailed, but the overall direction of migrating away from deprecated actions and improving security and documentation aligns with the changes made.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.