-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/dref import template improvements #1434
Feature/dref import template improvements #1434
Conversation
🦋 Changeset detectedLatest commit: 20dfeb3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
e7a1f3e
to
7548545
Compare
7548545
to
8ffff5e
Compare
8d7b642
to
0d1f0cf
Compare
ANSWERS @udaynwa @anamariaescobar @tovari QuestionsOperation Overview
Event Detail
Actions Needs
Operations
Timeframe and Contacts
|
cd1c8e2
to
d55f2da
Compare
- Update styling of the export - Headers and description - Add support for rich text on label and description - Hide options sheet - Rename 'headingType' to 'rowType' - Append 4 new lines on text area to set initial height but also expand on content
- Add description mapping for ns actions and needs identified - Hide operational timeframes heading - Hide indicators heading
- Move generateTemplate to utils - Make optionsMap and context optional for parseRichText
- Removed obsolete comments - Add descriptions for risk and mitigation section
d55f2da
to
20dfeb3
Compare
Thank you for the answers, @marcovvu1 . They were implemented and pushed to Staging in the go-web-app v7.6.2 Staging deployment yesterday. However, we would like to note a few points: Missing / to be implemented
(We will implement and push these 2 in the next Prod release) Questions
|
Update @marcovvu1 , the Missing / to-be-implemented ones have been implemented and pushed to Staging with go-web-app v7.6.3 just now. cc @tnagorra |
Thanks @udaynwa, on your two questions. Agree with the proposed guidance for the questions that cascade On the second point, yes indeed, that long text field should be available in the import template. |
Addresses:
Issues
Changes
on content
Template Documents
Generated template: DREF_Application_Response_import_template_25_10_2024,_16_08_46.xlsxGenerated template: DREF_Application_Response_import_template_28_10_2024,_15_09_23.xlsxGenerated template: DREF_Application_Response_import_template_29_10_2024,_16_42_36.xlsxThis PR doesn't introduce:
console.log
meant for debuggingQuestions
Operation Overview
Event Detail
Actions Needs
Operations
Timeframe and Contacts