- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2013 08:35 AM
At the bottom of the Incident record there is a related list for Child Incidents (I believe this is OOB), with an Edit button that brings up a slushbucket listing all Incidents in the Incidents table so you can choose to add them as children. The problem is only I, as admin, can see any Incidents listed. My regular ITIL users get the button and the slushbucket but the list of available Incidents just has < none > in it no matter what filters are used.
Is there a role or setting somewhere that allows my ITIL users to manually add child incidents using this slushbucket?
Solved! Go to Solution.
- Labels:
-
Incident Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2014 07:10 PM
Hi Steven Booth,
We had the similar issue when we upgraded from "Aspen" to "Calgary" and as a workaround we have setup the "Edit default filter" in the list control as "Active is true" to make tickets visible to "ITIL"
Please let me know if this works for you.
Thanks
Pradeep Sharma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2013 04:43 AM
There is an ACL for Incident.Child Incidents that has an operation of Write and the description says "Allow write for child_incidents in incident, if the ACL script returns true." with a script that just says "False;" with no conditions and it has no required role at the bottom.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2013 05:25 AM
Since the script is set to 'false', that indicates that no-one has Write Access. I'm guess the 'Admin Override' is selected thus allowing ADMIN to write.
If you have 'High Security' set on your Instance you will need to have the 'high_security' Role to modify the ACLs.
If you want everyone to be able to write child_incidents you can 'inactivate' the ACL
If you want itil to be able to write then set the script area to 'true' AND add the itil Role to the Related Role list.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2013 05:39 AM
I've tried both deactivating that ACL and changing it to true and adding ITIL to the required roles, neither works. Is it possible something other than an ACL is causing this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2013 06:28 AM
The ACL for incident.child_incident is NOT the correct ACL. This ACL does NOT allow write access to a field on the INC record which records a count of Child tickets.
The ACLs that apply to the Incident Record are the 'Incident.* Read/Write' and the 'Incident.none Read/Write'. Have these been modified?
Have you checked your List Controls?
Verified the user you are using has itil Role?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-06-2013 07:13 AM
The most recently updated Incident ACL's are the incident.child_incident one which I've been messing with this morning, and one for just Incidents that has an Operation of Read, a description of "itil role required to read incident records" and a required role of ITIL.
The List Controls are fine. I have changed the Edit, Filter and Link fields to both be blank or added ITIL role, neither allows ITIL users to see the list of incidents in the slushbucket.