We disabled all of the Rewards User Badges, but I noticed that the Give Badge button still appears on all profiles for all users regardless of permissions. Is it possible to disable this button?
I started a case on mine after failing to find an admin panel solution. Turns out it's a bug: PBOX-1979. Sorry I forgot to come here and post that in this thread after I got the news.
The tech support analyst helping me says, " This is a sev1 issue so it should be fixed when our patch rolls out. If not I will let ou know before hand." I dunno when patches go out, but I "think" that means in the "maintenance updates." Could be wrong about that, but searching for a schedule for patches didn't reveal anything.
Did you ever get this figured out? If so, how? I don't use Jive Rewards, but that "give a badge" option is showing up anyway. I must have something enabled that I don't want.
Hi Frank, unfortunately no - it appears that the button just continues to show even when the "give a badge" feature is disabled.
Is this a correct assumption, Curtis Gross?
Frank - thanks for the follow up. A sev 1 would indeed be fixed within a maintenance release.
Hi Curtis --
We received the 2016.2 Jive-x production upgrade this weekend and PBOX-1979 is not resolved.
Possibly not in the works until the maintenance update?
We got a little feedback that it's been solved on a case-by-case basis for some clients, but not yet across the board. Awaiting another update.
Sorry Paul, I think my phrasing to you was misleading. I didn't mean we're solving it on a per customer basis. I meant that we solved the issue where it was originally reported - giving a badge in the content text editor - but then saw it also cropped up on the Give a Badge in actions menu, and in the profile. We had a separate bug open for that, and my QE team tells me it's validated as fixed, so I'm surprised you're still seeing the bug. I asked one of the engineers to look specifically there, to see what might be happening. I'll follow up with you for more info in the other case.
Still seeing it in our instance, too.
Do you have a support case open for this? Would like to get more info from you. In our testing we aren't seeing this happen anymore, and you should have gotten the fix, but I want to find out if it only occurs under certain circumstances.
Here it is:
Retrieving data ...