| Agenda Items |
---|
1 | Overview of last three months: Tip |
---|
Last Quarter 🆕 x 2740 x 5660
|
Released Development in last 3 months Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-3713 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-3910 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-3316 |
---|
|
🆕 risr/ Risr integration |
2 | Roadmap Items:- Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-3691 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-3778 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-3356 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | EP-4112 |
---|
|
|
3 | Development for Discussion ESFA Submission (Former Ace 360 customers) liked the auto-submission to the ESFA, we would like feedback on speeding up the process (but without auto-submission as likely to be many conditions where they wouldn't want to auto-submit Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-7615 |
---|
|
We would like to know what your opinion and thoughts are around CRM like the addition of “CRM like” functionality to track the critical path for the apprentice , such as comms, emails, follow ups etc
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-8341 |
---|
|
We would like to know, should you be accepting a booking , if you don't have an EPA for it? Who needs to know about rejections? Possibly looking at an In app App version of the Digest Email -e.g. group together xx number of rejected EPA’s in xx period of time?
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-8006 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | a2269739-3244-3b4d-bb8f-c582148d7bba |
---|
key | SD-8117 |
---|
|
If we added a new step between QA published and results released and an apprentice was put into retake review the provider wouldn't be aware of why as they would not be aware of the result. Should we therefore look at moving the trigger in Retake Review to be at the point the result is made available rather than the QA being published? Would this be mainly something you would use for component results rather than certification? Would an alternative be to have a bulk publish QA’s screen?
|
4 | epaPRO Assess Demonstration |
5 | AdditionallyAOB? | 5 | |
6 | AOB? |
7 | Reminders |