ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Task being carried out (use name from wiki or describe the task if it is an additional one you have decided to try)Tester's NameCategory
Documentation = The app works as expected but documentation (or more/better documentation) will be needed to make function clear
Enhancement = You'd like to see some additional features or functionality in the application
Failure = You are unable to complete the test
Specification = The app doesn't behave as you'd expect given your understanding of Serials Management
Success = The app works as expected		Tester's feedback (describe the issue you've encountered or what changes you'd like to see, or any other useful information)PO comments and actions (for the PO to complete)Linked JIRA issues (where applicable)
2
Task 2.2: Add publication pattern with chronology and enumerationJared NagelSuccessThis worked but I couldn't get the preview (step 6) to dislpay a volume 11 (other numbers worked fine)Bug report added to Jirahttps://folio-org.atlassian.net/browse/UISER-99
3
Task 1.1: Create and view a serial linked to a POLJared NagelSuccessPerfect and smooth🎉
4
Task 1.1: Create and view a serial linked to a POLJennifer EustisSuccessI like the link to the "View in inventory". However, I added 3 notes which can't be viewed - it would be nice to view them in the right hand preview pane.JIRA to add notes to display UIOA-65 UIOA-100
https://folio-org.atlassian.net/browse/UISER-100
5
Task 5.2 Generate receiving pieces for a predicted piece setJared NagelFailureI couldn't get predictive patterns to link up to recieving. Step 11 wouldn't generate pieces in recieving when I clicked the button (probably a bug)At the moment there is an issue here, which means that even when we do generate the receiving pieces there is no feedback to the user. However I just wanted to check to see if there was some other issue here - did you check in Receiving whether the receiving pieces existed? Or did you just assume nothing had happened because there was no obvious feedback on screen? If the former any more information about the order you had linked the serial to would be welcomehttps://folio-org.atlassian.net/browse/UISER-90
6
Task 1.2: Create and view a serial linked to a package POLJennifer EustisSuccessGreat. Except I would like to be able to see notes when previewing record.JIRA to add notes to display UIOA-65 UIOA-100
https://folio-org.atlassian.net/browse/UISER-100
7
Task 1.1: Create and view a serial linked to a POLLucy BarronSuccess
8
Task 2.1: Add publication pattern with chronology onlyJennifer EustisSuccessTo see "Add publication pattern" when there was none, I had to click on the caret. It'd be great to just always see this button.Fixed - see linked Jira issuehttps://folio-org.atlassian.net/browse/UISER-65
9
Task 1.2: Create and view a serial linked to a package POLJoanna CerroSuccessWhen adding titles to a package, it would be great to have the package titles accordion default to expanded. I had some trouble finding the "Add" button.Serials PO to refer to Orders PO
10
Task 2.1: Add publication pattern with chronology onlyJoanna CerroSuccess
11
Task 2.2: Add publication pattern with chronology and enumerationJoanna CerroSuccess
12
Task 2.2: Add publication pattern with chronology and enumerationJennifer EustisFailureI noticed that in the preview and in the level no. of units, I can add negative numbers and there's no warning.JIRA bug raised UISER-103
https://folio-org.atlassian.net/browse/UISER-103
13
Tasks 3.1 and 3.14:
Add publication patterns of varying frequencies		Jennifer EustisSuccessNot sure this worked. Every time I tried to add a publication pattern, it replaced the new one with my old one. I think there can only be 1 pub pattern right. How do you deal with a change in the pattern or when every x amount of time, there is a different patter (monthly except for 5th year for special issue)?You are correct - there should be only one active pattern at a time. At the moment adding multiple active patterns is being allowed but it shouldn't be. There is work in progress to fix this (see linked Jira).

