RY shouldn't index pages starting with a dot (ex: .Page Name), for Scroll Versions
Priority
Description
Attachments
2
Activity
Show:
Resolved
Details
Details
Assignee

Reporter

Sprint
None
Story Points
1
Labels
Release date
Jul 30, 2024
Requirement Yogi
Linked requirements
Requirement Yogi
Linked requirements
Created April 11, 2024 at 8:55 AM
Updated August 27, 2024 at 9:32 AM
Resolved August 8, 2024 at 11:04 PM
Indexing v1 already works properly. Only the indexing v2 has an issue.
To reproduce
Create requirements in a page
The title of this page shall start normally (
Page Title
)Copy this page (using confluence copy)
Change the name of the title with a dot (
.Page Title
)Current behaviour (indexing v2)
→ Creates a multiple definition error for the requirement
Expected behaviour (indexing v2)
→ Requirements in the .Page Title shouldn’t be indexed
→ But, if the requirement only exists on a
.Page Title
, then the requirement should still exist with status=DELETED and text like this:For the developer
The method to detect whether it’s a
.Page
isisScrollVersionDocument()
, and you may need it in bothLegacyIndexingService
andIndexingService
.If you want to delete a requirement from a page, you need to call
importDocument(pageId, (callback) -> { page parsing which calls callback.saveRequirement(dtoRequirement); })
with no requirements for the page.But in your situation, you will still need to parse the page to create the requirements as “deleted”. Therefore I suggest to call the callback with a dtoRequirement which has status=DELETED,
And in this situation, a
DocumentImporterAPI.saveRequirementInternal()
which received a DTO with a status=DELETED, should check whether the requirement exists in the DB, and if it doesn’t, create it with the status=DELETED and the text that is provided.