Issue:
- Explanation: An item or task that needs to be tracked, managed, and resolved within a project. Issues can include tasks, bugs, stories, and more.
Project:
- Explanation: A collection of issues and settings in Jira, organized to facilitate collaboration on a set of related tasks or objectives.
Epic:
- Explanation: A large body of work that can be broken down into smaller tasks. Epics are often used to group related issues together.
Sprint:
- Explanation: A time-boxed iteration of work in an Agile project. Sprints usually last 1 to 4 weeks and involve completing a set of prioritized tasks.
Workflow:
- Explanation: A series of statuses and transitions that an issue moves through during its lifecycle, from creation to completion.
Status:
- Explanation: A state or condition that an issue can be in, representing its position in the workflow. Common statuses include “Open,” “In Progress,” and “Done.”
Resolution:
- Explanation: The final status of an issue, indicating its completion or resolution. Examples include “Fixed,” “Done,” or “Cannot Reproduce.”
Assignee:
- Explanation: The person or team responsible for working on an issue. Assignees are typically the individuals responsible for resolving or progressing the issue.
Reporter:
- Explanation: The person who reported the issue or created it in Jira. This is often the end-user or someone who identified a problem.
Component:
- Explanation: A module or section of a project that can be associated with issues. Components are used to categorize and organize work within a project.
Priority:
- Explanation: The level of importance assigned to an issue, indicating its relative urgency. Common priorities include “Critical,” “Major,” and “Minor.”
Watcher:
- Explanation: A user who is watching an issue and receives notifications about changes to that issue. Watchers are often interested stakeholders.
Field:
- Explanation: A data entry or display area in Jira that represents a specific piece of information. Examples include the summary, description, and comments fields.
Custom Field:
- Explanation: A field that users can define and configure based on their specific requirements. Custom fields allow for additional data capture beyond the default Jira fields.
Permission Scheme:
- Explanation: A set of permissions that determine what actions users or groups can perform within a project or on specific issues.
Dashboard:
- Explanation: A customizable page in Jira that displays a collection of gadgets (such as filters, charts, and statistics) to provide an overview of project status and progress.
Filter:
- Explanation: A saved Jira query that defines a set of criteria to find and display a specific list of issues. Filters are often used in dashboards and reports.
Gadget:
- Explanation: A small, customizable item that can be added to a Jira dashboard to display specific information, such as filter results, charts, or activity streams.
Agile Board:
- Explanation: A visual representation of work in an Agile project, usually using either Scrum or Kanban methodologies. Boards help teams manage and prioritize tasks.
Kanban:
- Explanation: An Agile project management methodology that emphasizes continuous delivery and flow of work, visualized on a Kanban board.
Scrum:
- Explanation: An Agile project management methodology that works in fixed-length iterations called sprints. Scrum emphasizes collaboration, accountability, and iterative progress.
Burndown Chart:
- Explanation: A graphical representation of work completed versus work remaining over time, commonly used in Agile projects to track progress.
Velocity:
- Explanation: A measure of the amount of work a team can complete in a single iteration or sprint. Velocity is often used in Agile planning and estimation.
Backlog:
- Explanation: A prioritized list of tasks or user stories that have yet to be worked on. Backlogs are often used in Agile methodologies to plan future work.
Release:
- Explanation: A version or iteration of a product that is made available to users. Releases often represent a set of completed features or bug fixes.
Component Lead:
- Explanation: A user assigned to oversee and manage a specific component within a project. Component leads are responsible for coordinating work related to their assigned module.
Issue Link:
- Explanation: A connection between two issues in Jira, representing a relationship or dependency. Issue links can be used to show parent-child relationships, dependencies, and more.
Resolution Date:
- Explanation: The date when an issue is marked as resolved. This date provides insight into when a particular issue was completed or addressed.
Jira Service Management:
- Explanation: A Jira product focused on providing service management and customer support capabilities. It includes features for handling incidents, service requests, and more.