When the pattern changes, the existing pattern will become "deprecated" and the new pattern will become the active one. In the case of "one off" changes (as your example) I guess the question would be when it's worth setting up a special pattern and when it's worth just amending the pieces - definitely worth some more discussion and thought		https://folio-org.atlassian.net/browse/UISER-35
14
5.1: Generate predictive piecesJennifer EustisSuccess
15
5.2: Generate receiving piecesJennifer EustisFailureWhen I clicked on Generate receiving pieces button nothing happenedConfimed this was a known bug - the pieces were generated but there was no indication in the Serials UI that this had happened. Should be resolved via UISER-90https://folio-org.atlassian.net/browse/UISER-90
16
Task 1.1: Create and view a serial linked to a POLBrian CheungSuccessGood to have the function to search against description field. Not related but just found PO notes are not searchable👍
17
Task 1.1: Create and view a serial linked to a POLLucy BarronSuccessIt seems like everything I did yesterday got wiped from the test instance. I am having to start all over with this step.I'm afraid the Folio Snapshot and Folio Snapshot 2 environments are wiped each day. I've added a note to the UAT page on the wiki to make this clearer. Do note however that the Tasks do not need to be performed in sequence. All the tasks are designed as stand-alone tasks. Only Tasks 1.1, 1.2 and 5.2 require a serial to be connected to a Purchase Order Line
18
Tasks 3.1 - 3.14: Add publication patterns of varying frequencies
Joanna CerroSuccess
19
Task 2.1: Add publication pattern with chronology onlyBrian CheungSuccess
20
Task 2.2: Add publication pattern with chronology and enumerationBrian CheungSuccessIssues recorded in UISER-73: Adding new publication pattern will overwrite existing one; also cannot delete a pattern?Fixed - see linked Jira issuehttps://folio-org.atlassian.net/browse/UISER-73
https://folio-org.atlassian.net/browse/UISER-35
21
Task 2.1: Add publication pattern with chronology onlyLucy BarronSuccessAt Step 6, I forgot to preview before saving. I could not figure out how to go back in and edit the pattern I just created. I only found the "Create pattern" option. Is there a way to edit a pattern after creation? I finally figured out how to create the expected pieces by hitting "Generate ..." and continued with the instructions. I think this will be very confusing to staff as many mistakes will be made especially at the beginning.PO to discuss with the dev team
22
Task 2.2: Add publication pattern with chronology and enumerationLucy BarronFailureI saved the pattern in 2.1 and it's not letting me save the 2nd pattern after trying twice. A serial changes frequencies over it's lifetime and we need to either be able to delete the old pattern or save multiple patterns.Fixed - see linked Jira issuehttps://folio-org.atlassian.net/browse/UISER-35
23
Task 2.2: Add publication pattern with chronology and enumerationLucy BarronEnhancementAlso, this is a design issue, but it is irritating to create all the stuff then have to scroll back up to the Label template. Can it be below? Bug created in Jir UISER-104
https://folio-org.atlassian.net/browse/UISER-104
24
Task 2.2: Add publication pattern with chronology and enumerationLucy BarronFailureAre technicians going to have to learn this type of programming for the Label Template to create a pattern each time or will there be something in plain language that they can choose?Ultimately we wish to have an easier to use interface here that does not require the user to remember the "token codes". We are considering the approach taken in circulation for patron notice templates https://docs.folio.org/docs/settings/settings_circulation/settings_circulation/#patron-notice-templates but would be interested in hearing suggestions for alternative approaches. However, for the first release of the module the user will have to enter the token codes by hand
25
Task 2.2: Add publication pattern with chronology and enumerationLucy BarronFailureAlso, I tried doing a combined issue and I only got the enumeration for the first piece, not the second. Maybe I'm jumping ahead of the test. You are correct there is an issue here at the moment. There is a Jira for this UISER-102 however, this is unlikely to be resolved for v1 of serials. There are limited workarounds available for very specific combined issue cases but no general solution right now.
https://folio-org.atlassian.net/browse/UISER-102
26
Task 1.1: Create and view a serial linked to a POL
Roman Yurchenko
SuccessEverything went fine according to the instructions.👍
27
Task 1.1: Create and view a serial linked to a POLNina StellmannSuccess
28
Task 1.2: Create and view a serial linked to a package POLNina StellmannSuccessIf I look at the serials title in the view mode I see the PO line number, the title of the package
and the order number but not the serials title. The serials title I can only see in the list of serials. The same I recognize when I open the serial in the edit mode, for example to add a description. Maybe it's helpful to see the serials title in the view mode and edit mode 		The serial title should be added to the serials view. There is a Jira for this UISER-65. Also in the serial edit view - there is a Jira for this: UISER-80https://folio-org.atlassian.net/browse/UISER-65
https://folio-org.atlassian.net/browse/UISER-80
29
Task 2.1: Add publication pattern with chronology only
Nina StellmannSuccessIt would be great to have an "i" icon for the template with information for how to fill the template inJira issue UISER-105 created
https://folio-org.atlassian.net/browse/UISER-105
30
Task 2.2: Add publication pattern with chronology and enumerationNina StellmannSuccess
31
Task 4.1 Add publication pattern with omissions
Nina StellmannSuccessAll works as expected👍
32
Task 5.2 Generate receiving pieces for a predicted piece setDung-Lan ChenEnhancementIf POL has create Inventory setting as none, receiving pieces are generated but a confirmation would have been ideal as I clicked on "Generate receiving pieces" again after the first click since no indication/confirmation that pieces were generated. Then I went to Receiving app and discovered two sets of the receiving pieces were generated becuase I clicked on the button twice.Confimed this was a known bug - the pieces were generated but there was no indication in the Serials UI that this had happened. Should be resolved via UISER-90https://folio-org.atlassian.net/browse/UISER-90
33
Task 4.1 Add publication pattern with omissions
Lucy BarronSuccessI experimented with adding additional omissions and these also worked.👍
34
Task 4.2 Add publication pattern with combinations
Lucy BarronSpecificationWhen issues are combined, the first issue and last issue should show with a slash / between to show both issues. Otherwise, it looks like the combined issues are missing. Thus, in the example given, the volume shoud say: Vol. 1 Issue 7/Issue 8 July/August 24. Another example is Vol. 1 Issue 6/Issue 8 June/August 24. How would we set up a patter where every issue is combined? For example: 2021/2022, 2022/2023You are correct there is an issue here at the moment. There is a Jira for this UISER-102 however, this is unlikely to be resolved for v1 of serials. There are limited workarounds available for very specific combined issue cases but no general solution right now.
https://folio-org.atlassian.net/browse/UISER-102
35
Task 1.1: Create and view a serial linked to a POL
Peter Sbrzesny, Martina Schildt
SuccessWorks as expected, links are working, given information is dispayed👍
36
Task 1.2: Create and view a serial linked to a Package POL
Peter Sbrzesny, Martina Schildt
EnhancementWhen a serial record is linked to a specific package title, the title should display on the serial record.
It would be helpful to have a link to the specific receiving title within the package.
Workaround: title can be recorded in description field.		The title displays in the serial pane header - although this may not be as obvious as it could be, and it isn't linked. I have created new issue in Jira to add the title in the main pane including a link to view the title in receiving
https://folio-org.atlassian.net/browse/UISER-112
37
Task 2.1: Add publication pattern with chronology only
Peter Sbrzesny, Martina Schildt
Success
38
Task 2.2: Add publication pattern with chronology and enumeration
Peter Sbrzesny, Martina Schildt
FailureWhen previewing predicted pieces, we have set a start date = March 1st and defined level 1 = 2 and level 2 = 3. The preview displayed Vol. 3, issue 2, March 24. We would have expected the display: Vol. 2 Issue 3, March 24Bug created in Jira https://folio-org.atlassian.net/browse/UISER-88
39
Tasks 3.1 - 3.14: Add publication patterns of varying frequencies
Peter Sbrzesny, Martina Schildt
Success
40
Tasks 3.1: Add an Annual publication pattern (1 issue per year)
Peter Sbrzesny, Martina Schildt
Success
41
3.2 Add a Bimonthly publication pattern (2 issues per month)
Peter Sbrzesny, Martina Schildt
FailureWhen doing the preview, the vol number does not use the values defined - it starts always with vol. 1 = known issueBug created in Jira https://folio-org.atlassian.net/browse/UISER-99
42
3.3 Add a Semiweekly publication pattern (2 issues per week)
Peter Sbrzesny, Martina Schildt
Success
43
3.4 Add a Daily publication pattern (1 issue per day)
Peter Sbrzesny, Martina Schildt
Success
44
3.5 Add a Biweekly publication pattern (1 issue per 2 weeks/14 days)
Peter Sbrzesny, Martina Schildt
Success
45
3.6 Add a Semiannual publication pattern (1 issue per 6 months)
Peter Sbrzesny, Martina Schildt
Success
46
3.7 Add a Biennial publication pattern (1 issue per 2 years)
Peter Sbrzesny, Martina Schildt
SuccessPreview for predicted pieces also works for value 3 for label 2, level1, results in "Band 3.2025"👍
47
3.8 Add a Triennial publication pattern (1 issue per 3 years)
Peter Sbrzesny, Martina Schildt
Success👍
48
3.9 Add a Three times a week publication pattern (3 issues per week)
Peter Sbrzesny, Martina Schildt
Success👍
49
3.10 Add a Three times a month publication pattern (3 issues per month)
Peter Sbrzesny, Martina Schildt
​
50
3.11 Add a Monthly publication pattern (1 issue per month)
Peter Sbrzesny, Martina Schildt
​
51
3.12 Add a Quarterly publication pattern (1 issue per 3 months / 4 issues per year)
Peter Sbrzesny, Martina Schildt
​
52
3.13 Add a Semimonthly publication pattern (2 issues per month)
Peter Sbrzesny, Martina Schildt
​
53
3.13 Add a Three times a year publication pattern (1 issue per 4 months / 3 issues per year)
Peter Sbrzesny, Martina Schildt
​
54
3.14 Add a Weekly publication pattern (1 issue per week)
Peter Sbrzesny, Martina Schildt
​
55
Task 4.1 Add publication pattern with omissions
Peter Sbrzesny, Martina Schildt
Success👍
56
Task 4.2 Add publication pattern with combinations
Peter Sbrzesny, Martina Schildt
EnhancementWorks as expected. It would be nice if the combined issue would show both Issue numbers instead of only one (e.g. if 7 and 8 are combined = Vol.1 Issue 7/8, July 24
Might be adjustable in receiving app.		As noted this can be adjusted in the receiving app, but we do aim to support this directly as well. A Jira story has been created
https://folio-org.atlassian.net/browse/UISER-102
57
Task 5.1 Generate predicted pieces
Peter Sbrzesny, Martina Schildt
SuccessWe generated predicted pieces with a combination - in the predicted pieces MCL the combined issues displayed at the end of the list - although we combined issues 5 and 6 = somwhere in the middle)👍
58
Task 5.2 Generate receiving pieces for a predicted piece set
Peter Sbrzesny, Martina Schildt
EnhancementPredicted pieces are succesfully generated in receiving. The time between publication and receiving is calculated correctly.
Issues:
The predicted piece set in Serials does not display anything in the column for "generated in receiving", altough the pieces have been generated in receiving. This happens for a pattern with combinations/omissions as well as for a pattern without these options.
We tested the generation with a pattern including a combination rule. The receiving pieces in Receiving do not display the number for the combined issues - instead there is a dash displayed - this can be solved by editing the receiving piece and adding a display summary.		The "Generated in receiving" column should be populated to give the user feedback. There is a Jira to fix thishttps://folio-org.atlassian.net/browse/UISER-90
59
Task 1.1: Create and view a serial linked to a POL
Sarah HamiltonDocumentationI did have trouble getting my PO to save initially. I clicked on the "Template Name", and that seemed to prohibit me saving it.Issue in Orders rather than Serials. To be fed back to the Orders Product Owner
60
Task 1.2: Create and view a serial linked to a package POL
Sarah Hamilton​
61
Task 3.1-3.2 Add publication patterns of varying frequenciesLucy BarronFailureWhen adding enumeration, the Preview always starts with the first issue. For the semiannual, for example, I set up the pattern and told it to start with volume 12, but it started with v. 1. For the annual, I had an enumeration and chronology and told it to start with v. 12, and it again started with v. 1 in the Preview. Otherwise, it is working.This is a bug. There is a Jira issuehttps://folio-org.atlassian.net/browse/UISER-99
62
Task 5.2 Generate receiving pieces for a predicted piece set
Reinhard Niederer
EnhancementThere is no success-message. Pressing the button several times creates more and more items for receivingConfimed this was a known bug - the pieces were generated but there was no indication in the Serials UI that this had happened. Should be resolved via UISER-90https://folio-org.atlassian.net/browse/UISER-90
63
Task 1.1: Create and view a serial linked to a POLMarie MeyerSpecificationWe added a note in the serials record (New serial -> add note), but it didn't show up anywhereA Jira has been created to add the notes to the display
https://folio-org.atlassian.net/browse/UISER-100
64
Task 1.1: Create and view a serial linked to a POLMarie MeyerEnhancementIn the serials record under the accordeon PO line we would like to see the publisher form the POLThis is a great enhancement suggestion. A Jira has been created but unfortunately this is not a straightforward thing to add (as the publisher is not available directly from the order line) so is unlikely to be done for v1 release (Quesnelia)
https://folio-org.atlassian.net/browse/UISER-114
65
Task 2.2: Add publication pattern with chronology and enumerationMarie MeyerEnhancementlabel type chronology -> year: the year should be defined flexibly - for example: a publication year of a journal is between April 2024 and March 2025, issues that are published between January 2025 and April 2025 should still be labled with year 2024This can be achieved by defining an enumeration with one level of continuous numbering - in this case this would start at "2025" and then can be used in the template.
66
Task 2.2: Add publication pattern with chronology and enumerationMarie MeyerDocumentationThere should be examples how the labels are written in the template field. A drop down menu with standard patterns to choose from would be helpful.Ultimately we wish to have an easier to use interface here that does not require the user to remember the "token codes". We are considering the approach taken in circulation for patron notice templates https://docs.folio.org/docs/settings/settings_circulation/settings_circulation/#patron-notice-templates but would be interested in hearing and discussing suggestions for alternative approaches. However, for the first release of the module the user will have to enter the token codes by hand
67
Task 5.1 Generate predicted piecesMarie MeyerEnhancement"Values to use for the first issue" fields should be mandatoryThis seems a sensible suggestion. I have created a Jira for this
https://folio-org.atlassian.net/browse/UISER-115
68
Task 5.2 Generate receiving pieces for a predicted piece setMarie MeyerSpecificationThere was no success-message so we clicked on the button twice because we thought it didn't work. We should not be able to generate the same pieces multiple times without warning. A success message or a warning would be great.Confimed this was a known bug - the pieces were generated but there was no indication in the Serials UI that this had happened. Should be resolved via UISER-90https://folio-org.atlassian.net/browse/UISER-90
69
Task 2.2: Add publication pattern with chronology and enumeration
Christina Lehmann
EnhancementPatterns that already exist should be displayed again and should be easily to modificate when there are any changes e.g. other number of issues, new chronology etc.I think this is a good suggestion, and I wonder if we could establish something like the Purchase Order template system where you can choose from a list of order templates that automatically fill out specific fields for you - and then you can make manual edits as necessary. I think it needs some more thought and discussion before we create a Jira for it.
70
Task 1.1: Create and view a serial linked to a POL


