Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Customized general fields are not imported #7147

Closed
1 task done
jpschneiders opened this issue Dec 1, 2020 · 1 comment
Closed
1 task done

Customized general fields are not imported #7147

jpschneiders opened this issue Dec 1, 2020 · 1 comment
Labels

Comments

@jpschneiders
Copy link

jpschneiders commented Dec 1, 2020

JabRef version JabRef 5.2--2020-12-01--706865f on Windows 10

Steps to reproduce the behavior:

  1. Export preferences with customized general fields from a JabRef instance.
  2. Import these preferences (an example is joined to this report as text file 2020_Pref_Jabref.txt ) in a new JabRef instance.
  3. The customized general fields are not imported along the other customizations.
@github-actions
Copy link
Contributor

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

  • If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
  • Provide further steps or information on how to reproduce this issue.
  • Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
  • If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

@github-actions github-actions bot added the status: stale Issues marked by a bot as "stale". All issues need to be investigated manually. label May 31, 2021
@koppor koppor moved this to Done in Prioritization Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants