Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

To limit the visibility of characters.

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.

To limit the visibility of characters.

Column size (width) should be adjustable

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-130

Could

Should user be able to change the width of the table? - Yes

It needs to be done on the core level.

No maker-and-checker logic for deletion

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-131

Must

It’s blocked by tasks epic

No validation on date of birth (should be restricted to prevent entering someone from the future)

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-24

Already fixed

Save changes doesn't seem to be working

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-134

Must

Social protection > Benefit plans

Requested description field not present

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-99

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 thereAdd ticket to hide schema for users with other roles than schema_admin.

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-195

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?Add ticket to remove policy holder field (or change field label/name).

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-197

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.

We should change the name of this field to Institution and change it to text field.

The advanced filter button doesn't work

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-71

Addressed already.

There should be possibility to search for how many active programs one beneficiary have.

Are there any beneficiaries who have more than one active program?

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)Add ticket to add data range to search criteria.

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-198

Currently we’re not able to search for historical data. We need to implement on a level of historical data.

Not sure if we’re able to implement it in the MVP and the first phase. We need to check how long time it would take.

Is it possible to import historical data? To discuss with the team. It’s possible. Confirmed with the Team. It should take 3-4MD to add this funcionality

Should be possible to select the beneficiaries from the list and get a detailed view (but currently, nothing happens)

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-111

Addressed already.

My profile

Cannot test the creation and editing of users

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 caseAdd ticket to remove unnecessary items from meny.

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-199

We would adjust menu and remove items which are not relevant to Social Protection.

Can we add a role in a frontend and configure its rights to only see the modules that are relevant to this role? Preferably from the frontend.

Insuree enquiry" Search bar is showing, which doesn't seem relevant to the current use case

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-135

We will change the placeholder in a search bar. What we should search in this search bar?

Individual - ask the team if we can search by other criteria?

Help

Maybe in the furute we could use search bar as a guide for user - to easily indicate areas in the system like if user types in “Benefit plan” then the menu item is highlighted

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.

Andrea: Clarifying that I didn’t mean for it to be a standalone solution. It clearly would be compatible with openIMIS (that’s the idea of the merger). But we need to make sure existing and future users can adopt and configure the platform as needed

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.

It’s significant to have a different navigation on the left side as well as different color scheme.

Yes

replace openIMIS logo with CORE-MIS logo attached Add ticket to change logo.

Jira Legacy
serverSystem JIRA
serverId97d38f4a-4cd9-3563-900d-60c9290b47f4
keyCM-200

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.

Andrea: the branding aspect is being discussed, but for now the SP modules are presented as CORE-MIS, so I think it would make sense to present it as suggested. As long as it possible to customize color scheme, logo and name than we can easily modify it as needed (see point below)

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:
This can be a right that admin has. Normally it would be configured at set up and possibly modified later (don’t think it would be frequent, but better to have it as an option).

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