You are here

Some Restrictions or things to remember

Error message

  • Deprecated function: TYPO3\PharStreamWrapper\Manager::initialize(): Implicitly marking parameter $resolver as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  • Deprecated function: TYPO3\PharStreamWrapper\Manager::initialize(): Implicitly marking parameter $collection as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  • Deprecated function: TYPO3\PharStreamWrapper\Manager::__construct(): Implicitly marking parameter $resolver as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  • Deprecated function: TYPO3\PharStreamWrapper\Manager::__construct(): Implicitly marking parameter $collection as nullable is deprecated, the explicit nullable type must be used instead in include_once() (line 19 of /homepages/11/d343571938/htdocs/drupal/includes/file.phar.inc).
  1. Burn-up is only calculated when something changes (a Story updated/added, a Status changed or Story moved to a different Iteration)
  2. Text in any field may not exceed 32000 characters (remember that if you are using formatted fields, you will suffer from html bloat!)
  3. A Story can only have a single owner/responsible person (create a tasks for a greater level of detail).
  4. Story Point templates are numeric only.
  5. No e-mail notifications, well not yet anyway
  6. Server times are used
  7. No Integration with other products
  8. Not suitable for public facing use. (security, SQL injection, ... etc)