Skip to main content
Question

JSS 9.96 Policies Web View

  • September 27, 2016
  • 13 replies
  • 56 views

Forum|alt.badge.img+12
  • Valued Contributor

I recently upgraded from Casper 8.72 to 9.96. One thing I have noticed is that every time I go back to the main Policies page all of the policy groups are expanded. In the old version I set them to hidden and they would stay grouped by default. Even if I manually choose hide and then reload the page they revert back to the "show all" view.

Anyone else running into this or have figured out a way to get the old defaults back?

13 replies

Forum|alt.badge.img+20
  • Valued Contributor
  • September 27, 2016

Hi @tomt, yes, I am seeing this as well. I haven't been able to set it back to hide and this is a very annoying problem that needs to be fixed. The constant jumping back and forth is a real time waster.


mm2270
Forum|alt.badge.img+24
  • Legendary Contributor
  • September 27, 2016

As far as I recall, this has been a problem for a while, though in reverse, for me. For example, I can go into Policies right now on our 9.82 JSS, expand all policy categories, or just a subset. Clicking off the Policies page and jumping back in shows all policy categories now collapsed again. Meaning, in my case, it doesn't remember my last setting of having certain (or all) policy categories expanded. So either way, this has never really worked reliably. At least not in my experience.

Though to be fair, it sounds like the problem as it is now would be more annoying than it was previously. Better to have them re-collapse than to have them all expanded I guess.

Edit: I partially take back my comment. It only seems to recollapse the categories under certain circumstances, not every time. I see it happen kind of randomly. Sometimes it retains the view, and other times it just reloads them in a default all closed state. So at best its inconsistent in the older releases. Not sure why, but wanted to just correct my statement for the record.


Forum|alt.badge.img+17
  • Contributor
  • September 27, 2016

Hi @tomt , @mconners , & @mm2270 ,

We're aware of this issue and have it filed as PI-002788.

If you don't already have a case open with your TAM, and would like to open one to have attached to the above PI, please get in touch with them either by giving them a call, sending an e-mail to support@jamfsoftware.com, or by using the My Support section of JAMF Nation.

Thanks!
Amanda Wulff
JAMF Support


Forum|alt.badge.img+12
  • Author
  • Valued Contributor
  • September 27, 2016

Thanks @amanda.wulff , I had myself added to the PI.

Tom


Forum|alt.badge.img+12
  • Author
  • Valued Contributor
  • January 24, 2017

I don't see it listed in the release notes, was this fixed in 9.97?


Forum|alt.badge.img+7
  • Contributor
  • February 1, 2017

@tomt This is still an issue that has not been resolved in 9.97x


Forum|alt.badge.img+12
  • Author
  • Valued Contributor
  • February 1, 2017

Disappointing...


Forum|alt.badge.img+12
  • Author
  • Valued Contributor
  • February 3, 2017

@amanda.wulff Any update on this issue? It's been four months and this seems to be a fairly simple thing to fix.


Forum|alt.badge.img+17
  • Contributor
  • February 3, 2017

@tomt

There are no updates on this issue. When the product issue mentioned earlier is resolved, it will show in our release notes.

Thanks!
Amanda Wulff
Jamf Support


Forum|alt.badge.img+11
  • Contributor
  • February 9, 2017

Forum|alt.badge.img+12
  • Author
  • Valued Contributor
  • May 23, 2017

So 9.99 just dropped. I read through the bug fixes (yes, I consider this a bug since I can't see any possible reason it would have been a conscious decision) and no mention of it.

Can anyone confirm if this has been fixed in 9.99?

Thanks


Forum|alt.badge.img+17
  • Contributor
  • May 23, 2017

@tomt

We make every effort to include everything fixed in the release notes; if you do not see PI-002788 listed in the release notes, that means that it has not been fixed in the release in question.

Thanks!
Amanda Wulff
Jamf Support


Forum|alt.badge.img+9
  • Contributor
  • May 24, 2017

Shame this is is not resolved ( PI-002788 ) - it's a real pain…