As shown in the video below, a dispute (UN/0183) becomes "locked" when an admin user published a dispute document (UN/0183/22) without actually editing anything under the dispute itself (UN/0183). This triggers a subsequent admin user having to override, causing confusion amongst admin users.
This is a high priority item, as it affects admin users on a daily basis.
Can you please add this as an Unplanned/Critical task.
Thanks,
Morgan
Notified 5 people
Harsh Parikh,Tech Lead
Hi
Paul
,
We checked and we are not able to find the above issue. Might be Nafiseh had open that dispute and directly close the browser window.
If you have any more details or any full video with this issue then provide us so we can check with those steps.
Notified 5 people
Paul Moon
Hi
Harsh
:
As you can see in the video below,
Nafiseh
and
Irit
tested IC/0428 and IC/0428/17. When Nafiseh first checked IC/0428 before Irit uploaded IC/0428/17, it doesn't require admin override. However, once Irit uploaded IC/0428/17, Nafiseh is presented with a message that Irit is editing IC/0428 and an admin override option; Irit was not editing IC/0428.
Publishing a dispute document should not trigger the dispute to become "locked" which require admin override by a subsequent admin user.
The videos below show the same issue on staging.islg.
Irit
did the following:
1. Published IC/0428/101 with PDF but no HTML (Dispute Document). After that, I went into IC/0428 (Dispute). I am getting the admin override message alerting me that Irit is editing IC/0428 even though she is not editing IC/0428 (Dispute).
2. Published IC/0428/100 with PDF but no HTML (Dispute Document) and then created a draft (there are two versions of IC/0428/100 on staging.islg admin). After that, I went into IC/0428 (Dispute). I am getting the admin override message alerting me that Irit is editing IC/0428 even though she is not editing IC/0428 (Dispute).
We need to be able to edit Disputes while there are Dispute Documents with a published version and a draft.
This is a high priority item, as it affects admin users on a daily basis.
Can you please add this as an Unplanned/Critical task.
Thanks,
Morgan
We checked and we are not able to find the above issue. Might be Nafiseh had open that dispute and directly close the browser window.
If you have any more details or any full video with this issue then provide us so we can check with those steps.
As you can see in the video below,
Publishing a dispute document should not trigger the dispute to become "locked" which require admin override by a subsequent admin user.
The videos below show the same issue on staging.islg.
1. Published IC/0428/101 with PDF but no HTML (Dispute Document). After that, I went into IC/0428 (Dispute). I am getting the admin override message alerting me that Irit is editing IC/0428 even though she is not editing IC/0428 (Dispute).
2. Published IC/0428/100 with PDF but no HTML (Dispute Document) and then created a draft (there are two versions of IC/0428/100 on staging.islg admin). After that, I went into IC/0428 (Dispute). I am getting the admin override message alerting me that Irit is editing IC/0428 even though she is not editing IC/0428 (Dispute).
We need to be able to edit Disputes while there are Dispute Documents with a published version and a draft.
Thanks,
Paul
This issue is resolved on staging.islg. Please check and confirm. Please check with new document.
Irit