Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11511

Agile Sprint Health Gadget causes JQL Query Error for '@' character

      1) Create a dashboard and add and configure an Agile Sprint Health Gadget.
      2) Click on the avatar of a developer in the Agile Sprint Health Gadget.
      3) A JQL error is generated:

      assignee=first.last@company.com AND Sprint=209

      Error in the JQL Query: The character '@' is a reserved JQL character. You must enclose it in a string or use the escape '\u0040' instead. (line 1, character 18)

      Similar to GHS-10231, '@' needs to be escaped.

            [JSWSERVER-11511] Agile Sprint Health Gadget causes JQL Query Error for '@' character

            Aakrity Tibrewal made changes -
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Aakrity Tibrewal made changes -
            Labels Original: affects-server fixme pse-request New: affects-server cleanup-seos-fy25 fixme pse-request

            Atlassian Update - 10 April 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            Please note the comments on this thread are not being monitored.

            You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 10 April 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments; this inactivity suggests a low impact. Please note the comments on this thread are not being monitored. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Data Center
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Bugfix Automation Bot made changes -
            Minimum Version New: 6.03
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850443 ] New: JAC Bug Workflow v3 [ 2936504 ]
            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 [ 2545213 ] New: JAC Bug Workflow v2 [ 2850443 ]
            Status Original: Verified [ 10005 ] New: Gathering Impact [ 12072 ]
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0

              Unassigned Unassigned
              dd47ae87e874 Leroy Camel
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: