Done
Details
Assignee
Oleksandr HladchenkoOleksandr HladchenkoReporter
Ann-Marie BreauxAnn-Marie Breaux(Deactivated)Priority
P3Story Points
2Sprint
NoneDevelopment Team
FolijetFix versions
Release
Poppy (R2 2023)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Oleksandr Hladchenko
Oleksandr HladchenkoReporter
Ann-Marie Breaux
Ann-Marie Breaux(Deactivated)Priority
Story Points
2
Sprint
None
Development Team
Folijet
Fix versions
Release
Poppy (R2 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created April 19, 2023 at 6:02 AM
Updated October 13, 2023 at 11:24 AM
Resolved May 5, 2023 at 6:58 AM
Purpose: To add the job ID and the job profile into the header of the Data Import log, to make the source of the log more clear.
As a staff person working with Data Import logs
I want to be able to tell which job a log belongs to, and which job profile was used for the job
So that I can understand the log screen better
Scenarios
Scenario 1
Given the Data Import log
When displaying the header
Then add "Job n" followed by a dot, before the number of records found (in the subheader)
With "n" being the job ID (last column in the log list)
See attached mockup
Scenario 2
Given the Data Import log
When displaying the header
Then add a separate row that has "Job profile xyz"
With "xyz" being the name of the job profile used for the import
See attached mockup
Scenario 3
Given the Data Import log
When displaying job profile name in the header
Then make it a hotlink
And when a user clicks it, display the job profile details (the same behavior as when a user clicks the job profile name in the log list)
Scenario 4
Given the Data Import log
When displaying the log
Then add a 20 pixel margin on both sides, so that the log does not go to the very edge of the page
Scenario 5
Given the Data Import Holdings JSON screen
When viewing older logs (for imports created before these log changes)
Then ensure there are no error messages or weird-looking UI display
NOTE: We cannot test this on Snapshot, since previous import jobs are cleared out every day. To test this, we'll need to do some imports on Folijet Rancher, then implement these changes, and then do some additional imports. When reviewing on Rancher, please add screenshot(s) to this Jira showing what the older logs look like after the changes are merged.
Scenario 6
Ensure automated testing coverage for this new code is 80% plus
Release notes
Remind SMEs that the hotlink is to the current version of the job profile, but may not be the same details as were used for the import, especially if the import was a while ago
What if the job profile was deleted? See UIDATIMP-1450 for how it will be handled