As a user of an openQA web UI instance using archived jobs I would like to understand that archived jobs can take longer to load than expected.
With #91782 we provide archive support meaning that some jobs are "archived" and loading can be slower than usual. To prevent user confusion the web UI should provide feedback when archived jobs are accessed.
- AC1: Users can see when they access jobs that can take longer due to results being stored on potentially slower storage
- provide feedback when archived jobs are accessed, e.g. showing a message "Archived job: Loading can take longer than usual"
- Description updated (diff)
What is actually slow here? And are we talking minutes or milliseconds?
Well, the archiving feature means that we can store on different storage than the normal one, normally it should be "cheaper+slower" storage so loading time can be longer.
The description doesn't seem to be based on a concrete user story.
Added a user story.
- Status changed from Workable to Feedback
- Assignee set to mkittler
The initial implementation of the archiving feature already shows an icon on the job details page, see https://github.com/os-autoinst/openQA/pull/3858/commits/a6215fcee6822b78e2e19a6fbbe592037264e5d4.