Inconsistent 'Last Updated' and 'Last Deployed' timestamps against instances
- Dominant language
- JavaScript
- Stars
- 400
- Forks
- 89
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 149
Description
### Current Behavior
In various views we display an elapsed time (`one week ago`) to indicate activity.
We have two different values
- `Last Updated` - which reflects the `updated_at` field of the database object
- `Last Deployed` - which reflects the last time the flows were updated (via the `Storage` table)
We are not consistent in their use and in some places I think we are mislabelling one as the other.
We should pick one and use it consistently.
### Pipeline stage view:
- Label 'Deployed'
- Value 'Deployed'
### Team Applications List
- Label 'Updated'
- Value 'Updated'
### Application Instances table:
- Label 'Deployed' 🔴
- Value 'Updated'
### Team Instances List
- Label 'Updated'
- Value 'Updated'
### Instance Overview
- Label 'Updated'
- Value 'Updated'
### Expected Behavior
Consistent information between views
### Steps To Reproduce
_No response_
### Environment
- FlowForge version:
- Node.js version:
- npm version:
- Platform/OS:
- Browser:
### Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
Contributor guide
Assessment
This issue has not been assessed yet.