--- title: "Jira Cloud Adoption Notes" description: "A record of practical experience in adopting Jira Cloud, covering GitHub integration, agile Sprint workflow design, task specifications, bug handling strategies, and examples of common JQL filters." canonical_url: "https://blog.markkulab.net/en/post/jira-cloud-implementation-notes" author: "Mark Ku" author_url: "https://blog.markkulab.net/en/author/mark-ku" site: "Mark Ku's Tech Notes" date_published: "2025-01-06 01:01:35 +0800" category: "Management" tags: ["jira", "agile", "scrum", "sprint", "github", "project management", "workflow"] language: "en" license: "CC BY 4.0" license_url: "https://creativecommons.org/licenses/by/4.0/" attribution: "when reusing or quoting, credit the author and link back to the original" --- # Jira Cloud Adoption Notes ## Background I found some Jira notes I wrote a year and a half ago and decided to organize them into a blog post. ### **What is Jira?** **Jira** is a professional project management tool that helps teams collaborate effectively and maintain clear, transparent project progress, whether for software development or daily task management. ### **Integrating with GitHub** After integrating Jira with GitHub, you can directly link relevant code within Jira, boosting work efficiency. Follow the official guide to set it up: [Integrate with Github](https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/) ### **Designing the Workflow** Because we've adopted agile development, we run two-week Sprints, planning the goals and deliverables for each iteration. We customize our workflow diagram based on the team's development process and update Jira statuses before our daily stand-up meetings. The Kanban board provides a clear overview of the project's current progress. ![Workflow Diagram](https://blog.markkulab.net/content/markku/posts/jira-cloud-implementation-notes/images/workflow.png) ![Kanban Board](https://blog.markkulab.net/content/markku/posts/jira-cloud-implementation-notes/images/board.png) ### **Jira Usage Guidelines** 1. **Basic Rules** - Task titles should follow the format: "Issue Key + Space + Message". For example: - Single task: `IUW-8 fix xxxx` - Multiple tasks: `IUW-8 IUW-9 fix xxx` - You can also use the issue key to create branches, and Jira will automatically link them to the code. 2. **Sub-task Principles** - If a task is too complex or requires collaboration from multiple people, it's recommended to break it down into sub-tasks (Child Issues). - If a task is handled by a single team member, using a *Check List* is a more intuitive way to track progress. - If a module is too large, a new issue should be created and linked to the main issue using *relates to*. 3. **Handling Pending Tasks** - When a task is blocked, be sure to mark it with a **Flag** and clearly state the reason for follow-up. 4. **Enhancement Tasks** - Before every optimization or new technology adoption, discuss it with the tech lead and PM to ensure the plan is clear before creating a task. - Document the solution in detail for future reference. ### **Handling Dependent Bugs Discovered During a Sprint** 1. **Fix Immediately** - When a bug affects the next stage of development, create a new issue card immediately, notify the PM for discussion, and bring it up in a meeting to prioritize it. 2. **Fix Opportunistically** - If the bug doesn't directly impact the current Sprint's timeline, you can fix it while you're at it. However, please create an issue and notify the PM. 3. **Postpone the Fix** - If the bug doesn't affect current requirements and can't be finished within this Sprint, create a new card and notify the PM, who will schedule it for later. ### **Common Jira Filter Examples (JQL)** #### **Personal Task-Related** - **Issues I created** ``` reporter = currentUser() AND resolution is EMPTY ``` - **Issues assigned to me** ``` assignee = currentUser() AND resolution is EMPTY ``` #### **Project Management-Related** - **Overdue tasks** ``` project = "US-Web" AND due < now() ``` - **Tasks completed in the last 30 days** ``` project = "US-Web" and resolved >= startOfDay(-30d) ``` - **Tasks with recent status changes** ``` status changed DURING (startOfWeek(-1), endOfWeek(-1)) ``` ### **Other Recommended Plugins and Tools** 1. **Microsoft Teams Notifications** - Install the Jira Cloud plugin to receive update notifications anytime via Teams: [Teams plugin](https://teams.microsoft.com/l/app/aa183fd9-7104-46c4-af9f-9ee9b81d717e?source=app-details-dialog) 2. **Checklist Plugin** - Jira doesn't have a built-in checklist. For advanced checklist functionality, you can use this free plugin (limit of 20 items per issue): [Checklist for Jira Free](https://marketplace.atlassian.com/apps/1223660/checklist-for-jira-free?tab=overview&hosting=cloud) ## Final Thoughts Adopting Jira not only boosts team efficiency but also organizes the project management process, ensuring every task is delivered on time and is clearly traceable. By using the strategies and tools mentioned above, adopting Jira can effectively enhance team collaboration and ensure a clear and efficient project workflow. --- ## About this article and its author Originally published on [Mark Ku's Tech Notes](https://blog.markkulab.net/en/post/jira-cloud-implementation-notes) License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) — when reusing or quoting, credit the author and link back to the original ### About the author **[Mark Ku](https://blog.markkulab.net/en/author/mark-ku)** — Software Solution Provider - 10+ years senior software engineer, now an AI Builder - Focused on large-platform architecture — North-American e-commerce, AI SaaS subscription billing - Combining AI Agents and automation to build evolvable product foundations ### Free tools built by the author All of these are free to use: - [Free PDF Sign Tool](https://blog.markkulab.net/en/tools/pdf-sign): Online PDF sign tool — draw, type, or upload a signature, then drag, resize, and download. Everything runs in your browser; nothing is uploaded. - [VS Code Refactory](https://blog.markkulab.net/en/tools/refactory): Refactory is a VS Code refactoring extension: 34 actions plus a 37-rule code-smell inspection layer with a Code Health dashboard, across 18 languages, backed by 534 tests. It learns your repo's conventions: where interfaces live, where DI is registered, whether 'use client' belongs. It ranks files by git churn × complexity so you know what to fix first, and hands any smell to the Claude Code already on your machine. Free to use, and your source never leaves your computer. - [DB-Kit Database Manager](https://blog.markkulab.net/en/tools/db-kit): DB-Kit is a lightweight, cross-platform database manager built with Tauri + Rust + React. Manage MySQL, MariaDB, PostgreSQL, SQL Server, Oracle, SQLite, MongoDB, Redis, Kafka, Elasticsearch and RabbitMQ from one consistent interface: passwords encrypted in the OS keychain, SSH tunnels, full CRUD, a visual query builder, stacked multi-statement result sets, cross-connection data transfer and compare/sync, Excel / CSV import & export, visualized execution plans, ER diagrams, scheduled backups, SQL stress testing with p50–p99 latency percentiles, a 15-rule SQL review engine, Kafka message browsing with monitoring & alerts, a bilingual UI (Traditional Chinese / English), a built-in AI assistant (natural-language SQL, AI review and tuning advice) and the dbk CLI. Free and open source (MIT), with installers for Windows, macOS and Linux. - [VS Code Super Mermaid](https://blog.markkulab.net/en/tools/super-mermaid): Super Mermaid is a VS Code extension for beautiful Mermaid diagrams out of the box: auto-colored live preview, mouse pan & zoom, high-res PNG / SVG export, 21 templates and multiple themes. Free and open source (MIT). - [React Super Mermaid](https://blog.markkulab.net/en/tools/react-super-mermaid): react-super-mermaid is an open-source React component library: render beautiful Mermaid diagrams with a single , with built-in colorful / sketch themes, pan & zoom, in-diagram search, and high-res SVG / PNG export. Lightweight, SSR-safe, fully typed. Free and open source (MIT). - [Jira / Confluence Super Mermaid](https://blog.markkulab.net/en/tools/jira-super-mermaid): An Atlassian Forge app: write Mermaid syntax directly inside a Jira issue or a Confluence page and get flowcharts, sequence diagrams, state machines and Gantt charts. 11 diagram types, SVG / PNG export, light and dark themes, full CJK support. Runs on Atlassian: your diagrams live in your own site and the app calls no third-party service. Free, coming soon to the Atlassian Marketplace. - [Mermaid Live Preview](https://blog.markkulab.net/en/tools/mermaid-preview): Write Mermaid in your browser, see it render instantly, and share the whole diagram as a single link. No sign-up, nothing uploaded to a server, and mermaid.live share links work as-is. - [React Intl Phone Number](https://blog.markkulab.net/en/tools/react-intl-phone-number): react-intl-phone-number is an open-source React component: framework-agnostic and antd-free, with E.164 in/out, a searchable flag / country-code dropdown, configurable validation levels (strict / mobile-strict / loose), themeable CSS, and i18n — phone logic powered by google-libphonenumber. Lightweight and fully typed. Free and open source (MIT). - [Uptime Kuma Cluster](https://blog.markkulab.net/en/tools/uptime-kuma-cluster): Turn single-node Uptime Kuma into a highly available cluster: OpenResty + Lua smart load balancing, shared MariaDB state, health checks and automatic failover, plus cluster-management REST APIs. One Docker Compose command to start. Free and open source (MIT). - [Special Education](https://blog.markkulab.net/en/education): Learning materials crafted for special education students ### Daily podcasts - [Mark's Tech Insights — Daily AI News](https://blog.markkulab.net/en/category/tech-news): Daily curated AI and tech trends. Catch the latest developments via audio summaries — covering AI applications, software architecture, DevOps, and engineering practice. — RSS: https://blog.markkulab.net/feed.xml - [AI股市蝦聊](https://blog.markkulab.net/en/category/ai-stock-chat): Every trading day, an AI-analyzed take on the Taiwan stock market, delivered as a two-host conversation covering the session and the next-day outlook. — RSS: https://blog.markkulab.net/ai-stock-chat/feed.xml - [開源好物週報](https://blog.markkulab.net/en/category/open-source-weekly): A weekly two-host pick of free open-source tools surfaced from real Hacker News, GitHub, and Reddit buzz — what pain they solve and the fastest way to get started. — RSS: https://blog.markkulab.net/open-source-weekly/feed.xml ### Newsletter [Subscribe to the newsletter](https://blog.markkulab.net/en/subscribe) — Be the first to know about new posts. No spam, unsubscribe anytime.