Julia LeggettSuccess👍
71
Task 1.2: Create and view a serial linked to a package POL
Julia LeggettSuccess👍
72
Task 2.1: Add publication pattern with chronology only
Julia LeggettSuccess👍
73
Task 2.2: Add publication pattern with chronology and enumeration
Julia LeggettSuccess👍
74
Tasks 3.1 - 3.14: Add publication patterns of varying frequenciesJulia LeggettDocumentation It was difficult to understand the documentation on Publication patterns: Templates. Need addtional exmples on writing tokens for the publication patterns. It would be good to get more specific feedback on how the documentation could be improved.

Ultimately we wish to have an easier to use interface here that does not require the user to remember the "token codes". We are considering the approach taken in circulation for patron notice templates https://docs.folio.org/docs/settings/settings_circulation/settings_circulation/#patron-notice-templates but would be interested in hearing suggestions for alternative approaches. However, for the first release of the module the user will have to enter the token codes by hand
75
Task 5.1 Generate predicted pieces
Julia LeggettSuccess👍
76
Task 5.2 Generate receiving pieces for a predicted piece setJulia LeggettSuccess👍
77
Task 2.2: Add publication pattern with chronology and enumerationMilena FeinFailureI created a publication pattern with chronology: chronology format = year / year format = 2023. Enumeration: enumeration format = numeric / level 1: no. of units = 1, format = Number, sequence = continous. level 2: no. of units = 6, format = number, sequence = continous. I generated the template: Jg. {{enumeration1.level1}} ({{chronology1.year}}), Nr. {{enumeration1.level2}}. To create a preview I selected start date = 01/01/2024 / Values to use for the first issue: Level 1 = 56, Level 2 = 598. I expected as first issue: Jg. 56 (2024), Nr. 598. After clicking on "Preview" the known issue appears that it starts with "Jg. 1 (2024), Nr. 1". Repeating clicking on "preview" it starts with: "Jg. 607 (2024), Nr. 56" or after further clicking "Jg. 155 (2024), Nr. 598". The result "Jg. 155 (2024), Nr. 598" also appears as first issue with tasks 5.1 and 5.2 (Generate predicted pieces and receiving pieces).Agree this is a bug. I think this is related to an existing JIRA UISER-99. We will investigate and fixhttps://folio-org.atlassian.net/browse/UISER-99
78
Task 5.1 Generate predicted pieces
Lucy BarronSuccess👍
79
Task 5.1 Generate predicted pieces
Lucy BarronEnhancementI think we discussed a feature where you can convert the months into the language you desire, instead of English.You are correct. This is meant to be supported but hasn't been managed yet. I have created a Jira for this. There is a work around which is to setup a Textual Enumeration with the months/days/seasons in the alternative language and apply them as a label.
https://folio-org.atlassian.net/browse/UISER-113
80
Task 5.2 Generate receiving pieces for a predicted piece setLucy BarronSuccessWhen you preview the pattern before saving, it starts with Vol. 1, issue 1, regardless of what you input. But when you save and preview before generating the issues, it shows the issue you specified to start with. 👍
81
Task 5.2 Generate receiving pieces for a predicted piece setLucy BarronSuccessWhen you generate receiving pieces in Step 12, the form doesn't close, so you don't know if it did it or not. {I clicked again and generated the issues twice. How do you undo that?}👍
82
Task 5.2 Generate receiving pieces for a predicted piece setLucy BarronSuccessI checked in (received) the first issue, then went to the inventory app. It said it was on order. It didn't show the issue I checked in in the holdings record. Why is that?👍
83
Task 2.1: Add publication pattern with chronology onlySylvia HamannEnhancementAfter clicking on "Preview" and choosing a start date, nothing happened on the first 4 tries - no message, no preview, no change in the preview modal. When I checked my input against the description of 2.1, I finally caught that two curly brackets in my template were missing. Would it be possible to check whether the used brackets are adding up, and if there are flaws in the template syntax, could there be a message e.g. in the preview modal that the template should be adjusted? And could the Title of the Preview window be changed to "Preview predicted pieces"? It seems a bit confusing to me (panicking for a moment because I thought something went fundamentally wrong ;-) )This is a good suggestion and I've created a Jira story for it
https://folio-org.atlassian.net/browse/UISER-116
84
Task 4.2 Add publication pattern with combinationsBob MorganDocumentationSuccessful completion, but with several stumbles. Would like context-sensitive help, i.e., explanation of what values correspond with those chosen.Agree we need to have good documentation and ultimately make the process of filling out the values easier and more intuitive
85
Task 2.1: Add publication pattern with chronology only
Roman Yurchenko
Success👍
86
Task 2.2: Add publication pattern with chronology and enumeration
Roman Yurchenko
Success👍
87
Tasks 3.1-3.14 Add publication patterns of varying frequenciesJulia LeggettSuccess👍
88
​
89
​
90
​
91
​
92
​
93
​
94
​
95
​
96
​
97
​
98
​
99
​
100
​