bcgov / bcgov/STRR

Enhance Test Environment to Reflect Municipality-Specific Rules for Help Desk Support

Open
#1,481 1 comment 0 reactions 0 assignees View on GitHub
STR
Dominant language
Python
Stars
2
Forks
22
Avg merge
2d 35m
Merged PRs (30d)
11

Description

Background:

Help Desk agents rely heavily on the test environment to support callers with registration and renewal processes. However, the current setup does not accurately reflect the variations in rules and layouts that exist across different municipalities.

Problem:

Agents are unable to fully replicate the customer experience because municipality-specific configurations (e.g., Business License rules) are missing or incomplete in the test environment.

Example :

In the Test environment for the same address – it says Short Term rentals are allowed in any of the hosts properties and does not mention a Business License

image.png

The screenshot from the citizen for the same address it it saying the property requires a Business License:

Impact:
• Reduced ability for Help Desk to effectively assist customers
• Increased handling time for support calls
• Risk of providing incorrect guidance
• Poor alignment between test environment and production experience

Recommendation:

To enhance test data to include all municipalities where different rules apply (e.g. Business Licence) ensuring agents can simulate real customer scenarios across all supported regions.

Acceptance Criteria:
• Agents can select and test scenarios for different municipalities
• Municipality-specific rules are reflected accurately in the test environment
• UI/layout matches what customers see in production
• Help Desk confirms improved ability to support customer scenarios

Notes:
This improvement supports both operational efficiency and customer experience by enabling more accurate troubleshooting and guidance.

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by locating the test-environment configuration and municipality-specific rule data, then compare the relevant test and production scenarios; done means agents can select municipalities, see accurate rules and layouts, and confirm the Help Desk scenarios work.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.