Jira
Overview
Visualize and analyze Jira resources, including projects, issues, and workflows. Gain actionable insights into project status, issue trends, and team productivity. Monitor governance, track progress toward organizational objectives, and ensure project alignment with business goals. Facilitate better decision-making through real-time data and reporting capabilities.
Configurations
| Configuration | Description |
|---|---|
| Blueprint Account Name | A human-readable name for your account that will be used to identify this account across the application. |
| Jira URL | The base URL of your Jira instance (e.g., https://yourcompany.atlassian.net/). |
| User Name | Your Jira username associated with your Jira account. |
| Access Token | A Jira API access token. You can generate this in your Jira account under the API token section. |
| Jira Account ID | The unique ID associated with your Jira account. This can be found in your Jira account settings.(i.e. 601cc79df564b600716b81db) |
| Data Crawl Frequency | The frequency at which Kscope will crawl your Jira account for updates and changes. |
Permissions
The Jira blueprint requires an API Token which you can create by clicking here. Please ensure that you use the "Create API token" option to create a simple token (not the scoped one) and give the API token a descriptive label.
When creating the API token, note that simple API tokens inherit your user permissions. Ensure your account has atleast one of the following permissions in the projects you want to monitor:
Required Permissions:
Data Crawl
BROWSE_PROJECTSADMINISTER
Remediation
CREATE_ISSUES
Permission Details:
| Permission | Why it's needed |
|---|---|
BROWSE_PROJECTS | Access and read project information, issues, workflows, and basic project data |
ADMINISTER | Full access to project configuration, advanced settings, and administrative functions |
CREATE_ISSUES | Create Jira issues for remediation tickets generated from security findings |
Important Notes:
- API tokens inherit the permissions of the user who created them
- The token works with Basic Authentication using your email address and the token
- Ensure your user account has appropriate permissions in all projects you want Kscope to access
For more details on the Jira permissions, you can refer to the following documentation: Jira Permissions Overview
Remediation
The Jira blueprint supports automated remediation — Kscope can create Jira issues directly from security findings.
When an insight is detected, click Create Ticket to generate a Jira issue with pre-populated details. The following fields are configurable:
| Field | Description |
|---|---|
| Project Key | The Jira project where the issue will be created |
| Issue Type | Type of issue to create (e.g., Task, Bug, Story). Default: Task |
| Priority | Issue priority: Highest, High, Medium, Low, or Lowest |
| Assignee | Account ID of the user to assign the issue to |
| Labels | Labels to apply to the issue |
| Due Date | Due date in YYYY-MM-DD format |
| Components | Issue components to apply |
| Custom Fields | Additional custom fields as a JSON string |
Remediation requires the CREATE_ISSUES permission listed in the Permissions section.
Enrichment Lookups
The Jira blueprint supports on-demand enrichment lookups — AI agents and downstream automations can query live project and issue state without waiting for the next crawl.
| Lookup Type | Description | Parameters |
|---|---|---|
project.get | Retrieve metadata for a Jira project by key | projectKey (required) |
project.list | List all Jira projects visible to the configured user | (none) |
issue.status | Retrieve the current status, resolution, and last-updated timestamp for a Jira issue | issueKey (required) |
issue.get | Retrieve full issue details (summary, description, priority, assignee, reporter, timestamps) | issueKey (required) |
Lookups reuse the same jiraURL, userName, and accessToken credentials configured for the crawl, and inherit the same BROWSE_PROJECTS permission requirement.
Schema Model
| Resources | Source Entity | Normalized Entity | Description |
|---|---|---|---|
| Jira Project | jira.Project | Project | A project in Jira. |
| Jira Account | jira.JiraAccount | Account | An account in Jira. |
| Jira Issue Link | jira.IssueLink | IssueLink | A link between issues in Jira. |
| Jira Watches | jira.Watches | Watches | A watch record for Jira issues. |
| Jira Board | jira.Board | Board | A board in Jira for managing tasks. |
| Jira Progress | jira.Progress | Progress | Progress tracking data in Jira. |
| Jira Issue | jira.Issue | Issue | An issue or ticket in Jira. |
| Jira Issue Fields | jira.IssueFields | IssueFields | Detailed fields of a Jira issue. |
| Jira User | jira.User | User | A user in the Jira platform. |
| Jira Permission | jira.Permission | Permission | Permissions assigned in Jira. |
| Jira Holder | jira.Holder | Holder | Entity that holds a specific role/permission. |
| Jira Role | jira.Role | Role | A role defined in Jira. |
| Jira Issue Type | jira.IssueType | IssueType | The type/category of an issue in Jira. |
| Jira Priority | jira.Priority | Priority | Priority level of a Jira issue. |
| Jira Subtasks | jira.Subtasks | Subtask | Subtasks associated with a Jira issue. |
| Jira Permission Scheme | jira.PermissionScheme | PermissionScheme | A scheme for managing Jira permissions. |
| Jira Avatar URLs | jira.AvatarUrls | AvatarUrls | URL links to avatars in Jira. |
| Jira Actor | jira.Actor | Actor | An actor (user or group) in Jira. |
| Jira Status Category | jira.StatusCategory | StatusCategory | A category representing issue statuses. |
| Jira Status | jira.Status | Status | The current status of a Jira issue. |
| Jira Resolution | jira.Resolution | Resolution | The resolution of a Jira issue. |
| Jira Issue Link Type | jira.IssueLinkType | IssueLinkType | Types of links between Jira issues. |
| Jira Actor User | jira.ActorUser | User | A specific user acting on an issue. |
| Jira ServiceDesk Created | jira.servicedesk.Created | Created | Record of ServiceDesk creation in Jira. |
| Jira ServiceDesk Customer | jira.servicedesk.Customer | Customer | A customer using Jira ServiceDesk. |
| Jira ServiceDesk | jira.servicedesk.JiraServiceDesk | ServiceDesk | A Jira ServiceDesk project. |
| Jira ServiceDesk Project | jira.servicedesk.ServiceDesk | ServiceDeskProject | A project under Jira ServiceDesk. |
| Jira ServiceDesk Org | jira.servicedesk.Organization | Organization | An organization in Jira ServiceDesk. |
| Jira ServiceDesk Queue | jira.servicedesk.Queue | Queue | A queue in Jira ServiceDesk. |
| Jira ServiceDesk Issue | jira.servicedesk.Issue | Issue | An issue under Jira ServiceDesk. |
| Jira ServiceDesk SLAs | jira.servicedesk.SLAs | SLA | Service Level Agreements in Jira. |