[Bug in the code] Failure in qa/specs/features/browser_ui/2_plan/issue/jira_issue_import_spec.rb:17
Summary
Failure in qa/specs/features/browser_ui/2_plan/issue/jira_issue_import_spec.rb:17
. Started to fail in https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/pipelines/194436852.
Update: Failure presumably casued by !43318 (merged) by looking into comparison 998f8f873d50290ddb3ed0d73dd0be9ab48c5c9e...bcc3eddf245af933cca06fe1b562ad8040eaf6ce
Problem: When users try to import issues from Jira, they're not being redirected to "Import in progress" page and import finishes silently (see #255929 (comment 418830075) for full details) :
Screen_Recording_2020-09-25_at_17.28.27
Failed jobs:
- https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/757293318
- https://gitlab.com/gitlab-org/gitlab-qa-mirror/-/jobs/757455652
Stack trace
1) Plan Jira issue import imports issues from Jira
Failure/Error: expect(page).to have_content("Import in progress")
expected to find text "Import in progress" in "Skip to content GitLab Projects Groups More Help J jira_issue_import-acef30f19475bda2 Project overview Issues 0 Jira Merge Requests 0 Requirements CI / CD Security & Compliance Operations Packages & Registries Analytics Wiki Snippets Members Settings Collapse sidebar gitlab-qa-sandbox-group qa-test-2020-09-25-12-44-29-7fc4f134ad33ae20 jira_issue_import-acef30f19475bda2 gitlab-qa-sandbox-group / qa-test-2020-09-25-12-44-29-7fc4f134ad33ae20 / jira_issue_import-acef30f19475bda2 New Jira import Import from Jira Import Test Data (JITD) Jira Integration Test Project (JITP) Issue label jira-import KEY-1 Jira-GitLab user mapping template Jira users have been imported from the configured Jira instance. They can be mapped by selecting a GitLab user from the dropdown in the \"GitLab username\" column. When the form appears, the dropdown defaults to the user conducting the import. Jira display name GitLab username gitlab-qa root Continue Cancel"
# ./qa/specs/features/browser_ui/2_plan/issue/jira_issue_import_spec.rb:73:in `import_jira_issues'
# ./qa/specs/features/browser_ui/2_plan/issue/jira_issue_import_spec.rb:19:in `block (3 levels) in <module:QA>'
# /usr/local/bundle/gems/rspec-retry-0.6.1/lib/rspec/retry.rb:123:in `block in run'
Screenshot / HTML page
Possible fixes
Edited by Nailia Iskhakova