Home › Solutions › Project Management With a Wiki and Calendar Built In

When the card links to the spec and the deadline lands on the calendar

From inside a Flocci Projects issue you can search the Flocci Library wiki and attach the spec page that defines the work — a bidirectional link, so the page shows the issue too — and you can push the issue onto Flocci Calendar as an event. Execution, documentation and schedule stay joined instead of living in three tools that only a human keeps in sync.

Who this page is for: Teams tired of copy-pasting between a tracker, a wiki and a calendar.

The standard stack is a tracker, a wiki and a calendar from three vendors, joined by pasted URLs. Those links rot the moment a page is renamed or an issue is closed, and nobody notices until a new engineer opens a card and finds a 404 where the spec used to be. The problem is not the tools; it is that the link is a string rather than a relationship.

In Flocci Projects the link is a relationship. Open an issue, search the Library from its Links panel, pick the page, and both sides now know about each other — rename the page and the reference follows. The same panel shows linked notes, calendar events, boards and related issues, so a card carries its full context rather than a paragraph of description hoping to explain it.

The calendar direction matters just as much. Push an issue onto Flocci Calendar and its due date becomes a real event on the team's schedule, with a marker on the card showing it is already there. It is the small, boring integration that stops a sprint deadline from existing only inside a tracker that non-engineers never open — and it works because Projects, Library and Calendar share one identity, one organization model and one bill.

What you get

Search the Library wiki and attach the spec page from inside the issue
Links are bidirectional — the page shows the issue too, and renames follow
Push an issue onto Flocci Calendar as an event, with a marker on the card
Linked entities cover pages, spaces, notes, events, boards and other issues
One Google sign-in and one bill across Projects, Library, Calendar, Notes, Infinity and Timesheets

Start free with Google sign-in

Frequently asked questions

Which apps can a Flocci Projects issue link to?

Library wiki pages and spaces, Notes, Flocci Calendar events, boards and other issues. Linking is done from the issue's Links panel, which includes a live search across the suite so you do not need the URL.

Is this different from pasting a Confluence or Notion link into a ticket?

Yes, in two ways: the link is stored as a relationship on both sides rather than as text in a description, so the wiki page shows the issue too, and a rename does not break it. A pasted URL is a snapshot; this is a live edge.

Does the calendar event update when the issue's due date changes?

Pushing an issue to the calendar creates an event and the card shows a marker that it is on the calendar. Treat it as a one-way push at the moment of creation rather than a continuously synced field — if you move the due date, revisit the event.

Do I have to use the whole suite?

No. Flocci Projects is complete on its own; the cross-app links are additive. But because the suite shares one login, one organization and one credit wallet, adopting Library or Calendar costs nothing extra in accounts or admin.