You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are updating the process for reporting an issue on the platform with a view to making it more straightforward for users by providing more and clearer options, at the same time exerting tighter control over the Slack channel. Due to our Pro subscription on Slack, we will need to migrate the issues channel across to the jac-community channel, which is our general channel. We can control the settings there so that only Admins/channel managers can create posts, but all users can reply in the thread. We are also looking at automating the Developer rota in Slack, so that whomever is on duty will be automatically assigned to the ticket raised.
Note: once all is up and running, the new system will be demoed at Show & Tell and a new user guidance video produced.
User Story
As the Digital team, I would like to improve the Report an issue process so that it is easier to use for Admins and more tightly controlled for ourselves.
Benefit(s) to user (if not already clear from User story)
Slack thread is clearer and it is easier to monitor, track and complete issues
Ask a question provides a quick option for Admins to get a quick response to sthg simple
Ticket assignment is automated
Feature(s) Description
Set up Slack API to support the changes to the form on the Digital Platform described here
Options 1 and 2 create a GH/ZH ticket and an alert in the Slack channel
The developer on duty according to the issues channel rota is automatically assigned to the ticket and an alert of the assignee is broadcast to the Slack channel (it would be great if this appeared in the thread under the issue alert!)
Option 3 creates only a thread in the Slack channel
In the case of option 3, the thread is assigned to Nick and Frances
NOTE: tests should initially be undertaken on the new channel before we link the Live environment up to the new Slack channel as we will need to communicate this change to users.
Acceptance Criteria
It's done when:
Admins can report an issue for themselves by completing a dedicated form; this creates a GH/ZH ticket, raises an alert in the new Slack channel and the developer on duty is automatically assigned to the ticket and an alert posted in the thread
Admins can report an issue for another user (Candidate, Assessor, Panellist) by completing a dedicated form; this creates a GH/ZH ticket, raises an alert in the new Slack channel and the developer on duty is automatically assigned to the ticket and an alert posted in the thread
Admins can ask a question; this does not create a ticket, but it creates a post in the Slack channel which is automatically assigned to Nick and Frances.
Definition of Done
User stories/acceptance criteria met
Internal reviews passed (feedback actioned)
User testing passed
Relevant technical documentation updated
User guidance updated
Deployed and merged without errors
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion
Nick
The text was updated successfully, but these errors were encountered:
Background
We are updating the process for reporting an issue on the platform with a view to making it more straightforward for users by providing more and clearer options, at the same time exerting tighter control over the Slack channel. Due to our Pro subscription on Slack, we will need to migrate the issues channel across to the jac-community channel, which is our general channel. We can control the settings there so that only Admins/channel managers can create posts, but all users can reply in the thread. We are also looking at automating the Developer rota in Slack, so that whomever is on duty will be automatically assigned to the ticket raised.
Note: once all is up and running, the new system will be demoed at Show & Tell and a new user guidance video produced.
User Story
As the Digital team, I would like to improve the Report an issue process so that it is easier to use for Admins and more tightly controlled for ourselves.
Benefit(s) to user (if not already clear from User story)
Feature(s) Description
NOTE: tests should initially be undertaken on the new channel before we link the Live environment up to the new Slack channel as we will need to communicate this change to users.
Acceptance Criteria
It's done when:
Definition of Done
User Testing Steps
Specify for users what is being tested (but not how to test it.)
Feature Champion
Nick
The text was updated successfully, but these errors were encountered: