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

Linked Issue does not check for invalid/non-existent JIRA issue keys

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • N/A
    • 2.10.0, 2.10.1
    • None

      If a Crucible review comment contains a text like "JA-1", it will be displayed as a "Linked Issue" under the review details, irrespective of whether this is an actual JIRA issue key or not.
      Even if there is an entity link configured between a JIRA and crucible project and the propertyies "Disable for unmapped JIRA Projects" and "Force Project Mappings" has been set to "ON" in JIRA, the "Linked Issue" is still being displayed.
      The actual text in the comment is also considered to be a JIRA link by default.
      There appears to be no check in place to confirm the validity of the linked issue.
      Screenshot attached.

        1. Screen Shot 2013-02-07 at 9.47.48 AM.png
          Screen Shot 2013-02-07 at 9.47.48 AM.png
          42 kB
        2. Screen Shot 2013-02-07 at 9.48.31 AM.png
          Screen Shot 2013-02-07 at 9.48.31 AM.png
          267 kB

            [FE-4487] Linked Issue does not check for invalid/non-existent JIRA issue keys

            Marek Parfianowicz added a comment -
            Atlassian Update – 31 January 2020

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.

            We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details.

            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 and vote on it. We will continue to watch the issue for further updates.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 31 January 2020 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it. We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details. 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 and vote on it. We will continue to watch the issue for further updates. Kind regards Marek Parfianowicz Development Team Lead

            ckline added a comment -

            Sten,

            Would it be possible for users to configure a list of prefixes that are to be considered valid Jira projects, and only link if the text matches one of those prefixes?

            For example, if I set up the list as:

            • "ProjectX"
            • "Internal-Dev"

            then Crucible would link twice in this sentence

            "This needs to be addressed for issues ProjectX-1234 and Internal-Dev-456"

            but not in this sentence

            "I think this made it into branch Shipping-1.2"

            That would be an acceptable solution for us and, I believe, could be made a performant one.

            ckline added a comment - Sten, Would it be possible for users to configure a list of prefixes that are to be considered valid Jira projects, and only link if the text matches one of those prefixes? For example, if I set up the list as: "ProjectX" "Internal-Dev" then Crucible would link twice in this sentence "This needs to be addressed for issues ProjectX-1234 and Internal-Dev-456" but not in this sentence "I think this made it into branch Shipping-1.2" That would be an acceptable solution for us and, I believe, could be made a performant one.

            Sten Pittet (Inactive) added a comment -

            This is a known limitation of the FishEye / JIRA integration. I've created https://jira.atlassian.com/browse/FE-4497 to make sure it is documented.

            I'll open this issue but solving it will not be trivial as it can be a performance issue if we have to do a look up on JIRA instances with a large number of issues. We had to do a tradeoff and the consensus was that this implementation would generate far more benefits.

            Regards,

            Sten

            Sten Pittet (Inactive) added a comment - This is a known limitation of the FishEye / JIRA integration. I've created https://jira.atlassian.com/browse/FE-4497 to make sure it is documented. I'll open this issue but solving it will not be trivial as it can be a performance issue if we have to do a look up on JIRA instances with a large number of issues. We had to do a tradeoff and the consensus was that this implementation would generate far more benefits. Regards, Sten

              Unassigned Unassigned
              ganand Gurleen Anand [Atlassian]
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: