Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-6981

Issue-Links from Repository Log to JIRA is sometimes wrong

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We're running Stash & JIRA in our Company and usually committing Changes with a JIRA Issues Key within the Commit-Message to display the Issue within the Repository Log view.

      However Stash seems to thread anything like "abc-1" or "OPS-665" as a regular JIRA Issue. This however isn't always true as we've done a lot of Commits like "Update Coding Style to be PSR-2". Stash does actually thread "PSR-2" as an Issue and links that to JIRA. There isn't even a project on JIRA which is called "PSR" (and therefor no such Issue Key).

      It'd be nice if Stash could fire a Lookup in JIRA if there's a project (or even an issue) before setting such a link on the web. It's not a major Problem, however our Product-Owners/Project-Managers do get confused by this behavior from time to time.

            Unassigned Unassigned
            47702ae9eb64 Peter Kühn
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: