Skip to content

added open fast trace requirements for backend search#13851

Closed
Bronterrzel wants to merge 6 commits into
JabRef:mainfrom
Bronterrzel:requirements-OFT-backend-search
Closed

added open fast trace requirements for backend search#13851
Bronterrzel wants to merge 6 commits into
JabRef:mainfrom
Bronterrzel:requirements-OFT-backend-search

Conversation

@Bronterrzel

Copy link
Copy Markdown

Open Fast Trace style requirements write up for backend search. As part of my bachelor's thesis.

Feedback or additional requirements i missed is appreciated.

Mandatory checks

  • I own the copyright of the code submitted and I license it under the MIT license
  • [/] I manually tested my changes in running JabRef (always required)
  • [/] I added JUnit tests for changes (if applicable)
  • [/] I added screenshots in the PR description (if change is visible to the user)
  • [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
  • [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

@palukku

palukku commented Sep 10, 2025

Copy link
Copy Markdown
Member

Looks like you forgot to add your changes to the commit (besides the submodules as already mentioned by the bot)?

@koppor

koppor commented Sep 12, 2025

Copy link
Copy Markdown
Member

Pleaee also include #840

@trag-bot

trag-bot Bot commented Sep 15, 2025

Copy link
Copy Markdown

@trag-bot didn't find any issues in the code! ✅✨

@jabref-machine

Copy link
Copy Markdown
Collaborator

Your pull request needs to link an issue correctly.

To ease organizational workflows, please link this pull-request to the issue with syntax as described in https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue:

Linking a pull request to an issue using a keyword

You can link a pull request to an issue by using a supported keyword in the pull request's description or in a commit message.

Examples

  • Fixes #xyz links pull-request to issue. Merging the PR will close the issue.
  • Fixes https://github.com/JabRef/jabref/issues/xyz links pull-request to issue. Merging the PR will close the issue.
  • Fixes https://github.com/Koppor/jabref/issues/xyz links pull-request to issue. Merging the PR will close the issue.
  • Fixes [#xyz](https://github.com/JabRef/jabref/issues/xyz) links pull-request to issue. Merging the PR will NOT close the issue.

`req~backend-search.field-search.field-contains~1`

Fields are searchable for contained words and sequences. Listing entries with the specified field which contains the searched word or sequence.
<!-- Inherent anyfield search is not a requirement, but a neat implementation feature. -->

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is covered by req~backend-search.field-search.pseudo-fields~1. Can be linked.

@koppor koppor added the status: changes-required Pull requests that are not yet complete label Dec 12, 2025
@koppor koppor mentioned this pull request Dec 17, 2025
1 task
@Siedlerchr Siedlerchr closed this Jan 27, 2026
@Siedlerchr

Copy link
Copy Markdown
Member

No work here since September

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: search status: changes-required Pull requests that are not yet complete

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants