Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-5077

Crucible does not auto generate a Link To Issue Key when creating reviews from commits that have an issue key that is using a non-default project key pattern

XMLWordPrintable

      Lets say you want to create a review from a commit. You can do this two ways:
      1. JIRA issue source tab, click on Create Review button.
      2. Fisheye news feed, click on the Cogwheel icon on a commit and create Review.

      Crucible will automatically add a Link To.. option that helps the user to link back to the JIRA issue in the review. This does not work when that issue belongs to a project that has a custom project key pattern, e.g.:

      TBK2-10200

      This works normally if the project key pattern is the default JIRA one.
      No errors thrown in the logs for both JIRA and Fisheye.

      Tested on the follow sets of installations:
      -------------------------
      JIRA 6.0.8
      Fisheye Plugin 6.0.2
      FeCru 3.0.3
      -------------------------
      JIRA 6.1.6
      Fisheye Plugin 6.1.6
      FeCru 3.2.4

        1. 2014-02-27 17.38.bmml
          0.4 kB
        2. 2014-02-27 17.38.png
          2014-02-27 17.38.png
          19 kB

            [FE-5077] Crucible does not auto generate a Link To Issue Key when creating reviews from commits that have an issue key that is using a non-default project key pattern

            Mark Mielke added a comment -

            Also with transparency - the criteria you are using is entirely invalid:

            1. 10 major releases to solve a problem? The "Timed out" aspect is on Atlassian's ability to deliver, not on the request.
            2. Not gained interest? On issues with many votes, it's claimed that interest isn't the only criteria.

            As far as I am aware - this issue remains relevant. Did you try it before concluding anything here?

            The real conclusion here is that you don't want to look into this issue, and the above logic blames the users for what amounts to an Atlassian failing. I normally ignore these, as I understand that it's difficult to manage a roadmap with limited resources - but the Crucible roadmap has seemed pretty dead, and it feels disingenuous to see messages such as the above that try to dress up "Won't Fix" as-if the users are at fault here. In our case - we have been seriously reconsidering whether Crucible/FishEye should be part of our solution anymore given the extremely low trickle of features and bug fixes that Atlassian has been addressing.

            Mark Mielke added a comment - Also with transparency - the criteria you are using is entirely invalid: 10 major releases to solve a problem? The "Timed out" aspect is on Atlassian's ability to deliver, not on the request. Not gained interest? On issues with many votes, it's claimed that interest isn't the only criteria. As far as I am aware - this issue remains relevant. Did you try it before concluding anything here? The real conclusion here is that you don't want to look into this issue, and the above logic blames the users for what amounts to an Atlassian failing. I normally ignore these, as I understand that it's difficult to manage a roadmap with limited resources - but the Crucible roadmap has seemed pretty dead, and it feels disingenuous to see messages such as the above that try to dress up "Won't Fix" as-if the users are at fault here. In our case - we have been seriously reconsidering whether Crucible/FishEye should be part of our solution anymore given the extremely low trickle of features and bug fixes that Atlassian has been addressing.

            Marek Parfianowicz added a comment -
            Atlassian Update – 5 October 2018

            Hi everyone,

            This issue has been reported several years ago for a version which is already end of life and is over 10 major releases behind the latest Fisheye/Crucible version. Additionally, it has not get interest since the time it has been reported. Therefore, we decided to close the issue as Timed Out.

            If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments. We will continue to watch the issue for further updates.

            Cheers

            Marek Parfianowicz

            Fisheye/Crucible TL

            Marek Parfianowicz added a comment - Atlassian Update – 5 October 2018 Hi everyone, This issue has been reported several years ago for a version which is already end of life and is over 10 major releases behind the latest Fisheye/Crucible version. Additionally, it has not get interest since the time it has been reported. Therefore, we decided to close the issue as Timed Out . If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments. We will continue to watch the issue for further updates. Cheers Marek Parfianowicz Fisheye/Crucible TL

            Dmitry Podupeiko added a comment -

            Any updates!

            Dmitry Podupeiko added a comment - Any updates!

              Unassigned Unassigned
              dleng Daniel Leng (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: