Add jira_imports table to track Jira imports
What does this MR do?
This table is to be used to track jira imports progress as well as some stats after the import is done.
As the intention is to allow multiple imports from different jira projects into a single gitlab project we want to be able to track the progress and the success/failure of each of the imports, as well as be able to present to the user a history of previous imports.
Given the above we cannot effectively use project_mirror_data and project_import_data as those have a 1-1 relationship with gitlab project.
more details on the context can be found at: &2766 (closed) and specifically #211660 (closed)
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team