Note: *Check out these useful books! As an Amazon Associate I earn from qualifying purchases.
Answer: Jira is an issue-tracking and project management tool developed by Atlassian. It is widely used for bug/issue tracking, agile software development, task management and project tracking. :contentReference[oaicite:2]{index=2}
Answer:
Answer: In Jira an issue is the basic unit of work/tracking: it can represent a bug, task, story, epic etc. It has fields like summary, description, status, assignee, reporter. :contentReference[oaicite:4]{index=4}
Answer: A workflow is a set of statuses and transitions that an issue goes through from creation to completion/closure. It defines how the issue moves between states. :contentReference[oaicite:5]{index=5}
Answer: Issue types categorize issues. Common ones: Story, Task, Bug, Epic, Sub-task. Each issue type often has its own workflow, fields, screens. :contentReference[oaicite:6]{index=6}
Answer: Schemes in Jira are reusable configurations which define behaviour for projects/issues. Examples: permission schemes (who can do what), notification schemes (who gets what mails), issue type schemes, workflow schemes, field configuration schemes. :contentReference[oaicite:7]{index=7}
Answer: JQL is Jira’s query language used to search for issues based on fields, keywords, operators, functions. It allows advanced filtering beyond simple search. :contentReference[oaicite:8]{index=8}
Answer: Boards provide visualisation for Agile teams. A Scrum board focuses on sprints and iterations; a Kanban board focuses on a continuous flow of work with WIP limits. They are built on issues from one or more projects/filters. :contentReference[oaicite:9]{index=9}
Answer: A dashboard in Jira is a page of gadgets/widgets which show issue stats, charts, filters, etc. To create: go to Dashboards ? Create new ? add gadgets, select filters. It helps users monitor progress, team workload, KPIs. :contentReference[oaicite:10]{index=10}
Answer: Filters are saved searches (often built using JQL) that can be shared, used in boards, dashboards, gadgets, subscriptions. They allow frequent reuse of queries. :contentReference[oaicite:11]{index=11}
Answer: Permissions control what users/groups can do (e.g., create issues, edit, delete, transition). They are managed via Permission Schemes, which are associated with projects. One assigns roles/groups/users appropriate rights. :contentReference[oaicite:12]{index=12}
Answer: The Move Issue wizard allows you to move an issue from one project (or issue type) to another. During move you can change project, issue type, status, fields. Config differences may require mapping. :contentReference[oaicite:13]{index=13}
Answer: Cloning creates a duplicate of an existing issue. The clone usually carries fields like summary, description, attachments (depending on config). Some things like comments, work logs may not be cloned. :contentReference[oaicite:14]{index=14}
Answer: Jira provides reports such as: Time Tracking Report, Average Age Report, Created vs Resolved, Pie Chart, Workload Pie Chart, User Workload, Sprint Report (Scrum), Cumulative Flow Diagram (Kanban) etc. :contentReference[oaicite:15]{index=15}
Answer: Versions (also called Fix Versions) represent release points. You assign issues to a version, track the version’s progress, mark as released when done. Helps in planning and release reporting. :contentReference[oaicite:16]{index=16}
Answer: An Epic is a large body of work that can be broken into multiple Stories (or tasks). A Story represents a single user requirement/feature. Epics span multiple sprints, stories are granular. :contentReference[oaicite:17]{index=17}
Answer: Jira integrates via built-in links, marketplace apps, REST API, webhooks. For example: Confluence for docs, Bitbucket for code, CI/CD tools for build/deploy. Integration improves traceability, automation and collaboration. :contentReference[oaicite:18]{index=18}
Answer: Jira Automation (for Cloud/Data Center) allows rules: triggers (issue created, transitioned), conditions, actions (send email, transition, comment, assign). This helps reduce manual effort and enforce process. :contentReference[oaicite:19]{index=19}
Answer: Add-ons/Plugins extend Jira’s functionality via the Atlassian Marketplace. Popular ones: ScriptRunner, Zephyr for test management, Tempo Timesheets, Portfolio for Jira (now Advanced Roadmaps), Jira Misc Workflow Extensions. :contentReference[oaicite:20]{index=20}
Answer: Jira supports bulk edit/change: Filter ? Tools ? Bulk Change ? select issues ? choose operation (edit, move, delete, transition) ? optionally disable notifications. Useful when many issues need updates. :contentReference[oaicite:21]{index=21}
Answer: JSM is Atlassian’s ITSM (IT service management) product. It supports incident, problem, change, service request workflows, and is used by service desks/support teams rather than just dev teams. :contentReference[oaicite:22]{index=22}
Answer: Limitations include: complexity with many custom fields, performance impact with huge issue counts, licensing cost, migrating between projects/instances can be complex, careful planning required for workflows, permissions and data hygiene. Awareness of best practices is key. :contentReference[oaicite:23]{index=23}