`ejira-update-my-projects` should be asynchronous

[LeonardMH]

Running ejira-update-my-projects on a large Jira project completely consumes Emacs. One of the projects I work on has 20,000+ Jira issues, this command has been running for about 2.5 hours and isn't even 25% complete but Emacs has been unusable the whole time.

It would be a massive improvement if this update process could be done asynchronously so as to not block everything else Emacs is doing. Parallel execution would be a nice bonus since the Jira API is so slow, but I'm sure that's harder.

[nyyManni]

Thanks for the feedback.

I fully agree that for the sake of the user experience all the update commands should be asynchronous. That was something I considered when creating the jiralib2 library but left it for the future for simplicity's sake.

I currently do not have the free time to allocate for implementing it but will happily merge a pull request if someone else is willing to spend the effort.

For the time being, in your use case it could be beneficial to create a custom update function which would filter the issues based on the last modification date (I hope all 20k of the issues have not been touched within the last few months for example?)