# Salesforce delivery where the board shows what actually shipped. > SyncOnAI 360 Projects is delivery management built into the platform that changes your Salesforce orgs. Each project has a board, backlog, sprints, roadmap, Gantt, releases, reports and wiki, and work items link to the audit findings that raised them and the proposals and deploys that delivered them. Source: https://synconai360.com/features/projects ## Key facts - **11**: Project views, from board and backlog to wiki and audit - **1**: Step from an audit finding to a work item - **Every**: Work item can link to the deploy that delivered it - **3**: Connectors: Jira, GitHub and Slack ## Why Salesforce project boards drift from reality Most Salesforce teams track work in one tool and change orgs in another. The board says done; the org says otherwise. Nobody can answer which requirement a production change belongs to without asking around. - **Done is not deployed.** A ticket moves to done when someone drags it. Whether the change reached production, and which version, lives somewhere else. - **Findings never become work.** Audits produce lists. Turning each finding into a scoped, estimated work item happens by hand, if it happens at all. - **Knowledge scattered.** Requirements in one place, decisions in chat, runbooks in a shared drive. The context for a change is gone by the time someone needs it. - **Status meetings to reconstruct status.** Leaders ask what shipped this sprint, and the team spends an hour matching tickets to deploys. ## What does Salesforce project management in SyncOnAI 360 include? Every project has a Board with work items by status, a Backlog of everything not yet in a sprint, Sprints to plan and run, a Roadmap and Gantt by epic with dependencies, a Calendar and Workload view to see who has too much, Releases to group work, Reports on the same report engine as the rest of the platform, a Wiki for project documents, the project's own Audit history and a Trash to restore deleted items. Work items carry a description, status, assignee, dates, custom fields, attachments, time tracking and history. Comments reply in threads with @mentions, and Watch notifies you when an item is commented on or changes status. - Board, backlog, sprints, roadmap and Gantt - Calendar, workload, releases and reports - Wiki, history and restorable trash - Threads, mentions and watchers on every item ## How are work items linked to Salesforce changes? Audit findings become work items in one step, carrying their evidence and estimate. Work items link to the proposals and deploys that delivered them, so the board shows what actually shipped, and the deploy receipt shows which work it belonged to. When an audit re-runs after the fix is deployed, the finding is marked verified fixed or regressed. The loop from problem to proof closes in one place instead of three. - Findings to work items with evidence and estimate - Work items linked to proposals and deploys - Fixes verified by the next audit run ## Can projects be configured to match how our team works? Project settings manage members and roles, custom fields on work items, webhooks and templates. Webhooks send events to another system when an item is created, updated, changes status, is commented on or gets an attachment; addresses on private networks are refused. Save any project's columns and fields as a template, and start new projects from it with everything copied in. Pages keep requirements, runbooks and meeting notes next to the work, and a recorded meeting's transcript can become a page. - Members, roles and custom fields - Webhooks for created, updated, status, comment and attachment events - Project templates - Pages for requirements, runbooks and meeting notes ## Does it work with Jira, GitHub and Slack? Yes. Raise audit findings as Jira Cloud issues for teams that plan there, record each deployed change as a GitHub pull request for teams that keep metadata in Git, and post deploy results to a Slack channel. Jira and GitHub are in beta. Admins connect each integration once for the workspace. Delivery stays in the tools people already use, with SyncOnAI 360 holding the link between the work and the org. - Jira: findings raised as issues - GitHub: deployed changes as pull requests - Slack: deploy results ## How do you report on Salesforce delivery? Each project's Reports tab uses the same report engine as the main Reports page, so the widgets a project lead builds and the dashboards leadership reads come from one source. Releases group work so a release report covers exactly what went out together. Across projects, the Command Center shows backlog KPIs and sprint progress beside org health and recent activity, so a delivery lead starts the day with both the work and the orgs in view. Because work items link to deploys, a report can say what shipped rather than what was dragged to done. - Project reports on the shared report engine - Release-level reporting - Backlog and sprint KPIs in the Command Center - Reports grounded in deploys, not card moves ## How delivery works in SyncOnAI 360 1. **Capture.** Create work items, or turn audit findings into them in one step. 2. **Plan.** Prioritise the backlog, plan sprints and group work into releases. 3. **Build.** Build the change in chat or on the builders and link the proposal. 4. **Ship.** The deploy is approved and receipted, and the item shows it. 5. **Verify.** The next audit confirms the fix, and reports show what shipped. ## Salesforce delivery, with and without SyncOnAI 360 | Without | With SyncOnAI 360 | |---|---| | Done means someone dragged the card | Done links to the deploy that shipped it | | Audit findings retyped as tickets | Findings become work items in one step | | Status meetings to match tickets to deploys | Reports on work and deploys from one source | | Context lost across tools | Pages, comments and history beside the work | | No proof a fix held | The next audit marks it verified fixed or regressed | ## Who runs projects - **Delivery leads.** Plan sprints, releases and the roadmap beside the orgs being changed, with work items linked to the deploys that delivered them. - **Consultancies.** Run every client project in the same workspace as the client's org, so status reports point at shipped changes rather than card movements. - **Platform teams.** Turn audit findings into work items in one step, keeping each finding's evidence and estimate on the card. - **Platform owners.** See delivery across projects in reports that share one engine with every project's own Reports tab. ## Frequently asked questions ### Is SyncOnAI 360 a replacement for Jira? It can be, with boards, backlogs, sprints, roadmaps, releases and reports. Teams that keep Jira can raise audit findings there and use both. ### How do audit findings become work items? Select findings in the audit and put them on a project board in one step. Each work item keeps the finding's evidence and estimate. ### Can we see which deploy delivered a work item? Yes. Work items link to the proposals and deploys that delivered them, so the board shows what actually shipped. ### Do projects support custom fields? Yes. Add your own fields to work items in project settings, and save the project's columns and fields as a template for new projects. ### Can project events reach other systems? Yes. Project webhooks send events when items are created, updated, change status, receive comments or get attachments. Addresses on private networks are refused. ### Can deleted work items be recovered? Yes. Deleted work items go to the project's trash and can be restored. ### Where do requirements and notes live? In each project's wiki and in Pages, which keep requirements, runbooks and meeting notes beside the work. A recorded meeting's transcript can become a page. ### Is project management included in every plan? Yes. Every plan includes every feature. Plans differ in users, production orgs and whether AI is included. ### Can we see delivery across all projects? Yes. The Command Center shows backlog KPIs and sprint progress across projects, alongside org health and recent syncs, deploys and audits. ### How do releases work? Releases group work items so you can plan, track and report on what goes out together, alongside sprints and the roadmap. ### Can work items have attachments and time tracking? Yes. A work item has its description, status, assignee, dates, custom fields, attachments, time tracking and full history. ### Can managers delete wiki pages? Each project's wiki holds project documents, and managers and admins can delete wiki pages. ### Do comments support mentions? Yes. Comments reply in threads, you can edit or delete your own, and @mentioning a teammate notifies them. Watching an item notifies you of comments and status changes. ### Is project management included on the free plan? Every plan includes every feature. Free covers one user and one production org with its sandboxes, on your own Anthropic or OpenAI key, with no credit card and no time limit. Paid plans include AI and cover more people and production orgs.