Balancing Product Tracking, Development and Releases in Jira for small team

[Sophia]

Hello,

I’m looking for feedback on setting up a Jira organization for a platform product and engineering team.

We are a small SaaS company with 4 developers split across 2 teams (Core/Backend and Frontend). I act as both Product Owner and functional tester.

Some User Stories needs contributions from both teams simultaneously. Developers track their work through tasks and subtasks linked to User Stories, throug 2 dedicated boards (Scrum for core team, Kanban for front-end team).

We are trying to establish a simple setup that allows us to track product progress, team activity, PO validation, and deployments across environments.

In particular, I’m wondering how to draw the line between what should be represented through Jira workflows and what should instead be handled through boards, filters, custom fields, dashboards, or automation rules.

How do you distinguish development progress from delivery progress?

Do you include DEV → PREPROD → PROD stages directly in your workflows, or do you manage environment tracking differently? Does PO functional validation belong in the Story workflow, or is it handled through a separate process? At the moment, I have created a dedicated board with four statuses to track PO validation.

I’d be very interested in hearing how other small software or SaaS companies have approached this challenge while keeping Jira simple and avoiding unnecessary complexity.

Thanks for your feedback.

[Tomislav Tobijas]

Hi @Sophia ,

A 'million dollar questions' I'd say 😅

I can just talk from experience seeing how different companies operate (as I work in consulting), and I can immediately say that there's no right way. Everyone operates differently. 👀

Anyway, related to environment tracking and validation - Atlassian will here probably recommend using Jira's integration with CI/CD tools (like Bitbucket Pipelines or Jenkins) instead of adding "DEV" or "PREPROD" statuses in the workflow. 

For PO validation, you can integrate this into the Story workflow using a "Waiting for Approval" status and then automate things like > transition stories once underlying sub-tasks are completed. ⚙️

Usually, you can distinguish types of progress to:

Development progress	Delivery progress
Tracked at the Task or Sub-task level within team-specific boards.	Tracked at the User Story or Epic level.

If we had to sum it up:

Workflows should represent the status of a work item (the "what"), while boards, filters, and dashboards should manage the view of that work (the "who" and "where"). It is best practice to keep workflows simple by limiting statuses and transitions to avoid unnecessary complexity. Use boards to visualize different team processes; for example, your Core team can use a Scrum board for sprint-based work while the Frontend team uses a Kanban board for continuous flow.

In the end, and when it comes to statuses and workflows, what I've seen is something like ... > "Prod ready" > "Released on Prod" or something in that area. Staging and testing are mainly combined into development statuses and things like "In review" if we're talking about actual tests on developed features. 🧪

Hope this helps.

Cheers,
Tobi