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
  • #36495

Closed (moved)
Open
Opened Aug 15, 2017 by Martin@MRentschler0 of 3 tasks completed0/3 tasks

Validate against trailing spaces in Jira Username configuration

Description

Trying to integrate gitlab with jira I was scratching my head on why it didn't run (w/o any sensible information in neither the logs nur the ui after performing a test). Turns out you can enter trailing spaces in the Username field and gitlab doesn't sanitize the input unlike it does seem to perform for the project key.

Proposal

Sanity check Username input the way the Project key already seems to be.

Links / references

Documentation blurb

Overview

What is it? a minor change Why should someone use this feature? If they are dumb like me. What is the underlying (business) problem? Sanity check, UI feedback. How do you use this feature? angrily.

Use cases

People who have to use Jira because they can't have gitlab web-exposed (and can't afford all the additional licenses) and who can't risk having customers accessing code.

Feature checklist

Make sure these are completed before closing the issue, with a link to the relevant commit.

  • Feature assurance
  • Documentation
  • Added to features.yml
Edited Aug 17, 2017 by Mark Fletcher
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#36495