Tasks and progress

The task overview brings together project work needing your attention and work already in progress. Open it after selecting the correct project.

Before you start — Select the project and distinguish actions awaiting your response from work already processing. The list provides follow-up; the associated item explains its question, confirmation or result.

Find your next action

Complete a required action on its associated item to retain the right context.

1. Click the tasks icon in the top bar to open the task overview.
2. Read To do.
3. Open the item whose question or prerequisite needs a response.
4. Complete the action in the screen that opens.
5. Return to the overview and review its state.

The action may concern project preparation, a clarification, a payment, a domain verification or another project prerequisite. Complete it in its own context rather than replying in an unrelated request.

Follow work already being processed

Read the detail to determine whether processing needs intervention or simply needs to continue.

1. Read In progress.
2. Identify the function, request or roadmap concerned.
3. Open the related detail when available.
4. Read the progress and any newly requested information.

An in-progress item does not always require a response. Check whether its detail asks you to do something before submitting another request for the same work.

One request can be processing while another asks you to clarify a rule. Answer the second item from its detail, then return to the overview. Creating another request for the first item would not provide the information that the second one needs.

Consult previous activity

Use history to review what was delivered for your project, then open the original item for its explanation.

1. Open the task history view.
2. Browse the entries, newest first, with Previous and Next (50 per page).
3. Read its date, description and recorded status.
4. Open the related project detail when you need the original context.

The history lists deployments, shipped roadmaps, executed Studio changes, created modules and paid invoices. Studio history and roadmap details provide further context for their respective changes.

Verify that completed work is available

Check the application before treating completed work as a change available to production users.

1. Find the completed work item and its relevant page.
2. Test the expected task in development.
3. Read the project version in Deployment.
4. Check the environment version before telling users a change is live.

Both the task outcome and the environment’s published version have been verified.

Note — An empty task list is not evidence that an uninstalled project is ready. Check setup, infrastructure availability and the selected project when the tools show a preparation message.