How to transition Decision from Not Started?

Question

I'm quite new to the Confluence tool and have been able to create a "fake" decision page for some team members. However, I'm unable to move it to "in progress" and the team members I've requested a decision from using the @Name insert, didn't get a notification/alert. What am I missing?

Thanks for your help.

Brant Schroeder · Accepted Answer

@Eilene Jones Welcome to the Atlassian community

If you are using a decision page you will have to update the status manually.

The individuals that you added as approvers should be notified on the page creation.

You will need to develop a process to get approvers involved and how the status will be updated.

Levente Szabo _Midori_ · Accepted Answer

@Eilene Jones Your full use case is not clear, but you can implement automatic Confluence page status updates and what's maybe more relevant to your use case. automated notification emails on certain events or page status updates.

For example, you can set an owner for the Confluence page, who gets a notification every time the page status changes, plus on preset periods, for expiring documents, like every 6 months, or every year, etc.

I hope these add value to your workflow and if you are new to Confluence, I suggest learning more about Confluence content lifecycle management implemented by Better Content Archiving.

A short video tutorial on automatic email reminders.

(Please note that Better Content Archiving is a free/paid, supported app and I'm part of the team developing it.)

Alexander Ovsyannikov_4ka6bw · Accepted Answer

Hi everyone,

As noted earlier, out of the box decision pages with statuses need to be updated manually. However, Atlassian Marketplace apps can offer better solutions for this use case.
For example, our Handy Macros for Confluence helps make these decision updates quicker. Handy Status allows creating predefined status sets with options to choose from. You can change statuses in a second by clicking them when viewing a page. Handy Status keeps its history for workflows requiring clear understanding of time and people connected to the status process.

Handy Date also works well for this use case as you can add date-pickers to your decision pages and save time on page editing.