medic/cht-core

Describe the issue When releasing a new version of cht-core, there is a series of manual steps the release engineer must perform to upgrade the demo instance. Besides just being more manual effort, these steps also require that the engineer has a working local environment setup for running things like kubectl and helm (things not normally required for CHT development). Also, the engineer has to have the proper access level for the demo-cht namespace on EKS (something unlikely to be granted to non-Medic engineers). Describe the improvement you'd like Unless I am missing something, we should be able to automate all of this via a new GitHub workflow that we can manually trigger against a specified tag. (Another option would be to do it as a new job in the build workflow that is triggered _for when upgrade completes`. The main challenge I see with that is we don't want to upgrade the demo instance for all tags, since that could cause downgrades when we publish new patches for older rele

Describe the bug Unable to hide individual form fields inside a repeat in the reports view. To Reproduce Steps to reproduce the behavior: Add a repeat to your app form Add some fields (questions) inside the repeat Add a column instance::tag and set it to hidden for some of the fields added in step 2 Convert and upload the app to CHT Submit a report using that form Check the report in the Reports tab All fields inside repeat are visible Expected behavior The fields inside repeat which have been tagged as hidden should not be visible. Screenshots Here is a sample XLSForm repeat survey: repeat.properties.json: { "title": [ { "locale": "en", "content": "Repeat" } ], "context": { "place": true, "person": true }, "icon": "icon-repeat", "hidden_fields": [ "hidden_props", "items.hidden_props" ] } After I fill the form, I can still see the fields that should have been hidden: Environment Instance: local Browser: Chrome Client platform: Wind

As an extension to this feature, we would like to see the uploaded image displayed on the client's profile and also be able to change the image in person-edit form.

Is your feature request related to a problem? Please describe. Requested on the forum. Currently CHT Targets and UHC counts are collected and stored per user per Gregorian calendar month. It is possible to customize the day of the month that target collection begins/ends by setting the uhc.visit_count.month_start_date value in the settings. This allows for adjusting target collection to be based on the nth day of the month instead of the 1st, but this value is bound to the day of the Gregorian calendar month. In regions that use the Bikram Sambat calendar, reporting cycles may be tied to BS months and not Gregorian months. In this case we would want the Target/UHC counts to reset at the beginning of the BS month (or in a fixed interval of days from the beginning of the BS month). Describe the solution you'd like We should add configuration that would allow aligning the Target/UHC counts to reset at the beginning of the BS month instead of the Gregorian calendar month. @bhishankc a key

Add the constant in DOC_TYPES Good first issue This ticket has the Good first issue label! This means it's been especially curated by other CHT contributors to be easy to work on for first time contributors per the docs. To succeed on this ticket, please follow the detailed steps in the parent ticket. This is largely a search and replace effort, but it's a great way to get introduced to working in GitHub, opening PRs and learning the basics of CHT Core dev setup.