Actions
New Feature #11166
closed
New Feature #11098: View for android Application updates monitoring and manage.
Adding operation log of a subscription
Start date:
13/05/2024
Due date:
28/06/2024
% Done:
100%
Estimated time:
Device Type:
Component:
Type:
QA Start Time:
QA Due Time:
QA Estimated Time(Hours):
Description
- Need to add new API which can be queried via subscription type.
- Need to add service layer business logic to handle this scenario.
- Need to add DAO layer improvements.
Files
Updated by
Updated by Nipuni Kavindya about 1 year ago
- Due date changed from 26/06/2024 to 28/06/2024
- Status changed from New to QA
- Assignee changed from Kavin Prathaban to Nipuni Kavindya
- % Done changed from 0 to 100
Updated by Arshana Atapattu about 1 year ago
- Status changed from QA to Implementation
Updated by Kavin Prathaban 12 months ago
- Status changed from Implementation to QA
Actions
#6
Updated by Arshana Atapattu 12 months ago
- File Screenshot from 2024-07-07 00-44-18.png Screenshot from 2024-07-07 00-44-18.png added
- File Screenshot from 2024-07-07 00-47-59.png Screenshot from 2024-07-07 00-47-59.png added
- File vokoscreen-2024-07-07_00-48-40.mkv vokoscreen-2024-07-07_00-48-40.mkv added
- Status changed from QA to QA Reject
Description
It seems like the logs are incorrectly picked.
On a subtenant the operation and the installation log seems to have a quite different dates [1]
This behavior was seen in other places also.
When there were two install operation for the same app, it showed the incorrect data of the log [2]
A success log was appeared in "Failed Devices"
Refer the video [3]
[1]![[1]](/attachments/download/3852/Screenshot%20from%202024-07-07%2000-44-18.png "[1]")
[2]![[2]](/attachments/download/3853/Screenshot%20from%202024-07-07%2000-47-59.png "[2]")
Updated by Lasantha Dharmakeerthi 12 months ago
- Status changed from QA Reject to QA
Updated by Arshana Atapattu 12 months ago
- Status changed from QA Accept to Closed
Closing due to QA accept
Actions