Scope 5.1 Developments #22
Replies: 7 comments
-
Hi @pallakartheekreddy @surendrasinghs please review the above functional & tech approach and let us know if any changes need to be done. We would also need your help identifying any other building blocks that would be used in the above developments. Thanks |
Beta Was this translation helpful? Give feedback.
-
@sanyapawah @tarang27 Thank you for sharing this. Please see my responses in-line.
Commented on the Confluence.
Please share the implementation details. Commented on the JIRA ticket for the same.
I believe this is a solution & tech design item and no development is planned for this.
I believe this is a solution design item and no development is planned for this.
Please share the implementation details. Commented on the PRD/Google Doc for the same.
Please share the implementation details. Commented on the JIRA ticket for the same.
Please share the implementation details. Commented on the JIRA ticket for the same.
Are these defined already? Please plan them as per the release calendar.
Please share the implementation details. Commented on the JIRA ticket for the same.
Please share the implementation details. Commented on the JIRA ticket for the same.
Looks good. Few general observations and requests
|
Beta Was this translation helpful? Give feedback.
-
Can you please plan to resolve bugs and defects from this list of tickets? I have filtered for relevant tickets related to your contributions. |
Beta Was this translation helpful? Give feedback.
-
@surendrasinghs @pallakartheekreddy @tarang27 adding the latest discussed approaches discussed for the above listed 5.1 scope use cases and bugs : Use Case : Admin controlled reminders/nudges sent to creators & reviewers -PRD | #15 | JIRA Bug: Send back for corrections button not working correctly - JIRA |
Beta Was this translation helpful? Give feedback.
-
Hi @surendrasinghs @pallakartheekreddy |
Beta Was this translation helpful? Give feedback.
-
Signed off in CoKreat Rel 5.1.0 Signed off in CoKreat Rel 5.0.3 Use Case : Bulk Approve button to be added in QuML 1.0 - JIRA Use Case : Print preview: Document generated as printout should be easily editable - PRD Bug : Content type under My Projects to be corrected for Q.set - JIRA Bug : Bulk approval not working for Questions added from Library - QuML 0.5 - JIRA UI/UX enhancements on current use cases/features Bug : Duplicate delay handling - JIRA Bug : Send back for corrections button not working correctly - JIRA Use Case : Send back for corrections button to be removed for questions added from Library - JIRA |
Beta Was this translation helpful? Give feedback.
-
Signed off : CoKreat Rel 5.1 Signed off : CoKreat Rel 5.0.3 In progress In progress Signed off : CoKreat Rel 5.0.3 Closed Signed off : CoKreat Rel 5.0.3 In progress |
Beta Was this translation helpful? Give feedback.
-
This is the finalised 5.1 scope for Prashnavali including critical use cases and bugs.
5.1 Items
Use Case : Admin controlled reminders/nudges sent to creators & reviewers -PRD | Github | JIRA
Use Case : Question type column to be added in QuML 1.0 - JIRA
Use Case : Bulk Approve button to be added in QuML 1.0 - JIRA
Use Case : Print preview: Document generated as printout should be easily editable - PRD
Bug : Content type under My Projects to be corrected for Q.set - JIRA
Bug : Bulk approval not working for Questions added from Library - QuML 0.5 - JIRA
UI/UX enhancements on current use cases/features
Bug : Duplicate delay handling - JIRA
Bug : Send back for corrections button not working correctly - JIRA
Use Case : Send back for corrections button to be removed for questions added from Library - JIRA
CC : @surendrasinghs @pallakartheekreddy
Please review the approach for the above finalised scope. We will commence the developments accordingly.
Beta Was this translation helpful? Give feedback.
All reactions