ISL Admin UI

[RevantCI]

CRUD verse markers from ISL bible screen

Use the ISL Bible page and in the Data column allow the user to upload the csv files as per the CRUD API calls
See screenshots from ISL Admin UI
Upload button can be more noticeable and we can upload csv file directly or zip

SP 4

Development

• - Check and update the existing table layout, column for handling or showing video id and verse marker - (ET - 2 hours) - (ATT - 2.5 hours)
• - Implement bulk upload select feature for verse marker upload - (ET - 4 hours) - (ATT - 3 hours)
• - Implement view verse marker dialog - (ET - 3 hours) - (ATT - 4 hours)
• - Check for crud functionalities - (ET - 1 hour) - (ATT - 1.5 hour)
• - Unit testing - (ET - 1 hour) - (ATT - 1 hour)
• - Code review - (ET - 2 hour)
• - Review changes - (ET - 1 hour)

QA

• Write testcase - Jesni(ET:30 mins)(ATT : 30 mins)
• Reviewing testcase- Revant (ET:10 mins)(ATT : 15mins )
• Testing - Jesni(ET: 1hr)(ATT : 1.5 hrs )
• Reviewing Testing - Seema (ET: 15 mins)(ATT : 15 mins)

[JesniJ]

Test Result

Verified the ISL Admin UI – CRUD Verse Markers functionality from the ISL Bible screen. Upload functionality for CSV/ZIP files and CRUD operations are generally working as expected.

Issues Noted:

• Deleting an ISL Bible resource is failing and showing a network error.
• Inside the Data search filter, the search behavior is not working as expected. Search results should prioritize book names starting with the entered value (e.g., typing Ge or Ti should first show matching book names like Genesis or Titus).

Moving the issue to in-progress

Note:

1. Regarding 1st point, it's a bug from backend side means if a resource has some data, then, it's unable to delete the resource. (Please verify in swagger for that resourceId)

@RevantCI

[RevantCI]

1. This is not working from the swagger itself , please check with @AthulyaMS about the error its not showing up in the errror logs or audit logs also. its fiailing silently which is not good.
   note resourceId which has issue
   {
   "resource_ids": [
   228
   ]
   }
2. this point we can skip for now, if we put the full book name we can get it.
   Sorting was not part of the issue specificaion so its not requried.

[JesniJ]

Moving the issue to done with dev team's comments .

[JesniJ]

Verified that the delete issue has been fixed and now users able to delete the resources.