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

Inconsistent function of @ mention of team member in comments and description, similar to Confluence shortcut.

    XMLWordPrintable

Details

    • Severity 3 - Minor
    • Hide

      Atlassian Update – 04 July 2019

      Hi everyone,

      After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out.

      Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy.

      To see what the Jira team is currently working on and has recently delivered see the following dashboards:

      We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments.

      Thank you,

      Pawel Drygas,

      Jira Server Bugmaster

      Show
      Atlassian Update – 04 July 2019 Hi everyone, After reviewing the overall customer interest and impact of this bug report we have decided to close this issue down. Our analysis has shown that over time this issue hasn't collected a significant number of votes, watchers, comments, or support cases from customers and therefore has remained very low on our priority list. Given these findings we can conclude it will not be fixed in the foreseeable future and wish to be transparent about our priorities by closing it as Timed Out . Although we're aware this issue may be still important to those of you who were involved in the initial conversations around it, we want to be clear by managing your expectations regarding the likelihood of a fix for it. The Jira team do their best to prioritise the issues that have high and critical impact with broad pervasiveness reflected in series of different factors. You can learn more about this by reading our Bug Fixing Policy . To see what the Jira team is currently working on and has recently delivered see the following dashboards: Jira Server and Data Center: Recently resolved issues Jira Server and Data Center: Current work and future plans Jira Server and Data Center: Bug Fix Board We understand that hearing a decision like this can be disappointing, but we hope you'll appreciate our transparent approach to product priorities and communications. We will continue to watch this issue for further updates, so please feel free to share any thoughts in the comments. Thank you, Pawel Drygas, Jira Server Bugmaster

    Description

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      This functionality seems to work sometimes work but

      a) Does not always echo back the same way it does in confluence. As I recall, sometimes you can type in the @ and your team list will appear and echo what you type, sometimes nothing appears, but when you type @teammember and save the issue the link shows up.
      b) In some contexts nothing happens at all, either when you type the @ or when you try to type @teammember and save. No dice.

      To be honest, I'm not exactly sure how often it's working, just know it doesn't always work, leading me to pull hair. (Well, kinda)

      It would be most helpful if this functionality worked from every issue comment view, including:

      • Workflows,
      • Edit issue,
      • Full issue page,
      • Green Hopper commenting

      There are many ways you can comment, and IMHO they should all behave the same way, or your users will be required to avoid certain forms in favor of the ones that work right.

      I get so used to typing @ in Confluence that it bums me out when nothing happens in Jira. And then when it appears to work sometimes and not others, it's a bit crazy making.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-31265 Inconsistent function of @ mention of team member in comments and description, similar to Confluence shortcut.

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              00b9bfc6b515 Hope Foster-Reyes
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: