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

Feature Request: Open Board File To Edit in Place #423

Open
immijimmi opened this issue Nov 21, 2023 · 1 comment
Open

Feature Request: Open Board File To Edit in Place #423

immijimmi opened this issue Nov 21, 2023 · 1 comment
Labels
enhancement New feature or request priority: low Low priority issue, nice to have implemented at some point but not urgent

Comments

@immijimmi
Copy link

Rather than importing a board, allow adding a reference to a board that serves only as a pointer to an external file.
Any changes made to the board in Kanri should be immediately reflected in that file, without requiring an export each time.
A board added to Kanri this way could be flagged as external in the boards list, to prevent confusion.

Rationale:
I'm trialing a workflow in which my issue tracking for any individual repository is handled by a Kanri board, the data for which is stored directly in that same repository. This allows it to benefit from all the advantages afforded by the combination of git/github (local control, versioning, cloud storage & collaboration etc.) and keeps it in the same place as the project it pertains to.
Unfortunately it can be a pain to repeatedly import/export boards to facilitate this, and there is potential for desync if some changes are made in Kanri and then mistakenly not exported before committing the file.

If this use case matches your view of how Kanri should be used, please consider adding this feature.

@trobonox
Copy link
Owner

Thanks for your suggestion. I have already thought of this idea and I think it's quite suitable for Kanri.

Unfortunately, this and some other changes would require me to write some custom backend logic for saving data, and I currently have barely any time to maintain this project so a change of that scope is out of the question.

I will put this on my backlog but no guarantees at all if and when this feature might be implemented.

@trobonox trobonox added enhancement New feature or request priority: low Low priority issue, nice to have implemented at some point but not urgent labels Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority: low Low priority issue, nice to have implemented at some point but not urgent
Projects
Status: Backlog
Development

No branches or pull requests

2 participants