Basecamp Export

From the list: Migrating provision lists from legacy ISLG

✔ High Priority: BIT/1377 (7-June-2021)

Irit W. added this on Jun 08, 2021
Completed Jun 09, 2021 by Irit W.

Assigned to: Akash B. Jitesh D.
Notes: Hi Akash

This is High Priority. We need this complete for tomorrow, June 8th:

BIT/1377 PDF and HTML was uploaded to app.islg today.
The provision list needs to be migrated from legacy to app.islg. You can delete the current provision list that is currently on app.islg before migrating the list from legacy. You can see the provision lists as shown below.

https://www.investorstatelawguide.com/CoreComponents/AddDocumentStep2Case1and2?docId=13507

image.png 31.3 KB • Download

Thank you,
Irit

cc Nafiseh
cc Martin

Comments & Events

Akash Buch

Irit

This file is migrated to app.islg, Please verify

Thanks,
Akash

Jun 08, 2021 at 8:11 AM Notified 4 people

Harsh Parikh, Tech Lead

Irit

Nafiseh

and

Paul

,

If you want to migrate Provisions from old legacy application to app.islg then please let know to

Harsh

and

Piyush

on ISLGRebuild group.

Jun 08, 2021 at 9:34 AM Notified 8 people

Paul Moon

Harsh

:

By ISLGRebuild group, do you mean integrate any request into the sprints that

Martin

manages or do you mean post these requests elsewhere within Basecamp?

Please specify where

Irit

should post these request to you and

Piyush

.

Thanks,

Paul

Jun 08, 2021 at 4:29 PM Notified 7 people

Irit Weinfeld

Thank you,

Akash

Nafiseh

, BIT/1377 has been migrated.

Irit

Jun 08, 2021 at 9:28 PM Notified 7 people

Harsh Parikh, Tech Lead

Paul

and

Irit

,

if it is an high-priority item then you will post in basecamp and address me and Piyush.

But, if it is not a high-priority item then you can request to Martin to add in sprint.

Jun 09, 2021 at 5:00 AM Notified 7 people

Martin Laporte, CTO

Paul

and

Irit

,

Can you help me understand what you would perceive as an acceptable turnaround for a regular priority request?

Thanks,
--Martin

Jun 09, 2021 at 2:41 PM Notified 7 people

Irit Weinfeld

Martin

,

A turnaround time of 1 to 2 days for a high priority request is acceptable. If I have an especially important request like this one above, then I provide a target deadline.

Thanks,
Irit

Jun 09, 2021 at 3:19 PM Notified 7 people

Martin Laporte, CTO

Irit

,

What about regular requests? Would waiting up to 3 weeks (length of sprint) be acceptable?
If waiting 3 weeks is too long, then I believe we should stick with one process, regardless of its urgency.

Thanks,
--Martin

Jun 09, 2021 at 3:30 PM Notified 7 people

Irit Weinfeld

Martin

,

Good question. If it's not a priority item, the deadline really depends on the type of request. I usually provide a target deadline for non-priority items as well. For some, it's 1 to 3 days. Other times, it could wait a week or two.
(For most items, 3 weeks would be too long).
For example,

The Daily HTML QC list, the turnaround time request is usually 1 day.
For Problems with Completed HTML documents, the turnaround time request is usually 1 to 2 days. If the issue is more complicated, it could take a week.
Migrating provision lists from legacy ISLG, the turnaround time could take 1 to 3 days.

Jun 09, 2021 at 4:58 PM Notified 7 people

Martin Laporte, CTO

Irit

,

Thank you, this is helpful.
In that case, let's keep the process as-is for all requests.

You log the request in Basecamp, and tag the appropriate resources
Dev team creates a Task under the "Unplanned/Critical Issues" sprint backlog item in DevOps
Once complete, Dev team reports back in Basecamp

Harsh

and

Jitesh

: as we go through a few sprints, let's track our time spent on these requests so we can allocate the right amount of hours to our "Unplanned/Critical Issues" sprint backlog item moving forward.

CC:

Morgan

Jun 09, 2021 at 5:32 PM Notified 7 people

Irit Weinfeld completed this to-do.

Jun 09, 2021 at 7:38 PM