Basecamp Export

Paul Moon

Hi

Martin

:

Please add this item to unplanned/critical task today. As shown in the video below, the notice that used to be present on app.islg is missing now. You can still see it on staging.islg.

Thanks,

Paul

Dec 20, 2021 at 7:12 PM Notified 1 person

Martin Laporte, CTO

Hi

Harsh

,

Please investigate this issue on app.islg.
Can you let us know why that feature is now missing?

Thanks,
--Martin

Dec 20, 2021 at 7:14 PM Notified 2 people

Harsh Parikh, Tech Lead

Hi

Paul

,

The data are different in staging and app.islg. We checked and found that following 2 UIN's are in same proceeding (Judicial Review) stage in app.islg.

IC/0404/04
IC/0404/05

As per criteria, if same dispute's both document have same proceeding stage then we are not displaying Notice message.

In Staging.islg, We have only one document IC/0404/04 has proceeding stage. Hence, The Notice message display in staging.

Please Let us know if you have any concern.

Cc :

Martin

Dec 21, 2021 at 7:30 AM Notified 2 people

Paul Moon

Hi

Harsh

:

Based on your description, the current ISLG criteria are wrong. Any UIN entered under the Related Document(s) field should trigger the notice, even if they are of the same category (e.g., Decision of Reviewing Court).

Martin

: is this an easy fix or do we need a new user story?

Thanks,

Paul

Dec 22, 2021 at 12:41 AM Notified 3 people

Piyush Kanpariya

Hi

Paul

,

This issue is resolved on app.islg. Please check and confirm.

cc:

Harsh

Martin

Dec 22, 2021 at 12:58 PM Notified 4 people

Paul Moon

Hi

Piyush

:

The specific example of IC/0404 documents is resolved, but there seems to be an issue with other documents/disputes. For example, AF/0040/24 and AF/0040/25 in the video show the notice when there is no Related Document(s) entry added on the admin site. The notice shouldn't appear.

Martin

: let me know if you want to complete this item and post AF/0040 issue as a separate issue.

Thanks,

Paul

Dec 22, 2021 at 7:40 PM Notified 4 people

Harsh Parikh, Tech Lead

Hi

Paul

and

Martin

,

The label = *Notice message is displaying as per following criteria.

It is checking either or Related Dispute Document Field or Proceeding Stage field.

The label will appear based on a dispute document existing with the same dispute in the dispute field + a proceeding stage later than the selected value in the 'Proceeding stage' field of the current document OR
The label will appear if there is data in the 'Related documents' field on the dispute document master list record

Following is the user story and basecamp thread for criteria which we developed.

https://industrialagency.tpondemand.com/restui/board.aspx#page=bug/21085
https://3.basecamp.com/3691577/buckets/5559242/todos/3375549045

Let me know if you have any concern.

Dec 24, 2021 at 5:19 AM Notified 4 people

Paul Moon

Hi

Harsh

:

Based on your explanation above, please let me know which category AF/0040/24 and 25 fall under the above two scenarios. If it is the first one (The label will appear based on a dispute document existing with the same dispute in the dispute field + a proceeding stage later than the selected value in the 'Proceeding stage' field of the current document), we may have to modify the criteria as they do not correctly represent the requirements.

Thanks,

Paul

Dec 30, 2021 at 12:21 AM Notified 4 people

Harsh Parikh, Tech Lead

Hi

Paul

,

AF/0040/24 and AF/0040/25 both are following under First Scenario. Following one.

The label will appear based on a dispute document existing with the same dispute in the dispute field + a proceeding stage later than the selected value in the 'Proceeding stage' field of the current document

Dec 30, 2021 at 12:00 PM Notified 4 people

Paul Moon

Hi

Harsh

:

There was an oversight in the original requirements. We will have to revise them and implement new requirements to correctly reflect when the notice appears.

Martin

: is this something you and I could work on or do we need to involve Industrial?

Thanks,

Paul

Dec 31, 2021 at 12:58 AM Notified 4 people

Martin Laporte, CTO

Hi

Paul

,

I suggest we work with Industrial to revise the requirement, especially since they were the original authors of the user story.

Thanks,
--Martin

Jan 04, 2022 at 12:45 PM Notified 4 people

Paul Moon

Hi

Martin

:

I haven’t decided yet, but what if we get rid of the first criterion below and have the notice appear only if there are related documents filled out (second criterion)? Could this be a solution to change the requirements sans engaging Industrial?

image001.png 54.2 KB • Download

Please let me know.

Thanks,

Paul

Jan 05, 2022 at 11:11 PM Notified 5 people

Martin Laporte, CTO

Hi

Paul

,

Removing the first criterion might be the simplest approach, but do we know why it was included in the user story in the first place? If not, it might be good to have a quick chat with Naomi to find out.

Thanks,
--Martin

Jan 06, 2022 at 12:50 PM Notified 5 people

Paul Moon

Hi

Martin

:

After consulting with

Nafiseh

, we will leave the current criteria as they are and simply change the text of the notice (adding "may affect or" below) in order to accommodate how the live site generates the notice.

Could you have DevIT change the notice as follows:

*Notice
See other documents and proceedings that may affect or may have affected the findings in this decision or award.

Naomi

: we will not need a revised user story for the time being.

Thanks,

Paul

Jan 11, 2022 at 9:05 PM Notified 6 people

Martin Laporte, CTO

Hi

Piyush

,

Per

Paul

's message directly above, can you make this quick change in our code and log this as a new task under "unplanned issues"?

The new message should read:

*Notice
See other documents and proceedings that may affect or may have affected the findings in this decision or award.

Thanks,
-Martin

CC:

Harsh

Jan 11, 2022 at 9:18 PM Notified 6 people

Piyush Kanpariya

Hi

Paul

,

The above change is done on app.islg and staging. islg. Please check and confirm.

https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/1375

cc:

Martin

Harsh

Jan 12, 2022 at 8:26 AM Notified 6 people

Paul Moon

Great. Thanks,

Piyush

.

Paul

Jan 12, 2022 at 5:28 PM Notified 6 people

Paul Moon completed this to-do.

Jan 12, 2022 at 5:28 PM

Paul Moon re-opened this to-do.

Jan 25, 2022 at 1:41 AM

Paul Moon

Hi

Harsh

:

Below you mentioned that the notice will appear in either case

image.png 100 KB • Download

If there are two subsequent documents that are in the same proceeding stage (e.g., Judicial Review), but an admin user manually tags both documents as related documents (second criterion above), shouldn't it display the notice anyway?

Please let me know.

Thanks,

Paul

Jan 25, 2022 at 1:48 AM Notified 6 people

Harsh Parikh, Tech Lead

Yes

Paul

. In this scenario the notice is display.

Jan 25, 2022 at 9:33 AM Notified 6 people

Paul Moon

Hi

Harsh

:

In the example below (IC/0275 documents), I still do not see the notice when I expect to see it based on the following.

image.png 29 KB • Download

Notice see other documents (25-Jan-22).mp4 9.25 MB • Download

Can you explain why?

Martin

: let me know how we should proceed with DevOps (other re-opening or starting a new item).

Thanks,

Paul

Jan 26, 2022 at 1:13 AM Notified 6 people

Harsh Parikh, Tech Lead

Hi

Paul

,

We checked and we are able to see the notice message. Actually, We are displaying notice message through SQL Job which is running every night.

Once you entered the data then next day you can able to see notice message.

image.png 231 KB • Download

Cc :

Martin

Jan 27, 2022 at 12:29 PM Notified 6 people

Paul Moon

Ok,

Harsh

. I assume the issue was related to Re: Disputes & Dispute Documents search field and filters not working - TOLOGIX - ISLG App Rebuild with no proper SQL indexing in the last few days?

Please confirm before I mark this complete.

Thank you,

Paul

Jan 27, 2022 at 6:12 PM Notified 6 people

Paul Moon

Hi

Harsh

:

Please answer my question above before I can mark this complete, thanks.

Paul

Mar 16, 2022 at 6:10 PM Notified 6 people

Harsh Parikh, Tech Lead

Hi

Paul

,

This issue was occurred due to Dtsearch Indexing Job which is already resolved.

Mar 21, 2022 at 5:50 AM Notified 6 people

Paul Moon

Thanks,

Harsh

.

Mar 21, 2022 at 5:09 PM Notified 6 people

Paul Moon completed this to-do.

Mar 21, 2022 at 5:15 PM

TOLOGIX - ISLG App Rebuild

✔ "*Notice See other documents and proceedings that may have affected the findings in this decision or award." missing on app.islg

Comments & Events