- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-10-2017 05:59 AM
Hi,
How do I ensure that when you open and create a new Incident Task from an Incident ticket, that it inherits the priority from the Incident ticket?
Many thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2017 02:19 AM
Couldn't you just dot-walk from the task to the incident... then obtain the priority from there?
Just thinking that it's a read-only value and won't change throughout related records, so makes sense to keep it in one location and display it in several, rather than copy it throughout different records (then factor in cascade updates if the incident priority changes)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 05:55 AM
Have you turned on BR Debugging (System Diagnostics> Debug Business Rules (Details)) to see if it is being run, the condition skipped, values set? It can give you more insight as to what is happening (or not.)
http://wiki.servicenow.com/index.php?title=Debugging_Business_Rules

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 05:56 AM
I also recommend taking a look at the Field Watcher for that priority field to see if it is being impacted by something else (client script, UI policy, etc.)
http://wiki.servicenow.com/index.php?title=Field_Watcher
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 08:26 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-11-2017 08:22 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-12-2017 02:19 AM
Couldn't you just dot-walk from the task to the incident... then obtain the priority from there?
Just thinking that it's a read-only value and won't change throughout related records, so makes sense to keep it in one location and display it in several, rather than copy it throughout different records (then factor in cascade updates if the incident priority changes)