/
Usage Guide for Admin Checker

Usage Guide for Admin Checker

1. Basic Overview

Admin Checker helps you verify administrator permissions from the actual Reporter across different Jira projects directly from your issue panel.

2. Issue Panel Features

Viewing Admin Status

  • Look for the Admin Checker panel in the right sidebar of any issue

  • The panel displays:

    • Current project key being checked

    • List of user groups

    • Admin status indicators (✅/❌)

Reading the Results

  • ✅ Green checkmark: Group has admin permissions

  • ❌ Red cross: Group lacks admin permissions

  • Groups are listed in alphabetical order

  • Table shows up to 10 groups per page

3. Using Custom Fields

Default Behavior

  • By default, checks permissions for the current project

  • Updates automatically when switching issues

Custom Field Usage

  1. Enter a valid project key in your configured custom field

  2. Panel updates automatically to show permissions for that project

  3. Supported field types:

    • Text fields (direct input)

    • Select lists single choice (dropdown selection)

    • Radio buttons

Field Validation

  • Project keys must be valid

  • Invalid keys show error message

  • Empty fields value change to default configuration (current project)

4. Real-time Updates

Automatic Refresh

  • Permissions update every 3 seconds

  • Field value changes are detected automatically

  • Group changes reflect immediately

Status Changes

  • Permission changes are reflected in real-time

  • Table updates automatically

  • Error messages appear instantly

5. Troubleshooting

Common Issues

  1. No data showing:

    • Verify plugin is enabled

    • Check custom field configuration

    • Confirm project key is valid

  2. Incorrect permissions:

    • Verify user has access to target project

    • Check group membership

    • Allow cache to refresh (3 seconds)

  3. Field not updating:

    • Refresh the page

    • Check field configuration

    • Verify field permissions

Error Messages

  • "Project key does not exist": Enter a valid project key

  • "No access": User lacks view permissions

  • "Invalid field": Check custom field configuration

6. Best Practices

Recommended Usage

  • Use dedicated custom fields

  • Validate project keys before saving

  • Regular permission audits

  • Keep field values updated

Performance Tips

  • Clear unused field values

  • Use project key format

  • Limit frequent project switching

Related content