Issues

Filters

Apply Clear

# Tracker Status Priority Subject Assignee Category Target version
45021 Work Package New Should have [WIP] [ASSIGNEE MISSING] Cross Browser Compatibility Content Editing 1.0 beta 1 Actions
45019 Work Package New Should have [WIP] Real-World Error Reporting Actions
45009 Work Package New Should have [EPIC] mobile phone version of content editing Actions
45003 Work Package Accepted Should have Media Browser Christian Müller Content Editing 1.0 beta 1 Actions
44981 Story New Should have Rename Node Types to final names Content Repository Sprint February 2013 Actions
44980 Story New Should have Show activity stream of changed content in Launch Bar 1.1 Actions
44979 Story New Should have Implement Frontend user / group concept 1.1 Actions
44978 Story New Should have Multi-Device Content 1.1 Actions
44971 Work Package Accepted Should have TYPO3 Neos API Definition Sebastian Kurfuerst Documentation 1.0 beta 1 Actions
44969 Story New Should have Document Two-Tree Localization Approach Documentation 1.0 beta 1 Actions
44957 Story New Should have Reliable clipboard and content element handles Sprint February 2013 Actions
44932 Story Needs Feedback Should have Update TYPO3CR Node Type Names according to concept Sprint February 2013 Actions
44925 Task New Should have Change the styling of Blog Posts with Expose to match the current styling Marc Neuhaus Sprint February 2013 Actions
44924 Task Accepted Should have Change the Post List view to use Expose Marc Neuhaus Sprint February 2013 Actions
44923 Story New Should have Multi-Lingual User Interface 1.1 Actions
44921 Story Accepted Should have Decide TypoScript and TYPO3CR Naming Sebastian Kurfuerst Content Rendering Sprint February 2013 Actions
44919 Story Accepted Should have Use Expose for listing BlogPost-Nodes in Frontend Marc Neuhaus Content Rendering Sprint February 2013 Actions
44916 Story New Should have Explore: Usage of Touch Screens for Neos Patrick Broens Content Management Sprint February 2013 Actions
44913 Story On Hold Should have RESTful NodeController for easy comment creation Content Management Actions
42672 Story New Should have As everybody, I want no JavaScript loading issues (Bugfix story) Actions
42220 Task New Should have "Uncaught ReferenceError: nextAnimation is not defined" javascript error on load (demo package) Actions
42216 Task New Should have Show at least some recognizable content of a node in the inspector panel. Now the header property is used which only works for headlines Actions
42206 Task New Should have When a content element is hidden based on hiddenBeforeDateTime / hiddenAfterDateTime the hidden CSS should also be applied (so the element should be transparent) Actions
41973 Task Accepted Should have Align button bars for editables on top of the editable border to prevent overlay issues with the content Sebastian Kurfuerst Actions
41931 Task New Should have TODO: add the page properties in a more clever way, and only when being in backend... Content Rendering Actions
41892 Task New Should have Set up an environment for the demo site plus the domain name: neos.demo.typo3.org Ben van 't Ende Actions
41878 Task New Should have extract package management to own package Actions
41877 Task New Should have Explore: Find a way to include Neos / Flow news via RSS Actions
41876 Task New Should have Make Neos UI work with Zurb Foundation (for example) Actions
41872 Task New Should have Detect if symlinks can be created Actions
41861 Story New Should have As any user I want a better usability of the backend UI Actions
41859 Task Accepted Should have Create a standard library for common string, array and date functions in EEL Christopher Hlubek Actions
41858 Story New Should have As an integrator I want a complete feature set in TypoScript and EEL Actions
41856 Task New Should have Require the needed graphic modules for the site import and show a warning if the modules are not found Actions
41855 Task New Should have Optimize the usability of the site creation wizard Berit Hlubek Actions
41853 Story New Should have As an integrator I want an optimized setup Actions
41852 Task New Should have Add default content styles inside the content elements package. Berit Hlubek Actions
41850 Story New Should have As an integrator I would like to include default content styles from Neos Actions
41845 Task Needs Feedback Should have write chapter on Testing in flow.typo3.org guide (Christian Peters takes over this task) Martin Muzatko Actions
41838 Task Accepted Should have document and update conventions for composer name and package keys Christian Jul Jensen Actions
41821 Task New Should have discuss how documentation can be improved Berit Hlubek Actions
41805 Task Accepted Should have adjust release process to Composer / create Neos release using release plugin etc Karsten Dambekalns Sprint February 2013 Actions
41787 Task New Should have change git repositories on git.typo3.org (FLOW3 -> Flow; Neos Name) Actions
41781 Task Accepted Should have set up integration.flow.typo3.org Karsten Dambekalns Sprint February 2013 Actions
41702 Story New Should have As an integrator I want to configure read / write access to pages / sections Actions
41701 Story New Should have As a content editor I want to have localization support ('single tree concept') 1.1 Actions
41700 Story New Should have As a developer I want to have a reasonable test coverage for JavaScript Actions
41687 Task New Should have ask community to convert Sebastians "Technical Overview to Neos" to documentation in ReST Actions
41686 Task New Should have ask community to convert Christians "Developing TYPO3 Neos Website" to tutorial in ReST Actions
41682 Task Accepted Should have create a package for flow.typo3.org website listing only typo3-flow-* composer packages ("mini-TER") Marc Neuhaus Actions
(101-150/230) Per page: 25, 50, 100, 200

Also available in: Atom CSV PDF