Created
July 14, 2013 17:00
-
-
Save claytron/5994933 to your computer and use it in GitHub Desktop.
Merge of plone.app.toolbar and plone.app.widgets issues into mockup tracker
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Could not create label Bug | |
| Could not create label Feature | |
| Could not create label toolbar | |
| Loaded issues 1 29 | |
| Loaded issues 2 0 | |
| Importing issue Personal-tools should come last in the DOM of the toolbar (127) | |
| Successfully created issue Personal-tools should come last in the DOM of the toolbar (45) | |
| Successfully imported comments in Personal-tools should come last in the DOM of the toolbar (45) | |
| Importing issue Upon edit success, page should reload if #portal-column-content is not found (126) | |
| Successfully created issue Upon edit success, page should reload if #portal-column-content is not found (46) | |
| Successfully posted comment in issue 46 | |
| Successfully posted comment in issue 46 | |
| Successfully posted comment in issue 46 | |
| Successfully imported comments in Upon edit success, page should reload if #portal-column-content is not found (46) | |
| Importing issue browser support (125) | |
| Successfully created issue browser support (47) | |
| Successfully posted comment in issue 47 | |
| Successfully imported comments in browser support (47) | |
| Importing issue currently this z-index is hardcoded but i agree we should make this configurable via "data-iframe-zindex" attribute. (124) | |
| Successfully created issue currently this z-index is hardcoded but i agree we should make this configurable via "data-iframe-zindex" attribute. (48) | |
| Successfully imported comments in currently this z-index is hardcoded but i agree we should make this configurable via "data-iframe-zindex" attribute. (48) | |
| Importing issue make sure diazo theme that ships with plone 4.3 works with toolbar (123) | |
| Successfully created issue make sure diazo theme that ships with plone 4.3 works with toolbar (49) | |
| Successfully imported comments in make sure diazo theme that ships with plone 4.3 works with toolbar (49) | |
| Importing issue plone.app.toolbar requires plone.app.jquery >= 1.8.3, but the theme editor in plone.app.theming works only with plone.app.jquery = 1.7.2 (122) | |
| Successfully created issue plone.app.toolbar requires plone.app.jquery >= 1.8.3, but the theme editor in plone.app.theming works only with plone.app.jquery = 1.7.2 (50) | |
| Successfully imported comments in plone.app.toolbar requires plone.app.jquery >= 1.8.3, but the theme editor in plone.app.theming works only with plone.app.jquery = 1.7.2 (50) | |
| Importing issue No feedback on delete if an error occurs. (120) | |
| Successfully created issue No feedback on delete if an error occurs. (51) | |
| Successfully imported comments in No feedback on delete if an error occurs. (51) | |
| Importing issue Add a note on bundles in documentation (119) | |
| Successfully created issue Add a note on bundles in documentation (52) | |
| Successfully posted comment in issue 52 | |
| Successfully imported comments in Add a note on bundles in documentation (52) | |
| Importing issue Navigation is not populated after a content item is deleted from folder contents (118) | |
| Successfully created issue Navigation is not populated after a content item is deleted from folder contents (53) | |
| Successfully posted comment in issue 53 | |
| Successfully imported comments in Navigation is not populated after a content item is deleted from folder contents (53) | |
| Importing issue Patterns are not reapplied when we encounter form errors (adding / editing content). (117) | |
| Successfully created issue Patterns are not reapplied when we encounter form errors (adding / editing content). (54) | |
| Successfully posted comment in issue 54 | |
| Successfully imported comments in Patterns are not reapplied when we encounter form errors (adding / editing content). (54) | |
| Importing issue modal helpers (js/bundles/toolbar.js) should be included in modal pattern (113) | |
| Successfully created issue modal helpers (js/bundles/toolbar.js) should be included in modal pattern (55) | |
| Successfully imported comments in modal helpers (js/bundles/toolbar.js) should be included in modal pattern (55) | |
| Importing issue contents overlay should be improved (111) | |
| Successfully created issue contents overlay should be improved (56) | |
| Successfully imported comments in contents overlay should be improved (56) | |
| Importing issue Change toolbar tile into transform that adds code (110) | |
| Successfully created issue Change toolbar tile into transform that adds code (57) | |
| Successfully posted comment in issue 57 | |
| Successfully imported comments in Change toolbar tile into transform that adds code (57) | |
| Importing issue complete set of steps to get any diazo theme up and going with toolbar (107) | |
| Successfully created issue complete set of steps to get any diazo theme up and going with toolbar (58) | |
| Successfully posted comment in issue 58 | |
| Successfully imported comments in complete set of steps to get any diazo theme up and going with toolbar (58) | |
| Importing issue add instructions to README.rst how to create pattern and register it , so its ready to be used with plone.app.toolbar (104) | |
| Successfully created issue add instructions to README.rst how to create pattern and register it , so its ready to be used with plone.app.toolbar (59) | |
| Successfully imported comments in add instructions to README.rst how to create pattern and register it , so its ready to be used with plone.app.toolbar (59) | |
| Importing issue i think we can remove action dropdown and use it only in contents overlay (102) | |
| Successfully created issue i think we can remove action dropdown and use it only in contents overlay (60) | |
| Successfully posted comment in issue 60 | |
| Successfully posted comment in issue 60 | |
| Successfully posted comment in issue 60 | |
| Successfully posted comment in issue 60 | |
| Successfully posted comment in issue 60 | |
| Successfully imported comments in i think we can remove action dropdown and use it only in contents overlay (60) | |
| Importing issue collection query widget doesn't work with toolbar (100) | |
| Successfully created issue collection query widget doesn't work with toolbar (61) | |
| Successfully imported comments in collection query widget doesn't work with toolbar (61) | |
| Importing issue Clicking outside the modal window closes the window. Therefore when editing, it's really easy to lose your changes. (97) | |
| Successfully created issue Clicking outside the modal window closes the window. Therefore when editing, it's really easy to lose your changes. (62) | |
| Successfully posted comment in issue 62 | |
| Successfully posted comment in issue 62 | |
| Successfully posted comment in issue 62 | |
| Successfully posted comment in issue 62 | |
| Successfully posted comment in issue 62 | |
| Successfully imported comments in Clicking outside the modal window closes the window. Therefore when editing, it's really easy to lose your changes. (62) | |
| Importing issue Lighter/ghost area when adding new content (93) | |
| Successfully created issue Lighter/ghost area when adding new content (63) | |
| Successfully imported comments in Lighter/ghost area when adding new content (63) | |
| Importing issue Support all widgets in p.a.registry (91) | |
| Successfully created issue Support all widgets in p.a.registry (64) | |
| Successfully posted comment in issue 64 | |
| Successfully posted comment in issue 64 | |
| Successfully posted comment in issue 64 | |
| Successfully imported comments in Support all widgets in p.a.registry (64) | |
| Importing issue rethink how / which buttons are listed in toolbar (86) | |
| Successfully created issue rethink how / which buttons are listed in toolbar (65) | |
| Successfully posted comment in issue 65 | |
| Successfully imported comments in rethink how / which buttons are listed in toolbar (65) | |
| Importing issue Make possible that Autocomplete widget can search also over fullnames of users. (83) | |
| Successfully created issue Make possible that Autocomplete widget can search also over fullnames of users. (66) | |
| Successfully imported comments in Make possible that Autocomplete widget can search also over fullnames of users. (66) | |
| Importing issue Growl-like notification center. Something similar that JC Brand did for collective.xmpp.* packages. (example: show notification after user saves/adds content. (82) | |
| Successfully created issue Growl-like notification center. Something similar that JC Brand did for collective.xmpp.* packages. (example: show notification after user saves/adds content. (67) | |
| Successfully posted comment in issue 67 | |
| Successfully posted comment in issue 67 | |
| Successfully imported comments in Growl-like notification center. Something similar that JC Brand did for collective.xmpp.* packages. (example: show notification after user saves/adds content. (67) | |
| Importing issue Site setup and all of its configlet pages should be in overlays. (81) | |
| Successfully created issue Site setup and all of its configlet pages should be in overlays. (68) | |
| Successfully imported comments in Site setup and all of its configlet pages should be in overlays. (68) | |
| Importing issue When changing state or changing different display view request should happen via POST request. (79) | |
| Successfully created issue When changing state or changing different display view request should happen via POST request. (69) | |
| Successfully imported comments in When changing state or changing different display view request should happen via POST request. (69) | |
| Importing issue Manage portlets from toolbar (77) | |
| Successfully created issue Manage portlets from toolbar (70) | |
| Successfully posted comment in issue 70 | |
| Successfully posted comment in issue 70 | |
| Successfully posted comment in issue 70 | |
| Successfully posted comment in issue 70 | |
| Successfully imported comments in Manage portlets from toolbar (70) | |
| Importing issue animate background when content changes in top frame (75) | |
| Successfully created issue animate background when content changes in top frame (71) | |
| Successfully imported comments in animate background when content changes in top frame (71) | |
| Importing issue Relation field will break p.a.t (60) | |
| Successfully created issue Relation field will break p.a.t (72) | |
| Successfully posted comment in issue 72 | |
| Successfully posted comment in issue 72 | |
| Successfully posted comment in issue 72 | |
| Successfully posted comment in issue 72 | |
| Successfully posted comment in issue 72 | |
| Successfully posted comment in issue 72 | |
| Successfully imported comments in Relation field will break p.a.t (72) | |
| Importing issue Responsive design for the toolbar (53) | |
| Successfully created issue Responsive design for the toolbar (73) | |
| Successfully posted comment in issue 73 | |
| Successfully posted comment in issue 73 | |
| Successfully imported comments in Responsive design for the toolbar (73) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Could not create label bug | |
| Successfully created label feature | |
| Could not create label widgets | |
| Loaded issues 1 17 | |
| Loaded issues 2 0 | |
| Importing issue @@syndication-settings Allowed Feed Types turns into a input type text (37) | |
| Successfully created issue @@syndication-settings Allowed Feed Types turns into a input type text (74) | |
| Successfully imported comments in @@syndication-settings Allowed Feed Types turns into a input type text (74) | |
| Importing issue test widgets on mobile devices (36) | |
| Successfully created issue test widgets on mobile devices (75) | |
| Successfully imported comments in test widgets on mobile devices (75) | |
| Importing issue unusable folder_constraintypes_form (33) | |
| Successfully created issue unusable folder_constraintypes_form (76) | |
| Successfully imported comments in unusable folder_constraintypes_form (76) | |
| Importing issue use the field's vocabulary_factory for DX as well (26) | |
| Successfully created issue use the field's vocabulary_factory for DX as well (77) | |
| Successfully imported comments in use the field's vocabulary_factory for DX as well (77) | |
| Importing issue better wirdget for zope.schema.List (24) | |
| Successfully created issue better wirdget for zope.schema.List (78) | |
| Successfully posted comment in issue 78 | |
| Successfully imported comments in better wirdget for zope.schema.List (78) | |
| Importing issue Predictive search should hide non-matching terms as user types (23) | |
| Successfully created issue Predictive search should hide non-matching terms as user types (79) | |
| Successfully imported comments in Predictive search should hide non-matching terms as user types (79) | |
| Importing issue When User's "Full Name" is edited, the change should be reflected on items where they are listed as Creator or Contributor (22) | |
| Successfully created issue When User's "Full Name" is edited, the change should be reflected on items where they are listed as Creator or Contributor (80) | |
| Successfully posted comment in issue 80 | |
| Successfully imported comments in When User's "Full Name" is edited, the change should be reflected on items where they are listed as Creator or Contributor (80) | |
| Importing issue Inconsistency between Dexterity and Archetypes when setting time on object dates (21) | |
| Successfully created issue Inconsistency between Dexterity and Archetypes when setting time on object dates (81) | |
| Successfully imported comments in Inconsistency between Dexterity and Archetypes when setting time on object dates (81) | |
| Importing issue Dexterity: Calendar "Today" and "Clear" buttons should not reload page in IE (20) | |
| Successfully created issue Dexterity: Calendar "Today" and "Clear" buttons should not reload page in IE (82) | |
| Successfully imported comments in Dexterity: Calendar "Today" and "Clear" buttons should not reload page in IE (82) | |
| Importing issue Help Text for Creators and Contributors should be updated to reflect new functionality (19) | |
| Successfully created issue Help Text for Creators and Contributors should be updated to reflect new functionality (83) | |
| Successfully posted comment in issue 83 | |
| Successfully posted comment in issue 83 | |
| Successfully posted comment in issue 83 | |
| Successfully posted comment in issue 83 | |
| Successfully imported comments in Help Text for Creators and Contributors should be updated to reflect new functionality (83) | |
| Importing issue Calendar Month and Year selectors should not close widget in Firefox (18) | |
| Successfully created issue Calendar Month and Year selectors should not close widget in Firefox (84) | |
| Successfully imported comments in Calendar Month and Year selectors should not close widget in Firefox (84) | |
| Importing issue Dexterity: Today and Clear buttons on calendar widget should not reload page (17) | |
| Successfully created issue Dexterity: Today and Clear buttons on calendar widget should not reload page (85) | |
| Successfully imported comments in Dexterity: Today and Clear buttons on calendar widget should not reload page (85) | |
| Importing issue Funny characters should not display when widgets are searching (16) | |
| Successfully created issue Funny characters should not display when widgets are searching (86) | |
| Successfully imported comments in Funny characters should not display when widgets are searching (86) | |
| Importing issue Tags, Creators and Contributors containing commas should not be split into two separate items (14) | |
| Successfully created issue Tags, Creators and Contributors containing commas should not be split into two separate items (87) | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully posted comment in issue 87 | |
| Successfully imported comments in Tags, Creators and Contributors containing commas should not be split into two separate items (87) | |
| Importing issue stable bootstraping of mockup development environment (9) | |
| Successfully created issue stable bootstraping of mockup development environment (88) | |
| Successfully imported comments in stable bootstraping of mockup development environment (88) | |
| Importing issue list/tag widget(select2) should be orderable (4) | |
| Successfully created issue list/tag widget(select2) should be orderable (89) | |
| Successfully posted comment in issue 89 | |
| Successfully posted comment in issue 89 | |
| Successfully imported comments in list/tag widget(select2) should be orderable (89) | |
| Importing issue No datetime widget for plone.app.event (2) | |
| Successfully created issue No datetime widget for plone.app.event (90) | |
| Successfully posted comment in issue 90 | |
| Successfully posted comment in issue 90 | |
| Successfully posted comment in issue 90 | |
| Successfully posted comment in issue 90 | |
| Successfully imported comments in No datetime widget for plone.app.event (90) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment