Hi Morgan ,

If user click on Full Citation text then will open Document View in new tab ?  same as for Treaty & Rule, if user click or any Treaty & Rule title then it will open Document View in new tab ?

Hi Harsh ,

I think it would make more sense to always open the Document View and Dispute View in a separate tab, particular given that the breadcrumbs are inconsistent and don't always lead you back to same place on the previous page.

Thanks,

Morgan

Having said that,  Melissa and Naomi do you foresee any issues with setting things up this way?

Morgan

Hi Morgan , 

No that should be fine for the documents/disputes to open in a new tab from the research tools. 

Thanks, 

Naomi 

Ok. Great. Thanks Naomi ​.

Harsh ​, could you please implement this across all the modules for the Document card view.

Note that this means it wouldn't apply when selecting full citations within the Treaties & Rules or Disputes & Dispute Documents libraries.

Thanks,

Morgan

Hi Morgan ,

I assume you posted above message in wrong thread.

Hi Morgan ,

As per your above comment, It means if user click on Full Citation, All Dispute, or Full Case & Analysis button from Treaty & Rule & Dispute Document Library then it opens Document or Dispute view in same tab.

Hi Harsh ​,

Yes, that's correct.

Thanks,

Morgan

Hi Morgan ,

This task is done on staging.islg. Please check and confirm.

Hi Piyush ,

The changes on staging.islg look good, and the changes can be deployed to app.islg when appropriate.

Martin , now that we've switched to the formal sprint process, we don't have a way of tracking which changes have been completed on staging.islg, but have not been deployed to app.islg. I think it's important we do this so that a final round of UAT is done after the changes are fully deployed on app.islg. How do you suggest we track this? Could this be done by adding a new a new state in DevOps like "Done - Staging"? The idea being that this item would get changed to "Done -Staging" now, and then changed to "Done" when it's confirmed that it was successfully deployed to app? It looks like this might be possible: https://devblogs.microsoft.com/devops/states-customization-on-team-services/ 

Thanks,

Morgan

Martin , further to our discussion this morning, I'm going to mark this to-do complete and let you or Harsh mark the relevant item in DevOps with the appropriate tag or status to indicate that the item is done on staging and pending deployment on production.

Thanks,

Morgan