...
Issue ref | Issue description | Date Reported | Reported by | Org | Comments | Assigned Release | Jira ref | Status |
|---|---|---|---|---|---|---|---|---|
LM0148 | Cannot edit a Schedule heading or cross-heading when Block Tags is turned on | Lucy Baines | OPC | SPT-477 | Open | |||
LM0166 | When filtering amendments, you cannot scroll down to the apply button when Chrome is at 100% | 5/5 | Mark Brough | SP | SPT-528 | Open | ||
LM0170 | We've been getting complaints about how often the system synchronises, how long it takes and the fact that you can't do anything when it's synchronising. | 13/5/21 | Louise Davies | OPC | EH to create confluence page | Open | ||
LM0171 | A few times when I was interacting with track changes, I got the following message: “Fragment has been deleted by another user. Click on "OK" to refresh the document.” Strange things would sometimes happen when I clicked OK – e.g. things would disappear. | 13/5/21 | Louise Davies | OPC | SC to test with group elements. Hard to recreate - over to the developers to investigate | SPT-543 | Open | |
LM0172 | If you copy and paste provisions which are in track changes, strange things can happen – e.g. you may not always be pasting what you have copied. | 13/5/21 | Louise Davies | OPC | LDAPP-2809 | Open | ||
LM0173 | In the Editor closing quotes after x-refs appear as opening quotes e.g. if text in the editor says for "paragraph 3" substitute "paragraph 3A" and the 3A is tagged as an x-ref, the quotes after it are the wrong way round. | 13/5/21 | Louise Davies | OPC | LDAPP-2810 | Open | ||
LM0174 | Closing quotes at the end of a quoted structure sometimes appear as straight quotes not curly quotes. For an example, see the following document, page 2, quotes at end of subsection (6)(b) and end of subsection (3). Everything looked in order in the editor and other closing quotes in the document appear correctly | 13/5/21 | Louise Davies | OPC | 14/5, EH request Project/document information | Open | ||
LM0177 | Tiny rogue line above word ‘Schedule’ on Contents page in a Scottish Bill | 29/6/21 | Stuart Todd | SPT-595 | Open | |||
LM0179 | Text in review filter is not cleared after saving | 14/7/21 | Fraser Gough | PCO | SPT-615 | Open | ||
LM0181 | Long section nums are causing the heading to auto-indent in SIs when inserted in quoted structures and the quoted structure is inserted in a regulation paragraph e.g. regulation 2(1) | SPT-622 | Open | |||||
LM0184 | Sticky version descriptions box in New dialogue | 7/8/21 | Fraser Gough | PCO | On the project tab, if I use the new button to create a new document in the project and then press it again to create another (without having logged out in between) the version description box of the pop-up still contains the name of the last document that I created. | SPT-651 | Open | |
LM0185 | Hyperactive duplicate label detection | 7/8/21 | Fraser Gough | PCO | In project tab, I tried fixing a version label from: “pROoceeds of crime” to “proceeds of crime”. This throws the error: There is already a working version “proceeds of crime" in the project. | SPT-651 | Open | |
LM0188 | Cannot edit schedule number when in 'no tag' view | 13/09/21 | Louise Davies | OPC | Emailed Louise with a couple of workarounds:
| SPT-667 | Open | |
LM0189 | Building Safety Bill - user unable to complete whole document renumber and fragment locked by another user. 'Other user' did not have document open. | 15/10/21 | Yohanna | HoC | EH - Unable to find locked provision, as 'massive' bill and looking for needle in haystack. Release All locs resolved the issue, but may want to look at finding neater solution infuture, eg: how renumbering works with locked provisions. | v11.2.0 | SPT-780 | Fixed, awaiting deployment |
LM0190 | Cannot insert sub-section after Closing words. This problem seems confined to a case where the original unnumbered section text ends with closing words. In the test section 2 seen in the screenshot above, which ends with a paragraph, the insert menu offers me the option to insert a new subsection even although there is a section 3 immediately below it. | 15/10/21 | Fraser Gough | PCO | Tell him to put his cursor in the section heading and the insert menu will give him ‘subsection’ – it will work from there. Fraser Response: Not very intutive. EH response: we'll loook at in future | Open | ||
LMP195 | Spacing between the end of a schedule and the heading of the next has been reduced. | 8/11 | Mike Wright | HoL | SC confirmed should be 36pt | v11.2.0 | SPT-703 | Fixed, awaiting deployment |
LMP196 | Table rendered incorrectly on PDF, when part of a definition | 16/11 | Mike Wright | HoL | SPT-708 | Open | ||
LMP197 | Order of Amendments in a CLoA is incorrectly sorting by a previous order of consideration | 24/11 | Mike Wright | HoL | SPT-716 | |||
LMP198 | Red highlighting no longer happening on overlapping amendments in the official lists for SP, HoC and HoL | 13/12 | Mhairi Gavin | SP | v11.2.0 | SPT-751 | Fixed, awaiting deployment | |
LMP199 | The long title is replacing upper case letters with lower case when bill is converted to an Act | 15/12 | Mike Wright | HoL | v11.2.0 | SPT-753 | Fixed, awaiting deployment | |
LMP200 | The project title is being updated when there are published versions and a user selects 'convert to act' | 15/12 | Mike Wright | HoL | SPT-752 | Open | ||
LMP201 | Amendment Manager tab not displaying amendments if there is an amendment with invalid XML | 22/12 | Mhairi Gavin | SP | v11.2.0 | SPT-765 | Fixed, awaiting deployment | |
LMP202 | user reported that 'Update x-ref' was not working when applied to 'whole document' | 11/01/22 | Laura Barrie | PCO | Discovered the issue was with tracked changes. Once they were accepted, the 'Update x-ref' function worked on the whole document again. Jamie has already fixed it, now winging its way through review process | v11.2.0 | SPT-773 | Fixed, awaiting deployment |
LMP203 | "Fragment has already been deleted by another user" error when deleting provisions in a new document that had been updated using 'pull' | 13/01/22 | Laura Barrie | PCO | SC have done extensive investigation into this issue and eventually concluded that it might have something to do with accepting all changes in another document, when these tracked change provisions linked back to provision in another document (within the processing instructions). Have written a support ticket outlining what the user did and what our theory is so that someone from Leidos can investigate further | SPT-776 | Open | |
LMP204 | You need a minimum of 2 rows to create or update a table in Lawmaker. This is frustrating when you are attempting to create a single row table (which has happened in live with Bethan in PPU creating over 20 single table row amendments to a bill. | 12/01/22 | Fliss Batty (on behalf of Bethan) | PPU | The workaround in the meantime is to create a table with 2 rows and delete the row. If they want to update the table they have to reinsert a row, update the table and then delete the row again. Not very intuitive | v11.2.0 | SPT-778 | Fixed, awaiting deployment |
LMP205 | Manuscript lists are renumbering previously published amendments | 22/12 | Mhairi Gavin | SP | SC worked out the marshalled lists were not checking for amendments published on other lists and also amendments published on manuscript lists were not being correctly updated to reflect this. | v11.2.0 | SPT-775 | Fixed, awaiting deployment |
LMP206 | Numbers inside quoted structures are dropping down a line | 14/01 | Bethan | PPU | Have worked out it's something to do with the line numbering processing instruction in the XML causing the issue. There is a woraround to conver the schedule paragraph in the quoted structure into a subsection. They look exactly the same in the PDF, it's only the underlying XML which will be affected. Will discuss this option as a potential workaround with Bethan on Monday | v11.2.0 | SPT-782 | Fixed, awaiting deployment |
LMP207 | PDFs generated from Editor and Project tab are different (differences in how empty placeholder elements are handled) | 18/01 | Mike Wright | HoL | v11.2.0 | SPT-788 | Fixed, awaiting deployment | |
LMP208 | line numbering went wrong on 5 random pages in a 173 page bill | 18/01 | Mike Wright | HoL | SPT-789 | Open | ||
LMP209 | Comparison of quoted structures | 14/1 | Louise Davies | OPC | Comparison of quoted structures (i.e. textual amendments) is going wrong when one of the source documents gets into a particular state. For some reason, the underlying XML of one of the documents had all its line breaks removed which doesn't affect how it looks in the Editor or in a PDF but is throwing the comparison function. We need to adjust the function so it is more tolerant of this. | SPT-791 | Open | |
LMP210 | Comparison failing in formula | 14/1 | Louise Davies | OPC | Comparison fails when one document contains a formula which replaces text in the other document. When the comparison feature was first implemented, you couldn't insert formulas so it may be that the interaction of the two was overlooked. | v11.2.0 | SPT-792 | Fixed, awaiting deployment |
LMP211 | Comparison failures | 14/1 | Louise Davies | OPC | Sometime elements of the underlying XML are appearing in the PDF which shouldn't be visible. I think this might be a change to the PDF generation code made for another purpose which has had this accidental side-effect. | v11.2.0 | SPT-783, SPT-793 | Fixed, awaiting deployment |
LMP212 | Formatting issue in PDF, spacing before a cross heading appearing in a quoted structure is wrong | 24/1 | Stuart Todd | SP | SPT-797 | Open | ||
LMP213 | Inserted SI text is formatting incorrectly and throwing out line numbering | 21/1 | Mike Wright | HoL | v11.2.0 | SPT-796 | Fixed, awaiting deployment |
...