You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@devlake.apache.org by "dosubot[bot] (via GitHub)" <gi...@apache.org> on 2026/04/29 21:20:40 UTC
Re: [D] Project best practices [incubator-devlake]
GitHub user dosubot[bot] edited a comment on the discussion: Project best practices
<!-- Greeting -->
Hi @varsis! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the incubator-devlake team.
<!-- Answer -->
DevLake projects are flexible and can aggregate data from multiple repositories and boards, so you have options for organizing them. Many teams set up projects per domain or product line, especially when repos and boards map cleanly to business boundaries. This makes dashboards and metrics more meaningful for stakeholders and simplifies data management. For mono repos or cross-domain boards, DevLake’s project mapping lets you associate multiple scopes (repos, boards, etc.) with a single project, so you can group related data even if it spans different sources [source](https://github.com/apache/incubator-devlake/blob/2c15ad880dce830c6512fa58039527cbf4745b8b/backend/plugins/org/tasks/task_data.go#L22-L52).
Tagging is now supported in DevLake, so you can assign tags to projects for filtering, dashboarding, and tracking by path, CODEOWNERS, or any other convention that fits your workflow [source](https://github.com/apache/incubator-devlake/pull/8334). This is especially useful if you want to create broader projects (like “backend”, “web”, or “mobile”) and then use tags to slice data by domain, team, or use case.
If your teams use boards that aren’t tied to a single repo or domain, you can include those boards in multiple projects or use tags to track cross-team work. For large setups, some users create projects with many repos and boards, then rely on multi-project dashboards and tags for company-wide metrics aggregation [source](https://github.com/apache/incubator-devlake/issues/8448).
In short: organize projects by domain or product line if possible, use project mapping to group related scopes, and leverage tags for flexible filtering and reporting. This approach scales well and keeps your data model aligned with your organization’s structure and reporting needs.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fincubator-devlake).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fincubator-devlake).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fincubator-devlake#message_id=bfdb36bb-11b3-4b82-8744-8b093ebec236) [](https://github.dosu.com/apache/incubator-devlake?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fincubator-devlake) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fincubator-devlake)
GitHub link: https://github.com/apache/incubator-devlake/discussions/8652#discussioncomment-15090759
----
This is an automatically sent email for dev@devlake.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@devlake.apache.org