Loading Profile...
hidden columns return after relaunch
when I close the program completely and then relaunch it, all the columns i'd previously hidden are again visible
I’m happy
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from the company
-
This fix has been released to the main build. You can download that here:
http://worklogassistant.com
Thanks again!
I’m happy
The company says
this solves the problem
-
Inappropriate?Hm, I can't reproduce this. However, there is some cases in which custom fields may show up *if* a custom field is added. In this case, it is not always possible to tell what has changed so all the columns reappear. Do you know if this is the case for you?
I’m happy Eric is happy
4 Comments Add a comment
This solves the problem
-
We're seeing the case you're mentioning where columns reappear after we add new custom fields. We have some new execs who are adding fields one or two a day and it's a drag given our 108+ fields to delete the ones we don't want again and again. Is there anything we can do differently to keep this from happening? -
Hmm, I don't think there is something you can do. I can see how it can be very annoying with 108+ custom fields. I will definitely try and get something for this in the next release. I'm pretty sure I should be able to catch this case and do *something* better than the current situation.
Sorry for the inconvenience. -
So, if you can tell the state the field was in before, then setting it to that state again preserves the query. If you hide unknown ones by default, then things look the same, but the user may not know there are new fields. If you turn them on by default, the user may have to go turn them off. I think I prefer "on if on before, otherwise off if off before or new".
Does that make sense? I think that's what you're saying in response to Eric, below. -
Yep, makes sense. I think the 3 of us are saying the same thing.
-
Inappropriate?what about hiding ALL custom field by default and then adding as needed?2 Comments Add a comment
This solves the problem
-
I think I may be able to determine what has changed. Specifically, I'm thinking that if the above case is detected, go through the new fields and determine if there are any existing fields that also existed previously. Make those visible and that is the sensible thing to do.
-
Seems like that's what you are saying. I'll try to do that.
-
Inappropriate?Hi there, I've posted a solution for this problem on the beta site. You can download it here:
http://next.worklogassistant.com
Thanks! -
Inappropriate?This fix has been released to the main build. You can download that here:
http://worklogassistant.com
Thanks again!
I’m happy
The company says
this solves the problem
EMPLOYEE
