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] Show info "Documents to be processed" #1069

Closed
monnypython opened this issue Sep 14, 2021 · 1 comment · Fixed by #1167
Closed

[Feature Request] Show info "Documents to be processed" #1069

monnypython opened this issue Sep 14, 2021 · 1 comment · Fixed by #1167
Labels
webui WebUI issues

Comments

@monnypython
Copy link
Contributor

If I import some documents via the webui and then continue working with other documents (waiting for new documents from queue), it would sometimes be helpful to see how many documents still need to be processed without having to look in the "processing que". So you would not have to interrupt the current other tasks and could continue with the new documents e.g. if the marker is no longer visible.

This could be a small mark on the gear symbol, for example. At best with the number of items still to be processed.

image

@eikek
Copy link
Owner

eikek commented Sep 30, 2021

Hi @monnypython , sorry for some reason I missed this issue. You're right - this would be a nice addition. The whole "processing" topic (ui wise) must be improved. It is still in its very first version :). There is an issue for this already (not that specific, just fyi): #596.

@eikek eikek added the webui WebUI issues label Nov 6, 2021
@eikek eikek added this to the Docspell 0.29.0 milestone Nov 6, 2021
eikek added a commit that referenced this issue Nov 12, 2021
eikek added a commit that referenced this issue Nov 12, 2021
@mergify mergify bot closed this as completed in #1167 Nov 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
webui WebUI issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants