Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !10658

Show sub-nav under Merge Requests when issue tracker is non-default

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Kushal Pandya requested to merge 30779-show-mr-subnav-issue-tracker into master Apr 12, 2017
  • Overview 15
  • Commits 7
  • Pipelines 3
  • Changes 12

What does this MR do?

When project has 3rd-party Issue tracker integration, clicking on Issues tab will directly take user to issue tracker page. Starting %9.0 we changed navigation order for Projects (see #26348 (closed)), where we removed sub-nav items from Merge Requests tab and showed them under Issues tab. In this case, user will never see sub-nav since page is redirected to 3rd-party issue tracker.

This MR restores sub-nav under Merge Requests when project has non-default Issue tracker (eg; JIRA, Bugzilla) integrated with the project. See #30779 (closed).

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • [ ] Documentation created/updated
  • [ ] API support added
  • Tests
    • [ ] Added for this feature/bug
    • All builds are passing
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Branch has no merge conflicts with master (if it does - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

Closes #30779 (closed)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 30779-show-mr-subnav-issue-tracker