Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 380
    • Issues 380
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2076
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Issue Tracker Integration is broken in 1.8.7.0

By andrew.nefed... on January 21, 2014 14:44 (imported from Google Code)


What steps will reproduce the problem?

  1. Configure issue tracker (i.e. Gurtle or JiraSVN) for some common parent directory.
  2. Have a repository in a hierarchy beneath that folder.
  3. Open commit dialog.

What is the expected output? What do you see instead?
Issue tracker's button in the upper right cornet of the dialog. But there is no.

What version of TortoiseGit and msysgit are you using? On
what operating system?
1.8.7.0

Please provide any additional information below.
I suppose the problem is caused by the revision b659814e after which project properties are no more read recursively. But it is very frustrating to configure issue tracker for each repository individually - we have dozens of them at work but only a single issue tracker (JIRA) with a common configuration.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking