Documentation

Expandable History List:

• • Click the arrow (▶) to expand/collapse
• • Shows total count: "Previous Assignments (3)"

Each History Entry Displays:

• • Repository: Which GitHub repository was used
• • Date: When the GitHub issue was created
• • GitHub Issue Link: Direct link to the created GitHub issue
• • Linked Pull Requests: PRs created by Copilot with status indicators

PR Status Indicators:

• • open Blue tag: Open PR (in progress)
• • merged Green tag: Merged PR (completed)
• • closed Red tag: Closed PR (not merged)

Compact Display:

• • Shows up to 3 PRs per assignment
• • Additional PRs shown as "+2" if more exist
• • Click PR numbers to view them in GitHub

❌ "GitHub token not configured"

Solution:

1. 1. Go to Project Settings → Apps → GitHub Copilot Configuration
2. 2. Add your GitHub Personal Access Token
3. 3. Ensure it has the required permissions

❌ "No repositories configured"

Solution:

1. 1. Add at least one repository in format: owner/repo
2. 2. Save the configuration
3. 3. Try the assignment again

❌ "Please select a repository"

Solution:

1. 1. Choose a repository from the dropdown menu
2. 2. This appears when multiple repositories are configured for manual assignment

❌ "Failed to create GitHub issue"

Possible Causes:

• • Invalid repository name format
• • Repository doesn't exist or isn't accessible
• • GitHub token lacks necessary permissions
• • Network connectivity issues

Solution:

1. 1. Verify repository exists and you have access
2. 2. Check token permissions
3. 3. Try again after a few minutes

❌ "Failed to assign GitHub Issue to Copilot"

Possible Causes:

• • Copilot doesn't have access to the repository
• • Repository settings don't allow Copilot
• • Token lacks assignment permissions

Solution:

1. 1. Ensure Copilot is enabled for your repository
2. 2. Check your GitHub Copilot subscription status
3. 3. Verify token has workflow permissions

❌ "A rule for this status already exists"

• • You can only have one automation rule per status
• • Remove the existing rule first, then create a new one

❌ "Target status is required"

• • Select a status from the dropdown menu
• • If dropdown is empty, check your Jira project configuration

❌ "Repository is required"

• • Select a repository for the automation rule
• • Add repositories first before creating automation rules

❌ "Failed to load project statuses"

• • Check your Jira project permissions
• • Try refreshing the page
• • Contact your Jira administrator

Automation not triggering:

1. 1. Verify the automation rule is configured correctly
2. 2. Check that the issue actually changed to the target status
3. 3. Look for automation comments in the Jira issue
4. 4. Check if "skip duplicates" is preventing the trigger

Multiple GitHub issues created:

1. 1. This happens when "Allow duplicates" is enabled
2. 2. Consider enabling "Skip if already assigned" for most rules
3. 3. Review your automation rule configuration

Wrong repository used:

1. 1. Check which repository is specified in the automation rule
2. 2. Edit the rule by removing and recreating it

GitHub Issue Format

As a user, I want to be able to log in to the system so that I can access my personal dashboard.
## Acceptance Criteria
- Login form with username/password
- Remember me checkbox  
- Password reset functionality
- Redirect to dashboard after login
---
Use the key [PROJ-123] in the beginning of the PR title.
*Automatically created from Jira issue: PROJ-123*

Jira Integration

Be Specific:

Include Acceptance Criteria:

## Acceptance Criteria
- [ ] Endpoint accepts POST requests to /api/register
- [ ] Validates email format
- [ ] Returns appropriate error codes
- [ ] Saves user to database

Mention Technology Stack:

For Automation - Use Clear Status Names:

• • Use descriptive status names like "Ready for Development" instead of generic "Open"
• • Align status names with your team's actual workflow
• • Consider creating specific statuses for automation triggers