Levi, That is a valid defect and is associated to hierarchical groups, it's open and listed as 'in progress'
On Thu, Feb 7, 2019 at 8:30 PM Lippincott, Levi (OMA-GIS) < levi.lippinc...@interpublic.com> wrote: > Radhika, > > > > I’m unable to find the defect now, I just emailed back on my support > ticket to find out what’s going on and if they gave me the wrong defect ID, > when I hear back I’ll let you know. > > > > I’ll share the case details I opened. > > > > *Subject*: Parent Group Members Unable to Modify Tickets for Child Groups > > > > *Description*: We setup a Parent Group following the instructions here: > https://docs.bmc.com/docs/ars91/en/using-a-parent-group-for-permissions-inheritance-609073717.html > > And then here: > https://docs.bmc.com/docs/ars91/en/controlling-access-to-requests-for-hierarchical-groups-609073689.html#Controllingaccesstorequestsforhierarchicalgroups-82480 > > This is on the HPD:Help Desk form. Members of the Parent Group are unable > to modify tickets without receiving this error: > > "You do not have the authority to modify incident, """INC000003459208""". > You must be a member or an associate member of either the owner group > (<group name>) or the assigned group (<group name>). (ARERR 1291018)" > > > > > > We went back and forth on this for a while until they realized the Parent > Groups permissions were not effectively trickling down like the > documentation says it should and they were going to fix it for 19.02. > > > > I’ll send an update once I hear back from BMC. > > > > Levi > > > > > > *From:* ARSList <arslist-boun...@arslist.org> *On Behalf Of *Narayanan, > Radhika > *Sent:* Thursday, February 7, 2019 9:06 PM > *To:* ARSList <arslist@arslist.org> > *Subject:* [EXTERNAL] RE: Question about parent groups > > > > Hi, > > > > Can you please share the description of defect id SW00552883 on parent > groups? > > > > *Thanks* > > *Radhika * > > > > *From:* ARSList <arslist-boun...@arslist.org> *On Behalf Of *Lippincott, > Levi (OMA-GIS) > *Sent:* Thursday, February 7, 2019 5:03 AM > *To:* ARSList <arslist@arslist.org> > *Subject:* Re: Question about parent groups > > > > Parent Groups are not working the way they are supposed to there is an > open defect on this I reported and is being worked on. > > > > SW00552883 > > > > I'm told it will be resolved in 19.02. > > Sent from my iPhone > > > On Feb 6, 2019, at 5:23 PM, Fawver, Dustin <faw...@mail.etsu.edu> wrote: > > LJ, > > > > I had not considered that because I’m not at all familiar with it. I was > concerned at the time about having to update the group names on user > profiles (a custom form), “Assigned to Group” field on tickets, string > values in workflow and such. I didn’t want things to break. Amazingly > enough, nothing broke, aside from these field accessibility issues. As of > now, I’m getting around this issue by adding folks to the old group. > Management would like for those old names to be removed as soon as I can > find a feasible way of doing so. > > > > Another factor that came into play is that when these groups were created > eons ago, their group IDs were < 1000. That range is now in the BMC > restricted airspace. I felt it best to have the new group IDs within the > acceptable range. I was thinking that if I also changed the group IDs for > the old groups as well as the names, that would definitely meant having to > touch the forms. > > > > I hope this makes sense. > > Thanks! > > Dustin Fawver > > Sr. Help Desk Technician > > Information Technology Services > > > > P: 423-439-4648 > > itsh...@etsu.edu > > <image001.png> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.etsu.edu_helpdesk&d=DwMGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=DnVIGSEzlRIXfZATPlRnwApWkmEhQz97sCzMg1WKoKg&m=EJizdLriltgwcJGGOBPJTIx6r4MedvpoG1DOjrE2nhA&s=WcPcmh2UObHoPsuTWueWkodYeHomyK0Pbe0mBpxPmws&e=> > > > > *From:* ARSList <arslist-boun...@arslist.org> *On Behalf Of *LJ LongWing > *Sent:* Wednesday, February 06, 2019 6:04 PM > *To:* ARSList <arslist@arslist.org> > *Subject:* [EXTERNAL] Re: Question about parent groups > > > > Dustin, > > I know this doesn't answer your question, but did you consider using the > DataWizard to actually change the names instead of creating a whole new > architecture? > > > > On Wed, Feb 6, 2019 at 3:59 PM Fawver, Dustin <faw...@mail.etsu.edu> > wrote: > > Greetings! > > > > Management wanted me to change the name of some groups, some majorly and > some not so much. So I created the new groups and made them the parent of > the respective old group. According to > https://docs.bmc.com/docs/itsm91/hierarchical-groups-using-a-parent-group-for-permission-inheritance-608490644.html > <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.bmc.com_docs_itsm91_hierarchical-2Dgroups-2Dusing-2Da-2Dparent-2Dgroup-2Dfor-2Dpermission-2Dinheritance-2D608490644.html&d=DwMGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=DnVIGSEzlRIXfZATPlRnwApWkmEhQz97sCzMg1WKoKg&m=EJizdLriltgwcJGGOBPJTIx6r4MedvpoG1DOjrE2nhA&s=WmsTnDQfD6WNorch3vg1pHOadl_MDQHAOgHa1qaXMUA&e=>, > it says that all permissions assigned to a child group are passed on to its > parent group. However, what I’m seeing is that if a user account is a > member of the parent group but not the child group, some elements of > certain forms are inaccessible for that user account. > > > > I was expecting that parent groups would be able to access things that the > child groups can access. Isn’t it supposed to work that way, or am I going > to have to touch the forms and fields in Dev Studio and adjust permissions? > > Thanks! > > Dustin Fawver > > Sr. Help Desk Technician > > Information Technology Services > > > > P: 423-439-4648 > > itsh...@etsu.edu > > <image001.png> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.etsu.edu_helpdesk&d=DwMGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=DnVIGSEzlRIXfZATPlRnwApWkmEhQz97sCzMg1WKoKg&m=EJizdLriltgwcJGGOBPJTIx6r4MedvpoG1DOjrE2nhA&s=WcPcmh2UObHoPsuTWueWkodYeHomyK0Pbe0mBpxPmws&e=> > > > > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rrr.se_cgi_listinfo_arslist&d=DwMGaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=DnVIGSEzlRIXfZATPlRnwApWkmEhQz97sCzMg1WKoKg&m=EJizdLriltgwcJGGOBPJTIx6r4MedvpoG1DOjrE2nhA&s=9sQyr8IGJaN3DI--1hT0ssd5Z0dRmFXrin-u7LbXd3c&e=> > > *The [EXTERNAL] tag in the subject line identifies emails that do NOT > originate from an ETSU person or service. Please exercise caution when > handling emails from external sources. Any email that is unsolicited and > requires you to take immediate action, appears to be forged or is PHISHING > for information can be verified by emailing the ITS Help Desk. * > > -- > ARSList mailing list > ARSList@arslist.org > > https://urldefense.proofpoint.com/v2/url?u=https-3A__mailman.rrr.se_cgi_listinfo_arslist&d=DwICAg&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=DnVIGSEzlRIXfZATPlRnwApWkmEhQz97sCzMg1WKoKg&m=EJizdLriltgwcJGGOBPJTIx6r4MedvpoG1DOjrE2nhA&s=9sQyr8IGJaN3DI--1hT0ssd5Z0dRmFXrin-u7LbXd3c&e= > > This message contains information which may be confidential and > privileged. Unless you are the intended recipient (or authorized to receive > this message for the intended recipient), you may not use, copy, > disseminate or disclose to anyone the message or any information contained > in the message. If you have received the message in error, please advise > the sender by reply e-mail, and delete the message. Thank you very much. > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist >
-- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
