We are building the native Collabase GitHub App to bridge the gap between project planning and code execution. Our goal is to reduce context switching by letting you manage core repository actions directly from your tasks, keeping your development workflow centralized. Here is what we are scoping for this integration: 🚀 Standardized Branch Creation: Create branches directly from a Collabase task. Branch names are auto-generated based on your team's templates (e.g., feat/TASK-123-new-feature), ensuring consistent naming conventions without manual effort. 🔄 Integrated PR Management: Open pull requests from within the task view. This automatically links the code changes to the relevant project context and requirements. 🚦 Real-time CI/CD & Review Status: Monitor the complete pull request status directly on the task card. This provides instant visibility into running GitHub Actions, build outcomes, and pending or completed code reviews. 🔗 Bidirectional Issue Linking: Connect existing GitHub Issues with Collabase tasks. This ensures that development operations and project management share a reliable single source of truth. Since every dev team has its own unique workflow, we want to build this together with you. Vote if this integration would solve a bottleneck for your team. To help us scope the feature correctly, please use the comments to share your ideas, current workarounds, or specific GitHub processes you need us to support.

Brian Trepto 1 day ago

Sep 30

High Priority

Reliable documentation is the foundation of effective collaboration. Once a knowledge base becomes cluttered with outdated information, teams stop trusting it and revert to asking repetitive questions. We are introducing Knowledge Health features within the Docs module to help you actively manage, review, and verify your articles, ensuring your single source of truth remains exactly that. Here is what we are scoping for Knowledge Health: 📅 Review Cycles & Expirations: Set specific validity periods for critical documents. Automatically flag an article as "Needs Review" after a predefined timeframe (e.g., every 6 months) to ensure the content reflects the latest processes and architectural decisions. 👤 Explicit Stewardship: Assign dedicated owners or subject matter experts to individual pages. When a document expires or is flagged for review, the system will automatically notify the responsible maintainer, eliminating ambiguity about who should update it. 🚦 Health Status Indicators: Clearly mark documents with visible status badges (e.g., "Verified", "Outdated", "Under Review"). This gives readers immediate visual context on whether they can trust and execute based on the information they are reading. 📊 Relevance & Usage Analytics: Identify which documents are heavily trafficked and which have not been viewed in months. Use these insights to confidently archive redundant pages and focus your maintenance efforts on the most critical operational assets.

Brian Trepto about 4 hours ago

High Priority

Maintaining a reliable single source of truth in your Registry is impossible if you have to manually update user directories, hardware assignments, or software licenses. We are expanding our import capabilities to automatically sync data from your core IT and identity systems directly into Collabase, ensuring your asset management stays accurate without manual overhead. Here is what we are scoping for the new import methods: ☁️ Identity Provider Sync (Entra ID & Google Workspace): Automatically import and continuously sync user directories, organizational units, and managed devices directly from Microsoft Entra ID or Google Workspace. Instantly use these synced records to assign tasks, define permissions, or map users to hardware assets in your Registry. 🗄️ Direct Database Connections: Connect directly to external databases (e.g., PostgreSQL, MySQL, MS SQL) to pull in specialized operational data, inventory lists, or legacy system assets without needing to export and upload CSVs. 🔄 Smart Attribute Mapping: Visually map external fields—such as Entra ID job titles, Google Workspace departments, or custom database columns—directly to your custom properties in the Collabase Registry. ⏱️ Automated Sync Schedules: Configure recurring sync intervals (e.g., hourly, daily) to ensure Collabase always reflects the current state of your external systems. The integration will automatically update mapped fields and flag deleted or disabled accounts.

Brian Trepto about 4 hours ago

High Priority

Finding specific information and synthesizing context across different modules can be a massive time sink. We are introducing CollabaseBrain, an intelligent conversational interface designed to query, analyze, and interact with your entire workspace using secure, local AI. Here is what we are scoping for the Collabase Brain integration: 🔍 Cross-Module Semantic Search: Move beyond exact keyword matching. Use natural language to search your entire environment, performing semantic queries across Tasks, Docs (Pages), Whiteboards, Registry Objects, and Test Runs to find exact concepts and context, not just file names. 💬 Context-Aware RAG: Ask complex questions about your projects or documentation. Brain uses Retrieval-Augmented Generation (RAG) to synthesize answers directly from your underlying data, providing accurate, cited responses based solely on your internal single source of truth. 🛠️ Actionable AI Skills: Brain is not just a read-only search engine; it can execute work. Instruct the chatbot to summarize meeting notes, draft manual test cases, generate sub-tasks, or update Registry assets directly from the conversational interface. 🔌 External Reach via MCP: Through the Model Context Protocol (MCP), extend Brain's capabilities to your third-party tools. Securely query external databases or trigger actions in connected enterprise systems directly through the Collabase chat.

Brian Trepto about 4 hours ago

High Priority

Managing complex projects and structured data often requires dynamic calculations. We are introducing Formula Custom Fields to allow you to compute values, calculate risk scores, and automate metrics directly within Collabase, eliminating the need to continuously export data to external spreadsheets just to run basic calculations. Here is what we are scoping for Formula Fields: ➕ Mathematical Operations: Perform standard calculations (add, subtract, multiply, divide) using existing numeric custom fields or standard system properties (e.g., calculating "Remaining Budget" by subtracting logged hours from estimated hours). 🔀 Logical Functions (If/Else): Utilize conditional logic to dynamically output values or text based on the state of other fields. For example, automatically output "High Risk" if a financial impact field exceeds a specific threshold. 📅 Date Calculations: Compute the exact duration between dates. Easily calculate metrics like lead time or cycle time by finding the difference between a task's creation date and a custom "Deployment Date". 🔼 Hierarchical Rollups: Aggregate data from nested child tasks or linked Registry items. Automatically sum up financial costs, average out story points, or count the number of open sub-tasks directly on the parent epic.

Brian Trepto about 4 hours ago

Sep 30

High Priority

Complex projects often contain deeply nested structures that are difficult to analyze in flat lists or standard Kanban boards. We are introducing a dedicated Tree View tab in the Projects module to provide a visual, mindmap-style representation of your work, allowing you to easily drill down from high-level objectives to granular deliverables. Here is what we are scoping for the Tree View: 🌳 Visual Work Breakdown: Display your project architecture as a branching, node-based tree. This provides immediate clarity on the relationship between overarching epics, standard tasks, and detailed sub-tasks. 🔍 Deep Drill-Downs: Easily expand and collapse nested hierarchies. Navigate vertically through multiple layers of work without losing your structural context or cluttering your screen. ⚡ Rapid Project Scoping: Add new child or sibling tasks directly within the tree structure using keyboard shortcuts. This makes the view highly effective for initial project breakdown sessions and rapid structural planning. 🖱️ Structural Drag-and-Drop: Reorganize your project hierarchy on the fly. Drag a task to a different parent node to instantly update its relational mapping across the entire system.

Brian Trepto about 4 hours ago

Low Priority

We are concidering a dedicated Collabase desktop client to provide a more secure, focused, and easily managed environment. For highly regulated organizations, relying entirely on web browsers can introduce risks from third-party extensions and create a fragmented user experience. Here is what we are scoping for the desktop application: 📦 Enterprise Deployment Support: Packaged for easy, centralized distribution via standard MDM (Mobile Device Management) solutions like Microsoft Intune or Jamf. We plan to provide standard installers (e.g., MSI, PKG) for automated, silent rollouts across your entire fleet. 🔒 Isolated Security Context: Run Collabase in a dedicated, sandboxed environment. This separates your sensitive project and registry data from general web browsing activity and potentially vulnerable browser extensions. 🔔 Native OS Integration: Leverage system-level features like native push notifications, taskbar badge counts, and launch-on-startup. This ensures critical SLA alerts and project updates are never lost in a sea of open browser tabs. ⚡ Focused Workspace: Provide a dedicated application window for your operational system, reducing context switching and keeping your team's attention solely on the work at hand.

Brian Trepto about 4 hours ago

Low Priority

We are planning a native Automation Engine to connect Collabase with your broader operational stack and automate complex processes. By combining deterministic rule-based logic with local AI capabilities, our goal is to let you build powerful, multi-step workflows entirely within your sovereign environment. Here is what we are scoping for the Automation Engine: 🔌 Third-Party Integrations & MCP: Connect directly with external tools like Bexio and HubSpot. By supporting the open Model Context Protocol (MCP), we allow both standard automation rules and our local AI to securely query and interact with your external systems. 🤖 Autonomous AI Agents: Deploy specialized AI agents as actionable steps within your workflows. Assign them to handle unstructured tasks—such as parsing incoming support emails, classifying data, or making routing decisions—before passing control back to strict operational rules. ⏱️ Event & Scheduled Triggers: Kick off workflows dynamically based on specific actions in Collabase (e.g., a task changing status) or run them on a strict time schedule (e.g., a weekly data sync). 🔀 Conditional Logic (If/Else): Build branching workflows that route actions differently based on specific field values, tags, or metadata criteria. ✅ Human-in-the-Loop Approvals: Pause an automation to require explicit manual approval from a designated user or team before executing critical downstream actions (e.g., executing a deployment or sending a finalized quote). 💻 Custom Code Execution: For complex edge cases that outgrow standard visual builders, inject custom scripts directly into the workflow to parse data or interact with external APIs. 🔄 Native Collabase Actions: Automate internal state changes, such as generating tasks, updating Registry assets, or notifying specific team members when conditions are met.

Brian Trepto about 4 hours ago

Dec 31

High Priority

We are enhancing the Projects Timeline view to support complex project planning. Our goal is to move beyond simple start and end dates by visualizing exactly how tasks relate to each other. Here is what we are scoping for Timeline Dependencies: 🔗 Visual Dependency Mapping: Draw and visualize relations directly on the timeline. Instantly see which tasks are blocking progress and which are dependent on prior work. ⚠️ Schedule Conflict Warnings: Get immediate visual feedback if a dependent task is scheduled to start before its prerequisite is completed, preventing impossible timelines from being planned. 🔄 Cascading Adjustments: When you drag a blocking task to a new date, optionally shift all dependent tasks automatically to maintain the project sequence without manual recalculation. 🔍 Critical Path Identification: Highlight the sequence of crucial tasks that directly determine the project's final delivery date, helping project managers focus on the highest-risk items.

Brian Trepto about 4 hours ago

Low Priority

We are planning a native Calendar View within the Projects module to help you visualize timelines, deadlines, and scheduled events. Our goal is to provide a clear, chronological overview of your work, making it easier to spot bottlenecks and coordinate complex schedules. Here is what we are scoping for the Calendar View: 📌 Dynamic Date Mapping: Plot tasks on the calendar using standard due dates or any custom date fields you have created (e.g., "Deployment Date", "Maintenance Window", "Review Date"). 🗓️ Flexible Timeframes: Toggle between monthly and weekly views to switch from a high-level strategic overview to detailed, day-to-day operational planning. 🔄 Dedicated Change Calendars: Leverage custom date fields to build specific IT Change Calendars. This allows infrastructure and development teams to coordinate releases, visualize freeze periods, and avoid conflicting maintenance windows. 🖱️ Drag-and-Drop Rescheduling: Adjust timelines on the fly by dragging and dropping tasks to new dates. This automatically updates the underlying date fields without needing to open the task details.

Brian Trepto about 5 hours ago

Low Priority

We know that the biggest barrier to adopting a new platform is leaving the legacy system behind. To support your transition to a sovereign infrastructure, we are building a dedicated migration tool designed to reliably import your existing data from Jira Data Center and Confluence Data Center directly into Collabase. Here is what we are scoping for the migration path: 📦 Jira to Projects Mapping: Import your issues, epics, comments, attachments, and custom fields. Our tool will allow you to map your existing Jira issue types and statuses directly to Collabase tasks and workflows. 📄 Confluence to Docs Conversion: Bring over your spaces, page hierarchies, and attachments. We aim to preserve your text formatting and automatically update internal links to work within Collabase Docs. 🗺️ Smart User & Permission Alignment: Map your existing Atlassian user directories to Collabase accounts. The tool will help translate basic permission schemes so that restricted pages and private projects remain secure after the move. 🔄 Phased Migration Support: Migrate project-by-project or space-by-space rather than forcing a massive "big bang" switch. This allows you to run test imports and transition individual teams at their own pace with minimal disruption.

Brian Trepto about 5 hours ago

High Priority

We are expanding the Test Management module to move beyond simply categorizing tests as "automated." Our goal is to deeply integrate your automated testing pipelines directly into Collabase, eliminating manual status updates and bridging the gap between manual QA and automated execution. Here is what we are scoping for the next evolution of Test Management: ▶️ Direct Execution Triggers: Trigger automated test suites (e.g., via webhooks or direct CI/CD integration) directly from within a Collabase Test Run. There is no need to switch to your CI tool to kick off a specific test cycle. 📥 Automated Result Ingestion: Automatically capture the execution results (pass, fail, skipped) and attach relevant logs or error traces directly to the respective test cases in Collabase. 📊 Unified Quality Reporting: View the outcomes of both manual test executions and automated test runs side-by-side in a single, consolidated dashboard. Get a complete, real-time overview of your release readiness without having to manually aggregate data from different tools.

Brian Trepto about 5 hours ago

High Priority

We are expanding Collabase Projects to support complete IT Service Management (ITSM) workflows. Our goal is to provide a unified environment where support teams and end-users can interact seamlessly, eliminating the need for a separate, siloed ticketing system. Here is what we are scoping for the initial ITSM release: 📥 Dedicated Request Queues: Structure incoming work with specialized triage views. Route, prioritize, and assign tickets efficiently without cluttering your standard development or project boards. 🌐 Customer Service Portal: A clean, dedicated front-end interface where internal or external users can easily submit support requests, communicate with agents, and track the status of their tickets. 📝 Custom Request Topics & Intake Forms: Define specific support categories (e.g., "Hardware Issue", "Access Request") within the portal. Attach customizable forms to each topic to ensure agents capture all necessary structured data upfront, drastically reducing back-and-forth communication. 👥 Customer Context: Link support requests directly to specific external clients or internal departments. This maintains a clear history of interactions and allows you to tie tickets to specific hardware or contracts in your Registry. 📚 Integrated Knowledge Base: Surface relevant Collabase Docs directly within the Service Portal. This enables self-service, allowing users to find solutions to common problems before creating a new ticket. ⏱️ SLA Management: Define and monitor Service Level Agreements. Track metrics like time-to-first-response and time-to-resolution, complete with visual warnings and automated escalations for approaching breaches.

Brian Trepto about 5 hours ago

High Priority