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

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

    • Icon: Bug Bug
    • Resolution: Timed out
    • Icon: Medium Medium (View bug fix roadmap)
    • None
    • 2016-04-18 Cloud
    • None
    • Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.87 Safari/537.36

    • Severity 2 - Major
    • Hide
      Atlassian Update – 11 October 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 – 11 October 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

      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.

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

            vboerner added a comment -

            having the similiar (maybe?)
            after changing the workflow (renames a status) - few people see the old status name. Meaning, they see the old statusname on the issue where I see the new status name. Even with cache cleared and even with different browser.

            vboerner added a comment - having the similiar (maybe?) after changing the workflow (renames a status) - few people see the old status name. Meaning, they see the old statusname on the issue where I see the new status name. Even with cache cleared and even with different browser.

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

                Created:
                Updated:
                Resolved: