Long running import causes Gateway Time-out (504) error

[codescape]

If the data set is too big the import will run into a Gateway Time-out (504) on the browser side but the import will still continue and finish. This should be changed and the import should be implemented more robustly - for example will a long running task with the current results being reported by the GUI.

Tasks

• implement a Task using the https://docs.atlassian.com/software/jira/docs/api/9.16.0/com/atlassian/jira/task/TaskManager.html
• wait for the task to finish and show results

[codescape]

https://github.com/search?q=com.atlassian.jira.task.TaskManager&type=code

[codescape]

A dependency to jira-core is required:

    <dependency>
        <groupId>com.atlassian.jira</groupId>
        <artifactId>jira-core</artifactId>
        <scope>provided</scope>
    </dependency>

[codescape]

Maybe https://docs.atlassian.com/software/jira/docs/api/9.16.0/com/atlassian/jira/task/ImportTaskManager.html is a better choice?