Tables in Jira
The jira plugin includes 18 tables:
Name | Description | Queries |
---|---|---|
The application properties that are accessible on the Advanced Settings page. | ||
The backlog contains incomplete issues that are not assigned to any future or active sprint. | ||
A board displays issues from one or more projects, giving you a flexible way of viewing, managing, and reporting on work in progress. | ||
This resource represents project components. Use it to get, create, update, and delete project components. Also get components for project and get a count of issues by component. | ||
Your dashboard is the main display you see when you log in to Jira. | ||
An epic is essentially a large user story that can be broken down into a number of smaller stories. An epic can span more than one project. | ||
Returns the global settings in Jira. | - | |
Group is a collection of users. Administrators create groups so that the administrator can assign permissions to a number of people at once. | ||
Issues help manage code, estimate workload, and keep track of team. | ||
Comments that provided in issue. | ||
Issue types distinguish different types of work in unique ways, and help you identify, categorize, and report on your teamβs work across your Jira site. | ||
Jira worklog is a feature within the Jira software that allows users to record the amount of time they have spent working on various tasks or issues. | ||
Details of the issue priority. | ||
Project is a collection of issues (stories, bugs, tasks, etc). | ||
Project Roles are a flexible way to associate users and/or groups with particular projects. | ||
Sprint is a short period in which the development team implements and delivers a discrete and potentially shippable application increment. | ||
User in the Jira cloud. | ||
A Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle, and typically represents a process within your organization. |