Jira for project management: how we run client projects

Why we run projects in Jira

A CRM project has small moving parts everywhere: a field here, an automation there, a form that needs mapping, a question for the client. In email, they get lost.

In Jira, each one is a ticket with an owner and a status. We can see what is open, the client can see what is waiting on them, and nobody has to ask where things stand.

We keep it simple on purpose. Small and medium teams do not need a full agile process to get value from Jira. They need clear tickets and a board people check.

1. One project per client

Each client gets its own Jira project. Their tickets, comments and files stay together, kept apart from other clients.

• Epics for the large pieces of work, such as an integration or a migration.
• Stories and tasks for the work itself.
• Bugs for anything that is not working as expected.
• Sub-tasks when one ticket needs steps owned by different people.

2. Write tickets anyone can pick up

A ticket should make sense to someone who was not on the call. Every ticket captures the same basics.

When a client sends a list of top priorities, each item becomes its own ticket. One big ticket with ten requests is hard to track and hard to close.

3. Keep the board short and honest

A kanban board with clear columns does more than a long workflow nobody follows. These are the statuses we use.

• Backlog: agreed work that has not started.
• In Progress: someone is working on it now.
• Blocked: waiting on access, a decision or another system.
• Ready for QA: built, and being tested before the client sees it.
• Pending Client Review / Feedback: the client checks it and replies.
• Done: tested, reviewed and closed.

We also use On Hold and Deferred for work the client has paused or moved to later, so it stays visible without cluttering the active columns.

4. Make it easy for the client to see progress

The board is only useful if the client can read it. A few filters and fields answer the questions clients ask, without a status meeting.

• Open issues for the client, filtered by owner or project.
• Tasks completed by whom and when, using Task Completed By and Task Completed Date/Time fields.
• Everything waiting on the client, in the Pending Client Review / Feedback column.
• Jira data pulled into Google Sheets when a client wants a report or a planning sheet.

5. Log time on the ticket

We connect Clockify to Jira, so the team logs hours against the ticket they worked on, with the ticket number and a short description.

That keeps time reports tied to real work, and it shows where the hours went on each part of a project.

6. Document as you go, hand it over at the end

Jira holds the history of the work. Documentation explains how the finished system works. We write both.

• Field mappings for forms, chats and calls into the CRM.
• How automations, flows and code work, for the next developer.
• Training guides for the team that will use it.
• A documentation and knowledge transfer ticket at the end, so the handover is part of the project, not an afterthought.

At the end of a project, the client gets full documentation and ownership of the code.

Setting up Jira for your own team

You can copy this setup: one project, three fields on every ticket, six statuses, and a filter for what is waiting on whom. Add time tracking and Sheets reporting when you need them.

Before you set up the board, it helps to see every system the project touches. Our free tech stack diagram builder maps them. If you want help with Jira or the CRM project behind it, book a free call.