- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2014 09:02 AM
Following the instructions in the Wiki our admin team is unable to create new Releases or Sprints in either the SDLC or StartNow applications (they reference the same objects from two places)
We can create and manage new Stories, Enhancements, and Defects, however, and the entirety of both applications were working during our Quick Start in Q1.
Suggestions on where to look further?
Thanks in advance.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 12:55 PM
Hilariously enough, I'm running into this exact issue over two years later - only this time, I'm having the issue with ***a brand new, out of the box Fuji Installation**...on a ServiceNow Developer Instance that I stood up an hour ago! *facepalm* My own difficulty from two years ago is the first Google result for this.
The correct answer is that the default conditions for the NEW button UI Action eliminate all possible users when selecting RELEASES from the left-hand Application Menu.
The condition out of the box is current.canCreate() && !RP.getListControl().isOmitNewButton() && RP.isRelatedList() && !RP.isManyToMany() && RP.getViewManager().getViewName() != ''
Removing && RP.isRelatedList() from the default condition allows the UI Action to properly place the New button at the top of the list when reaching the form via the SDLC (scrum) -> Releases menu item.
We have also ensured that we have users with the rm_release_admin role, and that the rm_release_admin role has Create rights in the ACL for rm_release_scrum but admin overrides that ACL, so it was definitely the isRelatedList() that was blocking everyone (including Admin) from accessing the New UI Action on the form. 😃
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2016 06:28 AM
Much thanks!
update this guy:
sys_ui_action.do?sys_id=032aeec00a0a2c395e2ced1c98df5543, and remove the condition "&& RP.isRelatedList()"
New button becomes available for all SDLC lists after the edit completed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-27-2016 01:14 PM
in fact I think I was experiencing this before in a previous company but had to use the magnifier search button and create a new release from there each time , and didn't think much of it
but explains why I'm struggling now with a newer implementation
