Project

General

Profile

Bug #13109

Bookmark seeding ignores controller when checking for existing records

Added by Marek Hulán over 3 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Database
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

During bookmarks seed we skip the record if some bookmark with the same name exist. If some plugin define it's own bookmark with same name for different controller, it's considered existing even if it's different bookmark.


Related issues

Related to Foreman Remote Execution - Feature #12814: Ship some default job invocation search bookmarksClosed2015-12-14
Related to Foreman - Feature #11451: Bookmark searches should only need to be unique within their controllerClosed2015-08-23

Associated revisions

Revision b5a2de22 (diff)
Added by Marek Hulán over 3 years ago

Fixes #13109 - seed bookmarks scoped per controller

Revision 88780c61 (diff)
Added by Marek Hulán over 3 years ago

Fixes #13109 - seed bookmarks scoped per controller

(cherry picked from commit b5a2de227c41b710a149c6137729d8c8f7477a05)

Revision 7a7e215f (diff)
Added by Dominic Cleal over 3 years ago

refs #13109 - 1.10 reports controller name

History

#1 Updated by The Foreman Bot over 3 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3049 added

#2 Updated by Marek Hulán over 3 years ago

  • Related to Feature #12814: Ship some default job invocation search bookmarks added

#3 Updated by Dominic Cleal over 3 years ago

  • Related to Feature #11451: Bookmark searches should only need to be unique within their controller added

#4 Updated by Dominic Cleal over 3 years ago

  • Legacy Backlogs Release (now unused) set to 104

#5 Updated by Marek Hulán over 3 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF