The Legal Data for OT/0020 is already available. In above video, you were displaying the dispute detail of UIN IC/0460.
And we found that there is no legal data under UIN IC/0460. Hence, It was not display in above video.
Notified 5 people
Paul Moon
Hi
Harsh
:
Sorry for the confusion. Yes, OT/0020 data does show up.
However, I discovered an issue where "Type of Court Decision/Judgment" erroneously appears under Dispute Details as shown below for every dispute. Could you remove it under "Dispute Details"?
Melissa
and
Naomi
, why was the "Type of Court Decision/Judgment" added to the Dispute form? I don't think this field is relevant anymore after we removed Proceeding Stage as the primary method for organizing dispute documents.
Thanks,
Morgan
Notified 6 people
Harsh Parikh,Tech Lead
Hi
Melissa
and
Naomi
and
Morgan
,
Please guide us what we need to do in this task as per story we remains Type of Court Decision/Judgment field in Dispute View.
Please let us know.
Notified 7 people
Morgan Maguire,CEO
Hi
Melissa
and
Naomi
,
Following-up on above, could you confirm what we should do about the "Type of Court Decision/Judgment". From our perspective, this field is not relevant to our data and should not have been added to the dispute form as hardcoded field, but I want to confirm that the field doesn't have a purpose that I'm not considering before we provide
Harsh
instructions to remove it.
This field was meant to be used to populate data in the “By Decision/Party Agreement” field. Seeing as we have removed that field, this one no longer needs to be hard-coded as a meta field in disputes.
Notified 7 people
Morgan Maguire,CEO
OK. Sounds good. Thanks
Naomi
.
Harsh
, could you please remove the "Type of Court Decision/Judgment" field from the dispute form to resolve this to-do:
We have removed The Type of Court Decision/Judgment MetaField from both staging.islg and app.islg.
From Subscriber side, it will be not visible but subscriber side you will check after will deploy code on 28th Feb.
Notified 7 people
Morgan Maguire,CEO
Ok. Sounds good
Harsh
.
Paul
, could you please test that this item is complete on the admin site and then perform a test on the subscriber site next Monday.
Thanks,
Morgan
Notified 7 people
Paul Moon
Ok, I'll test this next Monday. As far as I am aware, this problem does not show up on the subscriber site; let me know if you found it appearing on the subscriber site.
Thanks,
Paul
Notified 7 people
Paul Moon
Hi
Harsh
:
I confirm "Type of Court Decision/Judgment" that was appearing erroneously has been removed on both app.islg and staging.islg.
The Legal Data for OT/0020 is already available. In above video, you were displaying the dispute detail of UIN IC/0460.
And we found that there is no legal data under UIN IC/0460. Hence, It was not display in above video.
Sorry for the confusion. Yes, OT/0020 data does show up.
However, I discovered an issue where "Type of Court Decision/Judgment" erroneously appears under Dispute Details as shown below for every dispute. Could you remove it under "Dispute Details"?
Thanks,
Paul
Thanks,
Morgan
Please guide us what we need to do in this task as per story we remains Type of Court Decision/Judgment field in Dispute View.
Please let us know.
Following-up on above, could you confirm what we should do about the "Type of Court Decision/Judgment". From our perspective, this field is not relevant to our data and should not have been added to the dispute form as hardcoded field, but I want to confirm that the field doesn't have a purpose that I'm not considering before we provide
Thanks,
Morgan
This field was meant to be used to populate data in the “By Decision/Party Agreement” field. Seeing as we have removed that field, this one no longer needs to be hard-coded as a meta field in disputes.
Thanks,
Morgan
We have removed The Type of Court Decision/Judgment MetaField from both staging.islg and app.islg.
From Subscriber side, it will be not visible but subscriber side you will check after will deploy code on 28th Feb.
Thanks,
Morgan
Thanks,
Paul
I confirm "Type of Court Decision/Judgment" that was appearing erroneously has been removed on both app.islg and staging.islg.
Thanks,
Paul