Answers.Body: <p>Basically, you should reopen the original issue in JIRA once you have confirmed the problem is re-occuring in a later version than was fixed. Or if your account doesn't have the permission to do this in JIRA, leave a comment on the issue.</p>
  
  <p>Every issue in JIRA has a field that says which version of CiviCRM included the code developed to address it. Bugs might re-occur because only part of it was fixed, or the QA wasn't thorough enough, or more commonly some later change recreated the problematic behaviour somehow. </p>
  
  <p>Before reopening the issue, check that you can reproduce the error on the demo site, and make sure the behaviour matches the original bug description. </p>
  
  <p>If it seems a bit different, create a new issue and include a link to the old one in your description, saying why you think the bug is similar but not the same (this can save time for people working to fix the bug). </p>
  
  <p>If you're reasonably sure the bug is the same then reopen it, describe your experience including you site's version number, and indicate that you have reproduced the problem on the demo site. Note that you have to login to JIRA before you see the button to Reopen an issue:
  <img src="https://i.sstatic.net/DqQUk.png" alt="enter image description here"></p>
  
  <p>If you don't see the button, then just leave a comment:
  <img src="https://i.sstatic.net/mXwrt.png" alt="enter image description here"></p>
  
  <p>If an error was closed without being fixed because it couldn't be reproduced, you have an opportunity to assist even more. Try to take screen shots of the problem, and if possible, offer to do any testing the core team might request. This can involve checking a setting, examining a log file, or even putting in a debug statement. Rarely they might even benefit from accessing your system to investigate more thoroughly.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-25T03:33:37.143Z
Answers.Text: I cannot find a way to re-open the original issue, even if I am logged in
Answers.UserDisplayName: Vietyank
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-25T14:57:27.383Z
Answers.Text: Comment on the closed issue with the steps you have taken to ensure that the issue still exists on the latest version. i.e. testing on the latest version on the demo servers
Answers.UserDisplayName: Donald Lobo
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-26T23:59:37.613Z
Answers.Text: The demo server for Joomla is running 4.6.0. The issue was said to have been fixed in 4.6.1
Answers.UserDisplayName: Vietyank
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-27T02:34:55.930Z
Answers.Text: Is the issue Joomla specific? If so, maybe post a comment indicating you would like the Joomla demo site upgraded on the issue
Answers.UserDisplayName: Joe Murray
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-25T00:47:39.947Z
Answers.LastActivityDate: 2015-05-25T15:11:38.943Z
Answers.LastEditDate: 2015-05-25T15:11:38.943Z
Answers.UserDisplayName: Joe Murray
Answers.Body: <p>I suggest opening a new issue if you don't have permission to re-open the closed one - with adequate links to the closed one.</p>
  
  <p>Commenting on the closed issue might be noticed or it might not - but if not noticed straight away then it will be back off the radar.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-25T22:35:21.210Z
Answers.Text: Dave Greenberg said that because he and Kurund and Coleman all monitor JIRA comments as well as issues that it was fine to post a comment asking for issue to be reopened rather than creating new issue.
Answers.UserDisplayName: Joe Murray
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-25T22:32:40.720Z
Answers.LastActivityDate: 2015-05-25T22:32:40.720Z
Answers.UserDisplayName: eileen
Body: <p>What should I do if an issue is marked as fixed in JIRA for a particular version, but it is still occurring in a later version?</p>
  
Tags: <issues>
Title: What should I do if an issue is marked as fixed in JIRA but it is still occurring?
ThreadText: # What should I do if an issue is marked as fixed in JIRA but it is still occurring?
  
  (Asked by: username_0 on 2015-05-25)
  
  What should I do if an issue is marked as fixed in JIRA for a particular version, but it is still occurring in a later version?
  
  **Tags:** issues
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2015-05-25. Score: 8
  
  Basically, you should reopen the original issue in JIRA once you have confirmed the problem is re-occuring in a later version than was fixed. Or if your account doesn't have the permission to do this in JIRA, leave a comment on the issue.
  
  Every issue in JIRA has a field that says which version of CiviCRM included the code developed to address it. Bugs might re-occur because only part of it was fixed, or the QA wasn't thorough enough, or more commonly some later change recreated the problematic behaviour somehow.
  
  Before reopening the issue, check that you can reproduce the error on the demo site, and make sure the behaviour matches the original bug description.
  
  If it seems a bit different, create a new issue and include a link to the old one in your description, saying why you think the bug is similar but not the same (this can save time for people working to fix the bug).
  
  If you're reasonably sure the bug is the same then reopen it, describe your experience including you site's version number, and indicate that you have reproduced the problem on the demo site. Note that you have to login to JIRA before you see the button to Reopen an issue:
  ![enter image description here](https://i.sstatic.net/DqQUk.png)
  
  If you don't see the button, then just leave a comment:
  ![enter image description here](https://i.sstatic.net/mXwrt.png)
  
  If an error was closed without being fixed because it couldn't be reproduced, you have an opportunity to assist even more. Try to take screen shots of the problem, and if possible, offer to do any testing the core team might request. This can involve checking a setting, examining a log file, or even putting in a debug statement. Rarely they might even benefit from accessing your system to investigate more thoroughly.
  
  > **Comments:**
  > **username_1**: I cannot find a way to re-open the original issue, even if I am logged in  
  > **username_2**: Comment on the closed issue with the steps you have taken to ensure that the issue still exists on the latest version. i.e. testing on the latest version on the demo servers  
  > **username_1**: The demo server for Joomla is running 4.6.0. The issue was said to have been fixed in 4.6.1  
  > **username_0**: Is the issue Joomla specific? If so, maybe post a comment indicating you would like the Joomla demo site upgraded on the issue  
  
  ---
  
  ### Answer by username_3 on 2015-05-25. Score: 1
  
  I suggest opening a new issue if you don't have permission to re-open the closed one - with adequate links to the closed one.
  
  Commenting on the closed issue might be noticed or it might not - but if not noticed straight away then it will be back off the radar.
  
  > **Comments:**
  > **username_0**: Dave Greenberg said that because he and Kurund and Coleman all monitor JIRA comments as well as issues that it was fine to post a comment asking for issue to be reopened rather than creating new issue.  
  
  ---
  
  