Hi Melissa and Savannah ,

Based on conversations we've had in the past about how to deal with post-development feedback on the performance of the applications, I've created this to-do group for the ISLG team to submit their feedback on issues they experience with the new application after it is completed on March 15th. 

The idea is that any issues we encounter would be reported in to-do's (along with detailed descriptions, including URLs, screenshots and videos), and then you would take that feedback and log bugs in TargetProcess for resolution by DevIT.

Let me know if this sounds like the appropriate way to proceed, and I'll create an equivalent to-do list in the ILG project.

Note that we're currently planning to perform intensive testing of ILG March 1-15 and ISLG March 15-31. That way we can start the ILG subject-matter trial on March 16th, and start the ISLG migration/sync process on April 1st.

Thanks,

Morgan

Melissa  

Yes, this will work well for us for both ISLG and ILG. 

We'll plan to dedicate resources to this during the windows you'vre outlined above. 

Mel

Perfect. Thanks Melissa . Hopefully the feedback is minimal.

Morgan 

Hi Melissa , Ketan , Harsh and Jitesh ,

I did a few hours of testing on the admin site this evening, and found a number of problems with the meta fields managements pages that need to be resolved for me to build out the appropriate forms for all the master lists. I will continue my testing tomorrow, but please ensure these issues are addresses as soon as possible, because it will cause delays in us beginning the migration process.

In one of the to-do's I've requested that we integrate all the hard coded fields into the meta-field management page so that admin users can keep track of what fields are available, and reorder all fields within the form: Can't see hard coded fields in meta-field management page - TOLOGIX - ISLG App Rebuild. Harsh and Jitesh , how difficult would it be to implement this change? I'm conscious of our deadlines, and do not want to introduce major changes at this point, but it would be significantly easier to build out the master list forms if I could see all the fields in the meta field management page.

Also, did we wipe all testing data from the system? I noticed a number of unassigned lists and meta fields sets. Could we please ensure all this data is cleaned from the system.
 
Thanks,

Morgan 

OK Morgan . Lets discuss this thing in today's call and also, we updated the hard coded fields many time in dispute and some other masters. 

i insisit if we get the one final spread sheet of hard coded fields of all masters so we can again remove all unnecessary data and list and add all hard coded field once again.

Hi everyone,

I had a call with Ketan and Savannah this morning, and I understand Melissa , Harsh and Jitesh also discussed the issue earlier as well. 

I'm going to hold off on further testing of the ISLG admin site until a solution to some of these issues is proposed. However, let's ensure we treat this as a high priority so that we can get these forms built by the end of the week, so that we can start the data migration. 

I am available for a call between 6:15am and 7:45am tomorrow to discuss the hard coded fields.

Thanks,

Morgan

Hi Morgan ​,

We are available to discuss the hard coded fields today 6:15 AM.

Ok. Great. Thanks Harsh ​. Would 645am work?

I'll send a calendar invite.

Morgan

I've sent a calendar invite for 6:30am Vancouver time. Melissa , I've include you as well so that we can discuss the different options for dealing with the issues discussed here: Re: Can't see hard coded fields in meta-field management page - TOLOGIX - ISLG App Rebuild, but if you can't make it, I'll discuss with Harsh , Jitesh and Ketan , and update you.

Morgan

Hello Ketan , Harsh , Jitesh , Melissa and Naomi ,

I've completed my first round of testing and posted a number of to-do's above. To-do's that I think need immediate attention, because they will affect the migration have been assigned to Harsh and Jitesh (as well as Melissa and Naomi ). The rest may not be as urgent, but please review to assess.

I was able to test and build forms for all the master lists (pending resolution of some issue in the to-do's). I haven't had a chance to build the Legal Analytics forms. I'll start on these tomorrow.

Thanks,

Morgan

 

Hi Morgan ,

We are taking this feedback as high priority and started work on the feedback which assigned to me or Jitesh.

Hope this is fine.

Hi Morgan ​,

Could you please seprate the priority feedback? so we can look into those feedback first.

Ok. Harsh . I'll review each to-do, and mark each with "HIGH PRIORITY" that need to be addressed right away.

Morgan

Hi Harsh ,

I've marked all the to-do's that are high priority. Note that the to-do's related to "add to group" may be because I'm misunderstanding the requirements:

Problem with "add to group" function in Treaties and Arbitration rules - HIGH PRIORITY - TOLOGIX - ISLG App Rebuild
Problem with adding PDF and/or HTML after creating record in Dispute Document, Arbitration Rules ... - TOLOGIX - ISLG App Rebuild

Melissa and Naomi , could you please confirm, and I can update their priority status. Also, for the high priority items, should we log user stories in TargetProcess, or just deal with them directly in the to-do's?

Thanks,

Morgan 

Morgan ,

I will take a look at the above two issues and respond in their respective to do pages.

I have only been logging issues regarding the non-high priority items, as I believe Harsh and his team can implement the high-priority items immediately from here.

Thanks, 

Naomi

Perfect. Thanks Naomi .

Morgan 

Hello all,

I have moved all the to-do's above into appropriate priority groups. All to-do's in ISLG Team Feedback - Fix Now - TOLOGIX - ISLG App Rebuild should be resolved as soon as possible. All to-do's in ISLG Team Feedback - Fix Later - TOLOGIX - ISLG App Rebuild can be resolved in Phase 4.

Thanks,

Morgan

Hi everyone,

Based on testing performed by Irit , Paul and myself over the past few weeks, we've generated a number of to-do's about the ISLG admin site. Given the volume of to-do's, Ketan and Savannah , could you please give these a cursory review, and then we can discuss how we'll triage and integrate these into the development pipeline.

Thanks,

Morgan

Hello everyone,

Note that I've started to reorganize the ISLG Team Feedback to-do's. I've created the following groups:

Ketan , for planning purposes we should be including all applicable users stories for to-do groups 2, 3 and 4. However, let's ensure we distinguish between the groups so that we can postpone user stories to post-launch as required. Note that there are still a number to-do's in group 1 that need to be triaged by Naomi and Melissa , which will be transferred into groups 2-5 accordingly.

Thanks,

Morgan

Hello everyone,

Note that I am starting to add to-do's to this group again as we come across issues that we're seeing in the Subscriber site. Paul , Nafiseh , Irit and I are will start testing the site more intensively at the beginning of next month, but to-do's may be posted as issues are discovered over the next few weeks.

Melissa and Naomi , could you please triage these to-do's an create user stories in TargetProcess as required. Unless specified otherwise, assume that all the to-do's above need to be resolved before the application is launched in January and this should be put directly into the backlog.

Ketan , please take note from a workflow planning perspective.

Thanks,

Morgan

 

Hi Savannah ,

Following-up on my comment above, could you please ensure triaging the to-do's above starts this week. Note that all applicable user stories required before launch should be inserted directly into Backlog status in TargetProcess, and all post-launch users stories can be put into Open status.

Thanks,

Morgan

Hi Morgan , 

Yes, I reminded the team and will make sure triaging starts this week. 

Savannah

Hi everyone,

All the to-do's above have been moved into other to-do categories based on their priorities:

Thanks,

Morgan