In order to create a tracker from a Jira server, we need to make a bunch of REST calls to this server. Depending on the workload of the server, the number of issues to import, … it may takes too many time (either the request or the user can give up). This commit is an introduction for the full asynchronous process: * The jira information are stored in the database (token is stored symmetrically encrypted so that we can reuse it later) * The user is redirected to the list of all trackers * A feedback is displayed for tracker admins to warn them that there are pending trackers creation * It is not possible to create a tracker with same names than the Jira pending ones (old & new UI). That's all. The tracker will not be created for now. Next steps: - A cleanup will be done in database to remove pending jira that was not processed. - A background job will be introduced to consume the pending jira imports. This is hidden behind a feature flag. Please issue the following command in order to use it: tuleap config-set asynchronous_jira_creation 1 Reminder: with this setting, the tracker **will not be created**, it is here only for testing purpose. Part of story #14766: Have an import from jira structure Change-Id: I519ed6482dd313b893941caa38cb6e8562e473fa

+843 −29

Author

Nicolas Terray (nterray) 2020-05-12 19:48

Committer

Nicolas Terray (nterray) 2020-05-13 15:17

Hash 7e0ef83363f8c92c6caad0a294cd696b82017ef7

Parent ccb04c2217e351dc64e6cc3c216f1a30a4ef9ce2

Reference git #tuleap/stable/7e0ef83363f8c92c6caad0a294cd696b82017ef7