Cold Chain: No way for user to acknowledge temperature breach

[adamdewey]

Describe the bug

There appears to be no way for a Mobile user to acknowledge a temperature breach captured by the Cold Chain module.

In the Standalone Cold Chain app the user is able to acknowledge the temperature breach:

To reproduce

Steps to reproduce the behaviour:

1. Set up Cold Chain module
2. Produce a temperature breach
3. Attempt to acknowledge temperature breach

Expected behaviour

User Stories

As a...	Mobile Cold Chain user
I want...	the system to alert me while there are any unacknowledged temperature breaches
So that...	I can determine if there is a new / ongoing temperature breach that requires my immediate attention

As a...	Mobile Cold Chain user
I want...	the system to show a difference between acknowledged and unacknowledged temperature breaches
So that...	I can quickly determine which temperature breach requires my attention

As a...	Mobile Cold Chain user
I want...	to be able to acknowledge temperature breaches
So that...	I can tell the system that I no longer need to be alerted about this particular temperature breach

As a...	Mobile Cold Chain user
I want...	the system to display past acknowledged temperature breaches
So that...	I can refer to the system to look up historical data about temperature breaches

User should be able to acknowledge temperature breach by tapping on the triangle icon and selecting 'Acknowledge'

Once acknowledged the corresponding breach sections (hot and cold) should be updated:

Proposed Solution

Need to also update the acknowledged field in the temperature_breach table

May also be other tables that need updating - best to check the Standalone Cold Chain app or Desktop to see how they acknowledges temperature breaches

Version and device info

• App version: 8.6.2
• Tablet model: Samsung
• OS version: Android 13

Additional context

This has been reported by a client and so priority has increased accordingly

[DhanyaHerath]

Hi @arjunSussol! If you have capacity to look at this, could you do the same as we did for the other issue, and create a proposed solution and estimate for this work please? The best thing to do would be to look at how we do it in the cold chain app - it should work basically the same here. Let me know whether you are available, thank you! :)

[adamdewey]

@arjunSussol - happy to talk through anything too!

[arjunSussol]

@DhanyaHerath @adamdewey today, I have looked at the cold chain module in mobile.
I tried to figure out the requirement. I think I need a verbal talk with @adamdewey
So, after discussion I will estimate this work.
@adamdewey this week and next week I am going to occupy by GSR system, so I will telegram you after a week.

[adamdewey]

@arjunSussol - sure that sounds good, ok I'll send an invite in the calendar for the week starting 22nd May and we can have a chat then!

[adamdewey]

@arjunSussol & @DhanyaHerath - We are looking to shift to promoting cold chain with Open mSupply for future clients and discourage using the Mobile cold chain module unless there are no alternatives.

@Gwalior-84's main client is the only one currently using the Mobile cold chain module.

I'm trying to work out whether we need to do this issue at all or if we can keep our head down and free up Arjun and the team to get into a better position for eventually helping out on Open mSupply too.

Let me talk to @Gwalior-84 offline and will be in a better position to update on the priority for this.

[adamdewey]

@arjunSussol - I spoke to @Gwalior-84 and the decision was that we don't need to do this as we have the expectation that the client will transition to Open mSupply once cold chain is integrated (hopefully by Oct/Nov this year)

[arjunSussol]

Thanks @adamdewey for the update. I am going to close this issue.

[adamdewey]

Ok, these issues have suddenly become relevant again as it looks like F-client will be using Mobile Cold Chain after all.

So I'm re-opening this

[adamdewey]