Node Inputs
Required Fields
- Resource: Your Jira instance/site URL
- Project: The specific Jira project to read from
- Issue Information: The information to retrieve from each issue (eg. Assignee, Description, Issue Type, etc)
- Number of Issues: The maximum number of issues to retrieve (defaults to 10)
Note: Use the ‘Configure Inputs’ option to expose these fields as inputs to the node. Especially helpful for Loop Mode operations.
Advanced Filtering Options
The node offers three filtering methods - you can only use one at a time:1. Basic Filters
- Status: Filter by issue status (e.g., “To Do”, “In Progress”, “Done”)
- Priority: Filter by priority level (e.g., “High”, “Medium”, “Low”)
- Issue Type: Filter by the type of issue (eg. Subtask, Task)
- Labels: Filter by specific labels attached to issues
- Assignee: Filter by team member assignments
- Custom Fields: Filter by any custom fields configured in your Jira instance
2. JQL (Jira Query Language)
When enabled underShow More Options
, you can write custom JQL queries to filter issues with greater precision:
- Allows for complex conditions and combinations
- Follows Jira’s query syntax
- Overrides basic filters when enabled
3. Saved Filter
When enabled underShow More Options
, you can select filters already saved in your Jira instance:
- Uses existing filters you’ve created in Jira
- Simplifies complex filtering without writing JQL
- Easier to maintain as you can update the filter in Jira directly
Note: You can only use one filtering method at a time - either Basic Filters, JQL, or Saved Filter.
Issue Information Selection
Choose which information to retrieve for each issue:- Description
- Key
- Summary
- URL
- Assignee
- Status
- Priority
- Labels
- Issue Type
- etc.
Node Output
The node outputs lists (arrays) for each selected information field. For example:- If you select “Summary” and “Assignee”, you’ll receive:
summaries
: string[] - List of issue summariesassignees
: string[] - List of issue assignees
Number of Issues to Read
input is set to 1
.
Node Functionality
The Jira Issue Reader node serves as a bridge between your workflows and Jira, enabling automated issue retrieval and filtering.Key Features
Filtering Options
- Basic Fields: Priority, Status, Labels, Assignee, Issue Type
- Custom Fields: Organization-specific fields with AND/OR logic
- JQL: Advanced filtering with Jira Query Language
- Saved Filters: Reuse existing filters from your Jira instance
- Number of Issues: Control how many issues to retrieve
Custom Fields Combination
You can choose how to combine multiple custom field filters:- AND: Issues must match all selected custom fields
- OR: Issues must match at least one selected custom field
When To Use
The Jira Issue Reader node is particularly valuable in these scenarios:Project Management
- Monitor open issues across projects
- Track issue status changes
- Generate workload reports
- Identify bottlenecks
Automation Workflows
- Trigger actions based on issue status
- Create automated reports
- Send notifications for specific issue types
- Sync issues with other tools
Example Use Cases
- Daily Status Report
- Bug Tracking with JQL
- Sprint Planning with Saved Filter
- Cross-Project Executive Report
Important Considerations
- Authentication: Requires setup in the credentials page
- Permissions: Node can only access projects and issues the authenticated user has permission to view
- JQL Knowledge: For advanced filtering, basic familiarity with JQL syntax is helpful
- Saved Filters: Only filters visible to the authenticated user will be available
Practical Integration Examples
Here are simple yet powerful ways to use the Jira Issue Reader with AI nodes:1. Bug Report Analysis
-
Jira Issue Reader
- Filter by: JQL = “project = ‘Product’ AND issuetype = Bug AND status = Open”
- Get: Description, Priority, Components
-
Ask AI
- Prompt: “Analyze these bug reports and:
- Group similar issues
- Identify most affected components
- Suggest priority order for fixes”
- Prompt: “Analyze these bug reports and:
-
Slack Message Sender
- Daily digest to #engineering channel
2. Sprint Health Check
-
Jira Issue Reader
- Filter: Use Saved Filter “Current Sprint Issues”
- Get: Story Points, Status, Blocked status
-
Scorer
- Score sprint health (0-100) based on:
- Completion rate
- Blocked issues
- Remaining story points
- Score sprint health (0-100) based on:
-
Email Sender
- Weekly report to project managers
- Highlights risk areas when score < 70
3. Customer Issue Prioritization
-
Jira Issue Reader
- JQL: “project = ‘Support’ AND labels = ‘customer-reported’ AND created >= -14d”
- Get: Description, Impact, Customer name
-
Extract Data
- Extract from Description:
- Reported Problems
- Error Messages
- Business Impact
- Customer Urgency
- Extract from Description:
-
Ask AI
- Input: Extracted data + Impact + Customer name
- Analyze impact and urgency
- Suggest priority order
- Identify issues needing immediate attention
-
Slack Message Sender
- Alerts to #customer-success for high-priority items
4. Technical Debt Tracking
-
Jira Issue Reader
- JQL: “project in (Backend, Frontend, Infrastructure) AND labels = technical-debt”
- Get: Description, Components, Story Points
-
Categorizer
- Categories:
- Infrastructure
- Code Quality
- Security
- Performance
- Categorize based on issue description
- Categories:
-
Notion Page Writer
- Organized tech debt dashboard
- Group by category with effort estimates