List boards

Jira list boards action to retrieve a list of available Jira boards. This is a read-only action that returns structured board data with support for filtering by project, board type, and other criteria.

Prerequisites

• Your admin must complete the initial Jira setup and enable Jira actions in the Admin Console so that the Jira action pack is available in Agent Builder.
• Each user is prompted to connect their Jira account via OAuth in Glean before running agents that use Jira actions, including Jira Assign issue.
• If your Jira organization uses Central OAuth, a Jira administrator must authorize the app for the site before users can run Jira actions in Glean.

Supported parameters

Parameter	Type	Description
Project key or ID	String	Project identifier used to scope which boards to list.
Name	String	Filter boards by name.
Type	String	Filter by board type (e.g., scrum, kanban).
Include private boards	Boolean	Whether to include private Jira boards in the results.
Sort by	String	Sort key for the returned board list (e.g., name, id).
Start at	Integer	Zero-based index for pagination to fetch subsequent pages.
Results limit	Integer	Maximum number of boards to return per page.

Usage examples

• "Show me all scrum boards in the Mobile App project."

• "List all available Jira boards I have access to."

• "What kanban boards are in our Engineering project?"

Troubleshooting

• Possible cause: Jira's Central OAuth application has not been granted site-wide access by a Jira administrator.
• Fix: Ask your Jira administrator to complete the required app authorization flow in Jira, then retry the action.

• Possible cause: The filters are too restrictive, or the connected account does not have permission to view boards.
• Fix: Try removing filters like Project key or ID or Board type to see if more boards are returned. Verify the connected account has permission to view boards in Jira.

• Possible cause: The tools server backing this action is unreachable (404) or returning an internal error (500).
• Fix: Confirm that the action's server information is correct and reachable from Glean. For 500 errors, contact Glean support to investigate the underlying exception.

• Possible cause: The verify_code URI for tools OAuth has not been added to the allowed redirect URIs for the Jira OAuth app.
• Fix: An admin should add the tools OAuth verify_code endpoint for your Glean instance to the OAuth app's allowed redirect URIs and retry authentication.

FAQs

You can filter boards by type using the Board type parameter. Common board types include scrum and kanban boards.

To list boards for a specific project, use the Project key or ID parameter. If you leave this parameter empty, the action will return boards across all projects the user has access to.