Editing Kotahi issues log

==Background==
This page acts as a working list to log and manage issues or feature requests related to [[Kotahi]].

==Issues==

Key:<br>
<span style="color:#0d0d0d; font-weight:bold;">{{#fas:pause fa-xl}}</span> - On hold/pending<br>
<span style="color:#ff8533; font-weight:bold;">{{#fas:circle-half-stroke fa-xl}}</span> - In progress<br>
<span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span> - Complete

{| class="wikitable sortable"
! ID||Type|| Owner || Domain || Description/comment || Action/status
|-
| 1|| QOL || WO || Client Exit || Can we use 'Share with whanau' to change service status for family members (via activity whose completion changes service status).
|-
| 2|| QOL || Data || Assigned users || Currently any action on a client record adds user as 'assigned user'. We want this to only show 'case manager', or otherwise some way to configure who gets added to the client.
|-
| 3|| QOL || Data || Accessibility || Dark or high contrast mode option needed.
|-
| 4|| QOL || WO || Tasks || Need 'filter by activity' and/or 'Service' || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 5|| Workflow design || Data || Pre-population || Whanau ora 'requisition approval' currently pre-populates data based on the workflow. This process BREAKS when a second requisition occurs for a client/family.<ref>In this scenario, the latest correct requisition request data does pre-populate correctly. However, it also confusingly pre-populates approval data from the last saved approval (which relates to a different requisition!).</ref>
|-
| 6|| Bug? || Data || Form builder|| Some 'zombie' fields previously deleted seem to persist and cannot be removed.<ref>Reproducible example needed.</ref>
|-
| 7|| QOL || FIN || Tasks || Need list of requisitions under each client. Solved by completion of #4 || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 8|| QOL || FIN || Tasks || Is task 'Whanau ora' or 'Tupaia'? Solved by completion of #4 || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 9|| Workflow design || FIN || Attachments || Attached files do not pre-populate || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 10|| QOL || FIN || Notifications || Multiple notifications per task/request, and no clarification of client/task in body.<ref>Personal information not sent in notification as a privacy measure.</ref>
|-
| 11|| QOL || Data || Backfill || Need a way to bulk import historical client notes || <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-half-stroke fa-xl}}</span>: Draft solution in testing (Feb 2025).
|-
| 12|| QOL || Data || SMS || Booked appt SMS reminders not currently working || <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-half-stroke fa-xl}}</span> Active with vendor. They are testing solution.
|-
| 13|| Workflow design || Data || Form builder || File upload/attachment prepopulation errors. || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 14|| QOL || Data || PRIMHD reporting || Query - PRIMHD reporting automation available?
|-
| 15|| Bug? || Data || Tasks || Multiple open tasks of same type make it confusing to 'clear' assigned tasks.<ref>Specifically, using 'Record activity' from a user task list does not necessarily (or ever) record the assigned task but a duplicate assigned to another person. Completion therefore does not remove assigned tasks from task list as expected.</ref>
|-
| 16|| QOL || Data || Form builder || Can we set generic fields (duration, staff present) to mandatory in configuration.
|-
| 17|| Feature || Data || General || Site 'white label' to add org logo and remove Kotahi branding. || <span style="color:#0d0d0d; font-weight:bold;">{{#fas:pause fa-xl}}</span>
|-
| 18|| Feature || Data || Configuration || Export services with child activities for sharing.<ref>Or library/store facility to pick up configs.</ref>
|-
| 19|| Feature || Data || Security || Force 2FA for all or selected users || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 20|| Feature || Data || Client || Address validation.<ref>On client add/update, and geo data available for mapping - meshblock, SA2, long/lat.</ref> || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 21|| Feature || Data || Form builder || Multiple select combo field.
|-
| 22|| Bug? || Data || Import data || Postal address should not be mandatory if PostalAddressIsSameAsResidential is true || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 23|| Bug? || Data || Import data || DOB should not require datetime value
|-
| 24|| Feature || Data || Import data || Assign service on client import
|-
| 25|| QOL || Data || Configuration || Bulk edit permissions.<ref>For example, adding all users to a new service or managing via 'roles'.</ref>
|-
| 26|| QOL || Data || Tasks || Client task list is confusing to manage if there are multiple tasks across different services, and the activity name does not indicate service.
|-
| 26|| Bug? || Data || Tasks || If a client has already received a requisition approval, submitting a new requisition pulls in details from the previous requisition instead of generating fresh data || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 27|| Data Quality || Data || Data Consistency || Records inserted before 13/1/2025 have filesourcekey = NULL due to manual entry before column existed. || '''Action''': Reupload data from before the 24th<br> '''Status''': <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 28|| Bug? || Data || Tasks || If a new requisition requests fewer services than the previous one, some details from the previous requisition are still carried over. || '''Action''': Notified as bug with details to Kotahi 19/2/25. '''Status''' <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 29|| Data Quality || Data || Data Consistency || Merge function updates kptinsertedat for '''all''' records, even for those that have not been updated. || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
| 30 || Functional || Appointments || Client Selection || Need ability to select staff members as the client when creating appointments. Currently, only clients can be selected, but staff need to be included as valid participants. || Raised to Karo. Current workaround is to use a test client as a proxy. Implementing staff-as-client functionality deemed too complex for current scope.
|-
|31
|QOL
|Group activities
|Scheduled group acivities
|Need the ability to schedule group activities to recur on the same day and time each week for a specified duration.
|-
|31
|QOL
|Activities
|Activities list
|Activities shared by clients family members arent prioritised so they are sent to the bottom of the list by default.
|}

{| class="wikitable sortable"
! Timeframe || Type || Description || Status
|-
| ASAP || Data || Data supply to S3 is daily || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
|  || Feature || Client attachments can be viewed directly from another activity
|-
|  || Feature || Dark mode/high contrast theme
|-
|  || Feature || PRIMHD reporting automation
|-
|  || Feature || Address validation || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
|  || Feature || Force 2FA || <span style="color:#33d17a; font-weight:bold;">{{#far:circle-check fa-xl}}</span>
|-
|  || Feature || 'Assigned user' configuration
|-
|  || Feature || 'Share with whanau' completes activity for each selection
|-
|  || Feature || Multi-select list field in form builder
|-
|  || Data || Import historical notes and files from Aiga
|-
|  || Data || Complete DW implementation
|-
|  || Data || BI products
|-
|  || Data || MVP of basic read/write API
|}

==References==

[[Category:Kotahi]]