Deprecated: Joomla\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 41

Deprecated: Return type of Joomla\Input\Input::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 170

Deprecated: Joomla\CMS\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Input.php on line 31

Deprecated: Joomla\CMS\Input\Cookie implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Cookie.php on line 21

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Uri/Uri.php on line 141
Issue Tracker Customisation Guide :: Chapter 5. Project Names

Deprecated: F0FInput implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/f0f/input/input.php on line 35

Deprecated: Joomla\CMS\Input\Files implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Files.php on line 21

Chapter 5. Project Names

The component uses the name 'project' to describe which some may prefer to be named 'categories. It is not unexpected that in our solicitor example these might better be named contracts. These may be have a year as a sub project: i.e. Site A with sub projects 2014, 2015 2016 etc., or alternatively the year could be part of the 'project name'. i.e. 'Site A 2015' so each contract is an individual 'project'.

An alternative might be that each 'contract' type has a specific 'contract number' or 'client name'. In all up to ten sub levels are configurable which should be sufficient for most (any?) installation.

Issues may only be 'private' in that only the 'raiser' and the site administrators (and assignees) would be able to see them. There may/would probably be a few 'public' (generally viable) issues.

It is also possible that only registered' users/members to be able to open/update their own 'issues'.

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries