Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #37212

Closed (moved)
Open
Opened Aug 29, 2017 by Victor Wu@victorwuContributor

Auto test settings upon saving JIRA settings fix

Summary

The flow implemented in https://gitlab.com/gitlab-org/gitlab-ce/issues/31511 is not working for some cases. Specifically when the Jira API Url is not reachable

Steps to reproduce

  1. Go to the Jira integration page
  2. Fill in some data - make sure you fill a url that is not reachable (eg. https://test.example.com) into Jira API url (or you can fill the url in Web Url and leave Api url empty)
  3. Click "Test settings and save changed"

What is the current bug behavior?

The error "Something went wrong on our end" appears

What is the expected correct behavior?

The message "Test failed. Save anyway." should appear. A user still should have the possibility to save the configuration after the test fails.

Relevant logs and/or screenshots

https://sentry.gitlap.com/gitlab/gitlabcom/issues/43510/

Possible fixes

We rescue multiple exception in https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/models/project_services/jira_service.rb#L297 . We could add the SocketError exception to the list.

Original Description

The flow implemented here: https://gitlab.com/gitlab-org/gitlab-ce/issues/31511

is no longer working. In talking with @jarka , it was working prior at some point, but now we have the following:

Screen_Shot_2017-08-29_at_16.09.45

It should be

02-error-message-v4

The scope of this issue is to reimplement the requirements here: https://gitlab.com/gitlab-org/gitlab-ce/issues/31511.

Edited Nov 28, 2017 by Victor Wu
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#37212