MokoConsulting/MokoJoomCross
1
0
Fork 0
Code Issues 105 Pull Requests Releases 1 Wiki Activity

Test: Per-service help links in service edit sidebar #76

New Issue
Open
opened 2026-05-29 04:12:43 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-29 04:12:43 +00:00
Owner
Copy Link
Copy Source

Test: Service Setup Guide Links

What changed

When a service type is selected, a "Setup Guide" button appears in the edit sidebar linking to the KB article on mokoconsulting.tech.

Steps to test

  1. Edit a service → select Twitter → verify "Twitter Setup Guide" button appears
  2. Click it → verify it opens the correct KB article in a new tab
  3. Change service type to Facebook → verify link updates
  4. Select a new service (no type yet) → verify no button shown
  5. Test several service types to verify correct URL mapping

Labels

type: testing, priority: low

## Test: Service Setup Guide Links ### What changed When a service type is selected, a "Setup Guide" button appears in the edit sidebar linking to the KB article on mokoconsulting.tech. ### Steps to test 1. Edit a service → select Twitter → verify "Twitter Setup Guide" button appears 2. Click it → verify it opens the correct KB article in a new tab 3. Change service type to Facebook → verify link updates 4. Select a new service (no type yet) → verify no button shown 5. Test several service types to verify correct URL mapping ### Labels `type: testing`, `priority: low`
jmiller commented 2026-05-29 04:12:45 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/76-test-per-service-help-links-in-service-e

git fetch origin
git checkout feature/76-test-per-service-help-links-in-service-e
Branch created: [`feature/76-test-per-service-help-links-in-service-e`](https://git.mokoconsulting.tech/MokoConsulting/MokoJoomCross/src/branch/feature/76-test-per-service-help-links-in-service-e) ```bash git fetch origin git checkout feature/76-test-per-service-help-links-in-service-e ```
Sign in to join this conversation.
Labels
Clear labels
pending: testing
Implemented, awaiting testing
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Type Task
Status —
Priority —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomCross#76
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?