Usage

Usage

๐Ÿ”ง Setup & Configuration

1. First-Time Setup

  1. Navigate to Jira App Settings โ†’ Find "Git Info Configuration" in admin panel

    image-20251228-121702.png

    Then Go to โ€œGit for Jiraโ€œ

  2. Click "Add New Configuration"

    image-20251228-183614.png
  3. Choose your Git provider:

    • ๐Ÿ™ GitHub: Personal Access Token.

    • ๐ŸฆŠ GitLab: Access Token.

    • ๐Ÿ”ท Azure DevOps: PAT

      Note the app also support create pull request and merge pull request feature, so both READ and WRITE permission is required.

2. Configure Connection

Enter the configuration name(customized), token and repos you prefer to search.

3. Repository Management

  • Auto-fetch: Use "Fetch My Repositories" button

  • Manual add: Enter owner/repo (GitHub) or project/repo (Azure DevOps)
    Note that Manual add is recommended, because it will have small set of scope to search and index which have better performance, however, if you donโ€™t want to maintain frequently as your repo count increases fast, please use Auto.

  • Multiple configs: Create separate configs for different environments

๐ŸŽฏ Using the App in Jira Issues

Now you are able to check the Git information in any Jira issue. You will find the Git information panel displayed like this:

image-20251228-140207.png

ย 

If you donโ€™t see this panel, you can enable it via:

image-20251228-140306.png

๐Ÿ“ Commits Tab

Shows all commits mentioning this Jira issue

image-20251228-183734.png

๐Ÿ“ฆ What you'll see:
โ€ข Commit messages containing your issue key (e.g., PROJ-123)
โ€ข Author, date, and repository info
โ€ข Direct links to commits on Git platform
โ€ข Quick SHA copy button

๐ŸŽฏ Use case: Track all code changes for a specific issue

ย 

โš™๏ธ Pipelines Tab


Pipeline-20251228-183929.png

Displays CI/CD pipeline runs

๐Ÿ”ง What you'll see:
โ€ข Pipeline/build status (โœ… Success, โŒ Failed, โณ Running)
โ€ข Trigger information and duration
โ€ข Branch and commit details
โ€ข Direct links to pipeline runs

๐ŸŽฏ Use case: Monitor build status for issue-related changes

๐Ÿš€ Deployments Tab

Shows deployment history

๐ŸŒ What you'll see:
โ€ข Deployment environments (Production, Staging, etc.)
โ€ข Deployment status and timestamps
โ€ข Related commits and branches
โ€ข Deployment URLs

๐ŸŽฏ Use case: Track where and when changes were deployed

๐ŸŒฟ Branches Tab

Lists branches related to the issue

Branch-20251228-184004.png

๐ŸŒฑ What you'll see:
โ€ข Branch names containing issue key
โ€ข Last commit date and author
โ€ข Branch protection status
โ€ข Quick navigation to branches

๐ŸŽฏ Use case: Find all active development branches

๐Ÿ”€ Pull Requests Tab

pullreust-20251228-184037.png

ย 

Displays linked PRs/Merge Requests

๐Ÿ”„ What you'll see:

  • PR titles and descriptions

  • Status (Open, Merged, Closed)

  • Source โ†’ Target branch flow

  • Direct PR links

  • Merge/Close actions (if supported)

๐ŸŽฏ Use case: Review and manage pull requests

ย 

๐Ÿ“„ File Changes Tab

Detailed file diff view

image-20251228-184223.png

๐Ÿ“Š What you'll see:
โ€ข Files changed in each commit
โ€ข Line-by-line diff with +/-
โ€ข Change statistics (additions/deletions)
โ€ข File status (added, modified, deleted)

๐ŸŽฏ Use case: Review exact code changes

โšก Actions Tab

Perform Git operations directly from Jira!


image-20251228-184355.png

๐ŸŒฟ Create Branch

1. Select repository 2. Choose "Create Branch" action 3. Enter: Branch name (suggested: feature/PROJ-123) 4. Select: Source branch (usually main/master) 5. Click: Execute โ†’ Branch created! โœ…

๐Ÿ”€ Create Pull Request

1. Select repository 2. Choose "Create PR" action 3. Fill: Title, source branch, target branch 4. Add: Description (auto-filled with issue reference) 5. Click: Execute โ†’ PR created! โœ…

โœ… Merge Pull Request

1. Select repository with open PRs 2. Choose "Merge PR" action 3. Select: PR to merge from dropdown 4. Confirm: Merge action 5. Click: Execute โ†’ PR merged! โœ…

๐ŸŽฎ Quick Actions Guide

For Developers:

1. ๐Ÿ“Œ See issue PROJ-123 in Jira 2. ๐ŸŒฟ Go to Branches tab โ†’ Create "feature/PROJ-123" 3. ๐Ÿ’ป Code and commit (mention PROJ-123 in commit message) 4. ๐Ÿ”€ Go to PR tab โ†’ Create pull request 5. โš™๏ธ Monitor pipeline in Pipelines tab 6. ๐Ÿš€ Track deployment in Deployments tab

For Managers/Testers:

1. ๐Ÿ“Š Check Commits tab for all changes 2. ๐Ÿ‘€ Review File Changes tab for code review 3. โœ… Check Pipelines tab for build status 4. ๐ŸŒ Verify Deployments tab for release status 5. ๐Ÿ” Use PR tab to review pending changes

๐Ÿ”„ Refresh & Cache

  • Auto-cache: Data cached for 1 week for performance

  • Manual refresh: Click "Refresh" button in any tab

  • Force refresh: Hold Shift + Click Refresh (bypasses cache)

๐ŸŽจ Visual Indicators

Status Badges:

  • โœ… Success (Green): Completed successfully

  • โณ Running/In Progress (Blue): Currently executing

  • โŒ Failed (Red): Operation failed

  • โš ๏ธ Pending/Queued (Yellow): Waiting to run

  • ๐Ÿ”„ Unknown (Gray): Status unclear

Provider Icons:

  • ๐Ÿ™ GitHub

  • ๐ŸฆŠ GitLab

  • ๐Ÿ”ท Azure DevOps

๐ŸŽฏ Remember: The app works by searching for your Jira issue key (like PROJ-123) in Git content. Always include the issue key in branch names, commit messages, and PR titles for best results!

Happy coding! ๐Ÿš€๐Ÿ‘จโ€๐Ÿ’ป๐Ÿ‘ฉโ€๐Ÿ’ป