In RTC 6.0.4 there is a new permission called Check-in (server) - what is this for?
![]() Hi there,
|
Accepted answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 31 '17, 2:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER I have confirmed with RTC development that this is a bug ... this permission is a no-op and should not be shown. Donna Thomas selected this answer as the correct answer
|
One other answer
![]()
Comments ![]() FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
These are the new server-side preconditions, and those are well documented.
Donna's question is about the new checkin permission. That is not documented, and it is unclear what function it performs. One would think it would allow/disallow checking in to a component, but according to my testing, it has no effect ... you can checkin without this permission being set for any of your roles.
I have tested regarding Restrict Check-in Based on Specified MIME Types and Encodings and this condition was working fine.
As Geoffrey wrote, I'm not looking at the new preconditions or any Operational Behavior. In the permissions, there is a new permission directly under Source Control in Team Permissions (as you can see in Eclipse). Literally just is named "Check-in (server)". That's what I'm talking about. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
Just FYI - I know what "checking-in" means - but the old permissions are still there and we could check-in then. We just want to know what this is giving (or not giving) permission to accomplish in the tool.
Hi Donna ... I'm checking with Dev ... please stay tuned ...