Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-13663

Wrong status of JIRA Issues displayed when they are mentioned in JIRA Issue comments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Medium Medium
    • Classic - Boards

    • Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36

      Recently a feature to display mentioned issues status and summary has been added to JIRA, that's cool.

      But this feature has a bug. The displayed status is wrong, does not match the actual status of the issue.

      Examples:

      • Actual: DONE (green fill), Displayed: COMPLETE (green outline)
      • Actual: READY FOR RELEASE (yellow fill), Displayed: IN PROGRESS (yellow outline)
      • etc.

      See the attached screenshot as a proof.

      Please contact me if you need any details. Sorry if this issue has already been reported, I could not find it.

        1. jira-comment-wrong-status-1.png
          jira-comment-wrong-status-1.png
          8 kB
        2. jira-comment-wrong-status-2.png
          jira-comment-wrong-status-2.png
          37 kB

            [JSWCLOUD-13663] Wrong status of JIRA Issues displayed when they are mentioned in JIRA Issue comments

            Dylan added a comment -

            Hi,

            This bug has been closed as "Won't Fix" due to inactivity - the last update was over 2 years ago.

            If this issue is still occurring please add a comment or contact our support team to re-verify.

            Cheers,
            Atlassian Support

            Dylan added a comment - Hi, This bug has been closed as "Won't Fix" due to inactivity - the last update was over 2 years ago. If this issue is still occurring please add a comment or contact our support team to re-verify. Cheers, Atlassian Support

              Unassigned Unassigned
              78d4be004f92 sompylasar
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: