All guides
Admin

Roadmaps

Screen guide

Before you start

Use an administrator account with permission to manage this feature. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /admin/roadmaps on your site.

Steps

Create or update: Save changes / Save and add to roadmap

  1. Open /admin/roadmaps/suggestions on your application domain, using the administrator account for this task.
  2. Find the form containing Title, Description, Roadmap content. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Use the button shown for the current state: Save changes, Save and add to roadmap. Creation and editing can show different labels; submit the form once.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
TitleRequired. Enter the title for this task, using the help or example shown by the form. Maximum 255 characters.
DescriptionRequired. Enter the description for this task, using the help or example shown by the form.
Roadmap contentEnter the roadmap content for this task, using the help or example shown by the form. The form’s example is Optional. Use this to refine the roadmap item content before adding it.. Replace it with your own value.
StageEnter the stage for this task, using the help or example shown by the form.
StatusChoose Enable, Disable.

Use Save changes

  1. Open /admin/roadmaps on your application domain, using the administrator account for this task.
  2. Find the form containing Title, Description, Stage. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save changes. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
TitleRequired. Enter the title for this task, using the help or example shown by the form. Maximum 255 characters.
DescriptionRequired. Enter the description for this task, using the help or example shown by the form. Maximum 255 characters.
StageRequired. Enter the stage for this task, using the help or example shown by the form. Maximum 100 characters.
PriorityOptional unless the current form requests it. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 9999.
ContentOptional unless the current form requests it. Enter the content for this task, using the help or example shown by the form.
StatusRequired. Choose Enable, Disable.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct administrator account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 275481cdd3c8519a24c5ecf5cac3e11ceb1708d8

Source-only route information
MethodSource-default route
RESOURCE/admin/roadmaps
POST/admin/roadmaps/list
GET/admin/roadmaps/update
GET/admin/roadmaps/edit/{id}
POST/admin/roadmaps/save
POST/admin/roadmaps/status/{any}
POST/admin/roadmaps/destroy
GET/admin/roadmaps/suggestions
POST/admin/roadmaps/suggestions/list
GET/admin/roadmaps/suggestions/update
GET/admin/roadmaps/suggestions/edit/{id}
POST/admin/roadmaps/suggestions/convert/{id}
POST/admin/roadmaps/suggestions/save
POST/admin/roadmaps/suggestions/status/{any}
POST/admin/roadmaps/suggestions/destroy
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
titlemodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapsController.php
descriptionmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapsController.php
contentmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapsController.php
statusmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapsController.php
status_labelmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapsController.php
prioritymodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapsController.php
titlemodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapSuggestionsController.php
descriptionmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapSuggestionsController.php
roadmap_contentmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapSuggestionsController.php
statusmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapSuggestionsController.php
status_labelmodules/AdminRoadmaps/app/Http/Controllers/AdminRoadmapSuggestionsController.php