Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-29353

Strange behavior when mention issue key in the comment

XMLWordPrintable

      If the jira.projectkey.pattern is set to "(([A-Z0-9]{0,5}-)?([0-9]{4})){1}", when adding the "issue key" in the the comment, it will return an output "project key""issue key".

      For example, if my project key is TEST-1234 and the issue key is TEST-1234-01. So, once the issue key is added in the comment it show up the text message "TEST-1234TEST-1234-01" as in the screen shot.

        1. comment_duplicate.png
          comment_duplicate.png
          20 kB
        2. Screen Shot 2012-08-15 at 5.16.20 PM.png
          Screen Shot 2012-08-15 at 5.16.20 PM.png
          76 kB

            [JRASERVER-29353] Strange behavior when mention issue key in the comment

            Ewelina Fiedorowicz made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]

            Ewelina Fiedorowicz added a comment -
            Atlassian Update – 22.07.2021

            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 resolve it as Time Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira 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 Bugfix Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Ewelina Fiedorowicz

            Ewelina Fiedorowicz added a comment - Atlassian Update – 22.07.2021 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 resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira 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 Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ewelina Fiedorowicz
            Bugfix Automation Bot made changes -
            Minimum Version New: 4.04
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2837150 ] New: JAC Bug Workflow v3 [ 2915275 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2567783 ] New: JAC Bug Workflow v2 [ 2837150 ]
            Status Original: Needs Verification [ 10004 ] New: Needs Triage [ 10030 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1533414 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2567783 ]
            Confluence Escalation Bot (Inactive) made changes -
            Support reference count New: 1
            Confluence Escalation Bot (Inactive) made changes -
            Support reference count Original: 3
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: comment pattern project_key New: affects-server comment pattern project_key

              Unassigned Unassigned
              yilinmo Yilin (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: