Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #7115

Closed
Open
Created Jun 11, 2014 by Administrator@rootOwner

Issue/MR title markdown parsing issue

Created by: dblessing

Issue/MR titles support markdown. The problem is when the title ONLY contains something that is a link you can no longer navigate to that merge request. For example, we have JIRA as the issue tracker so anything like 'PROJECT-123' triggers markdown linking. I accidentally created an issue titled 'PROJECT-123'. In the merge request list I tried to click on the merge request and was instead taking to issue 'PROJECT-123'.

This can also be an issue if you put a merge request link in the title, like '!123'. Instead of going to the correct merge request you will be taken to merge request 123. This is probably not desired. I'm not sure markdown is needed in titles. Thoughts?

Assignee
Assign to
Time tracking