Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Issue status automatically changed to New

web-app

Hello. I hope you can help us with an odd problem we've just discovered in one of our projects.

 

We have several issues whose status had been set to something other than New (for example Closed or Awaiting) but now appears as New. These issues haven't been edited in at least several months but we've noticed the problem today. All the issues seem to belong to the same project. Here is an example of the history of one of the issues:

 

Date User Issue Changes 17/10/2006 03:35:27 Nathan Becker Fixed version changed to 6.1 Major Release (September 23, 2006) 17/10/2006 03:35:27 Nathan Becker Issue resolution changed to BOL 21/09/2006 09:51:47 Mateusz Majewski Issue status changed to Closed 12/09/2006 16:19:02 Mateusz Majewski Fixed version changed to 12/09/2006 16:19:02 Mateusz Majewski Issue status changed to Delivered 14/08/2006 10:08:01 Jakub Sus Assigned resource changed to Mateusz Majewski 14/08/2006 08:51:13 Jakub Sus Estimated days effort changed to 2 14/08/2006 08:51:13 Jakub Sus Percent complete changed to 100 14/08/2006 08:50:31 Jakub Sus Created

And yet the current status is New:

Issue Details   [Edit]  [Move]   [Copy]   [Delete] Issue ID BOL-1483 Type  Bug Priority  Major Visibility Public Assigned to Reported by Jakub Sus Component BOL Fixed For Version [6.1] 6.1 Major Release (October 14, 2006) Risk Level No Risk Status New Awaiting Estimated To be Ordered Ordered In Development Delivered Closed Hold Approved Rejected In Test Tested Successfully Input needed Ask for Estimation Ready for Test Deployment Test failure Update Resolution None BOL CBOL DEFAC FIDRI GIS Hakan Deleback ICS ref team NOFAC OIS ref team OMS Operations SEAPR SELOG SEROP USBFP USFAC USINY USINY001 USINY002 WMS ref team CAABB BOSS POL  Update

 

We are running version 2.0.5 and we have added several new Status types since these cases were created. I've looked at a few of the issues and I don't see anything obvious which they all have in common.

 

Is this a known bug?

PLABB
· 1
PLABB
Replies (4)
helpful
0
not helpful

Have you deleted the resource (actual user) for the issue?


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

Thank you for the reply. Yes, we did delete two users recently and they seem to have had the cases assigned to them currently or in the past.

 

We noticed this shortly after the team members left and their accounts were deleted so that's likely what happened... I suppose we should deactivate accounts instead of deleting them?


PLABB
· 1
PLABB
helpful
0
not helpful

Yes, in 2.2 you can deactivate an account.

However, you can change the delete user stored procedure (in 2.0.5) to not update the issue status.


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Thank you. That gives us a good reason to upgrade.


PLABB
· 1
PLABB