User can’t see feature/activity
Plan import error (e.g. must match template)
Not all regression features should be in the active phase
Satisfaction ratings in another format other than 5 stars
Test Plan isn’t cloned when creating a new project
“Set your start date in the future” Error
Can’t change phase date
What to check for:
Is the current date past the end date of the phase?
Why:
Once a phase has ended, it is locked in and it is no longer possible to make changes. This is because of the way dashboards are generated. Adjusting a phase after it has been completed will cause the dashboards to break and can result in bad data.
Suggested Solution:
Move features from the expired phase to a new, active phase.
User can’t see feature/activity
What to check for:
Does the team/user role have access to the feature?
Why:
Features will only show up within the Feature drop-down if users are a part of a team/user role with access to that feature. Features and activities will only show up on the home page/Activities drop-down if users are a part of a team/user role with access to that feature.
Suggested Solution:
Navigate to the Modify Feature page and check the Team Access block to see which teams are able to view the feature. Either turn on view access for a team the user is on or add the user to a team with access.
What to check for:
Is the Feature a part of a current phase?
Why:
Features/activities will only show up on the project home page/Activities drop-down when they’re a part of a current Engagement phase or they’re a New User Feature and the user has not yet completed their New User Features.
Suggested Solution:
If the feature is not a part of a current engagement phase, you can move the feature. If it is a regression feature, check the “Include Regression Features” option for that phase. If it’s a New User Feature, ensure the user has not previously completed their New User Features (adding new New User Features won’t re-trigger them).
Plan import error (e.g. must match template)
What to check for:
Do the headers match the template?
Why:
It’s possible a company’s licensing was changed and they’re using a template from their previous Centercode edition. Or perhaps they simply edited the headers within their template. In any case, the template being imported must match.
Suggested Solution:
Ensure the template matches the platform expectations exactly. IIt may be easiest to download a new copy of the template and fill it out again before importing.
Not all regression features should be in the active phase
What to check for:
Are regression features turned on for the active phase? Do users have view access for the feature?
Why:
When checking the Include Regression Features box, all regression features will be added to the phase. Users will only be able to see/interact with features when they have View Access to that specific feature.
Suggested Solution:
Our best practice recommendation is to enable regression features for the active phase then temporarily remove view access for the features testers shouldn’t see. That said, a better solution could potentially be designed, so don’t forget to create/update a SIP ticket.
Satisfaction ratings in another format other than 5 stars
What to check for:
Why the client wants satisfaction ratings in a different format.
Why:
Currently, we only offer 5 star ratings for satisfaction scores. Understanding the client’s pain and use case(s) will assist the product team in developing a functional and effective solution.
Suggested Solution:
Create/update a SIP ticket.
Test Plan isn’t cloned when creating a new project
What to check for:
Is the client able to create a test plan in XLSX format for use in future projects?
Why:
Having a saved project plan template means they can easily import that plan into their new projects.
Suggested Solution:
Educate the client on how they can fill out a test plan template in XLXS format then import that test plan. If that solution isn’t acceptable, gather as much information as you can about their pain and use case then create/update a SIP ticket.
“Set your start date in the future” Error
The customer is trying to adjust an active phase end date and they’re getting the error message “Set your start date in the future”.
What to check for:
Confirm if the customer has modified their timezones in the midst of their active project phases.
Why:
The timezone validation is potentially being ignored when adjusting current active phase dates.
Suggested Solution:
Create a CRAP ticket for the dev team to adjust the phase end date on the back end. Add the customer to the existing CON until the bug is resolved https://centercode.jira.com/browse/CON-22374