Issue | Ticket | Priority |
Comments |
Core changes | |||||||||||||
Beneficiaries and households > Individuals | View of the table goes beyond one page (need to scroll right) | Does any solution for that already exist in OpenIMIS Damian Borowiecki ? Limit inputs as a solution. | Wrapping text and setting max width for columns | ||||||||||
Suggest setting the default spacing so that it fits the screen. | It’s connected with the previous one - if we set a default spacing we should find the way to present the table where data are beyond that spacing. Limit inputs as a solution Andrea: one could not display it entirely, but it should be possible to copy and paste. also, it could be visualized in detailed page for example | Wrapping text and setting max width for columns | |||||||||||
Column size (width) should be adjustable |
| Could | Should user be able to change the width of the table? | ||||||||||
No maker-and-checker logic for deletion |
| Must | It’s blocked by tasks epic | ||||||||||
No validation on date of birth (should be restricted to prevent entering someone from the future) |
| Already fixed | |||||||||||
Save changes doesn't seem to be working |
| Must | |||||||||||
Social protection > Benefit plans | Requested description field not present |
| Must | Code Review stage. Should be included in 2nd sprint | |||||||||
Are the schema and json_ext fields freely editable? we might need maker and checker logic there |
Add ticket to hide schema for users with other roles than schema_admin. | Maker and checker will be added and it will not be freely editable. Schema_admin role is in the system and other users will not see this schema. | ||
Can you clarify the use of the "policy holder" field in this context? |
Damian Borowiecki, do we need that field? I think is was just used by mistake since we are using it openIMIS
Add ticket to remove policy holder field (or change field label/name). | We can remove policy holder for now. Should we add person who is responsible for a benefit plan? This was the aim of policy holder field. | ||||||||
The advanced filter button doesn't work |
|
Must
Addressed already. | |
I assume the default view would take into account the latest status, but please note that time period configuration fields should be included in the advanced filter, e.g. searching who had status "suspended" between date X and Y) |
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Add ticket to add data range to search criteria. | Currently we’re not able to search for historical data. We need to implement on a level of historical data. | ||||||||
Should be possible to select the beneficiaries from the list and get a detailed view (but currently, nothing happens) |
|
Addressed already. | ||
My profile | Cannot test the creation and editing of users |
Damian Borowiecki Dominika Bieńkowska It wasn’t in the requirements and we didn’t create a ticket for that yet. If I’m not mistaken, we settled that the users are going to be uploaded to the system by using openFN
https://coremis.s1.openimis.org/front/admin/users This table should be filtered. | |
Menu navigation bar | Most of the modules are not relevant. Let's kindly focus on a smaller deployment with menus contextual to the Social Protection use case |
I highly unrecommend that. The purpose of this project is to add Social Protection modules from CORE-MIS to OpenIMIS and not to create a CORE-MIS modules in python with openIMIS designs - to be confirmed at Deep Dive
Andrea: The design is modular and it should be possible to select relevant modules. In current cases, Cash transfer project will not be interested in Health insurance, and vice versa.
Add ticket to remove unnecessary items from meny. | We would adjust menu and remove items which are not relevant to Social Protection. | |||||||||||
Insuree enquiry" Search bar is showing, which doesn't seem relevant to the current use case |
| We will change the placeholder in a search bar. What we should search in this search bar? | ||||||||||
UI |
The idea is to create a version of the CORE-MIS in Python. Linked to the previous point, in order to ensure existing users don't get confused with the different interface, please allow view with a vertical menu bar (left side) and a different color scheme. | This is not the idea of the project. It has to be clarified |
. Confirmed in today’s call (13/6) it’s ok as proposed. It’s a core change. This can’t be in the scope of this MVP. | Yes | |||
replace openIMIS logo with CORE-MIS logo attached | Add ticket to change logo. | The combination of OpenIMIS and CORE-MIS is supposed to be a new system as discussed at the very beginning. This is to be confirmed with WB Team and Uwe. Confirmed in today’s call (13/6) it’s ok as proposed We can change logo. | ||
choice of bar (vertical or horizontal) as well as color scheme, name of platform and logos/photos should be configurable from the UI | Are we sure that users should have such customization possibilities? Dominika Bieńkowska Andrea: Confirmed in today’s call (13/6) it’s ok as proposed | Yes |