For Confluence Cloud

    Proment

    A status, an owner, a next action and a timeline — on a Confluence page.

    Coming soon on the Atlassian Marketplace

    What it does

    A topic is a page

    Create a topic as an ordinary Confluence page, or bring an existing page into Proment.

    The state sits beside it

    Keep its status, owner, next action, priority and timeline together.

    See what needs attention

    Find work that is unassigned, overdue, not picked up, or quiet.

    Inside your site

    The app runs on Atlassian infrastructure inside your own Atlassian tenant.

    Proment is a hobby project.

    It is built and maintained by one person, part-time, alongside other work: a solo developer in Belgium who is passionate about technology and about how organisations keep track of things, and who built the tool he wanted.

    There is no team, support desk or roadmap. There is no commitment to develop Proment further, add any feature, or keep pace with changes to Confluence.

    What happens to your pages

    Proment never edits, moves or deletes a page it did not create. This boundary is enforced in code, not merely promised. Installing Proment cannot damage the pages already in your spaces. Existing pages keep Confluence's own history, export and backups, and nothing about them changes.

    What Proment adds around those pages — statuses, timelines, stakeholders and configuration — exists only there, in one copy, with no vendor-side restore path because there is no vendor side. Keep anything important in your own records and back it up. Do not let Proment be the only place something exists.

    Topics created by Proment are ordinary Confluence pages in your own spaces. They remain if the app is removed.

    Support

    The Atlassian Marketplace sets a response floor for every app: within 24 hours for anything Atlassian identifies as critical, and within five business days for everything else. This is the Marketplace's floor, not an additional promise made for Proment, and it is a maximum rather than a target.

    A response is a reply acknowledging the message, not a diagnosis, fix, workaround or timetable. Critical means whatever Atlassian determines is critical; marking an email urgent does not make it critical. Business days are Monday to Friday, excluding Belgian public holidays.

    A reply saying “yes, that is broken, and I do not know when I will get to it” satisfies the response requirement in full. Support does not include a commitment to fix a problem or develop the app further.

    mail.lucanise@gmail.com