Project Archive
Hi,
While working with JKE sample project, I thought to create one more time JKE sample project. So I archived the JKE Banking and renamed to JKE banking1(in all QM,RM,CM). Now I created the sample JKE Banking Again.
No Issues.
Now when i see the the personal Dashboard of Bob or ursula, I can see that they are still pointing to JKE Banking1 project(which is the archived project). I have to change this manually by goiing to Menu-Settings-Select the right prject (JKE banking) in each Widget.
So the question is what could be best Practce to Archive the project? or is it a bug in JKE banking. Because when you archived the project normally all the existing users of tht projects are still exists. and when you create the same JKE Banking project, it just check whether the users are exists or not but does not check the users are belongs to which (old or new) project.
While working with JKE sample project, I thought to create one more time JKE sample project. So I archived the JKE Banking and renamed to JKE banking1(in all QM,RM,CM). Now I created the sample JKE Banking Again.
No Issues.
Now when i see the the personal Dashboard of Bob or ursula, I can see that they are still pointing to JKE Banking1 project(which is the archived project). I have to change this manually by goiing to Menu-Settings-Select the right prject (JKE banking) in each Widget.
So the question is what could be best Practce to Archive the project? or is it a bug in JKE banking. Because when you archived the project normally all the existing users of tht projects are still exists. and when you create the same JKE Banking project, it just check whether the users are exists or not but does not check the users are belongs to which (old or new) project.
One answer
Hi Manoj,
what I do is manage my several test environments with a small software that essentially backs the derby DB and other stuff up. I usually have a starting point that I use if I need a fresh environment.
What you discover could be an issue with the JKE sample. You could create a work item. Since JKE is not meant to be a for production usage, I am not sure what the priority would be.
what I do is manage my several test environments with a small software that essentially backs the derby DB and other stuff up. I usually have a starting point that I use if I need a fresh environment.
What you discover could be an issue with the JKE sample. You could create a work item. Since JKE is not meant to be a for production usage, I am not sure what the priority would be.