Specification list

Task/Asset Management

Multiple task types including "texture", "3D model" and "general" with type specific funtionality.

Information per general task:

• title to identify the task easily
• detailed task description (not required)
• author, date of creation
• comments
• assigned team member (not required)
• priority of the task
• completion status
• multiple tags/labels per task
• show the tasks that wait for this task and show the tasks this task waits for

Functionality for general tasks:

• link two tasks together ("waiting for" relationship)
• assign team member to any task
• change of a task should notify the assigned team member, if he does not change the task himself
• (only) used tags should be offered to the editing user when he wants to add a tag
• It should be possible to use one title for multiple tasks, but the user should be warned when he tries
• add comment to any task and remove/edit own comments.

Additional information/functionality for asset tasks:
See https://github.com/Katharsas/GMM/wiki/Specification-for-assets

Notifications

• If task status changes to DONE, all users get notified (public notification)
• Notify all users about any comments on any task (public notification)
• Admins can activate a big permanent custom message for all users for special technical announcements (e.g. downtimes for new application version rollouts)
• Notify users if there was a change to a tasks they are assigned to
• Users get a hint if they have "unread" notifications, and can mark single/all unread notifications as "read"
• Users can switch off public notifications

Automatic asset import

See https://github.com/Katharsas/GMM/wiki/Specification-for-assets

Persistence

The application will persist the following data as human readable XML once in a while. The autosave frequency can be set in the applications settings file. An admin can also save manually or create a backup, which will not be overriden on a new save operation. The directory for new assets and old assets will not be saved or backuped by the application, this needs to be done by hand, if necessary.

• all task data for all tasks (no assets/files included, only links the them)
• user profiles and settings for each individual user (filter settings, notifications, etc.)

Team/User management

• The admin can add/deactivate/activate users and change their username. He can also generate a new random initial password to forward to the user.
• Only a user can change and define his own password as he likes.
• Passwords are saved by the application as hash via standard encryption lybrary
• Users cannot be removed completely, as they are needed as author/assigned object for comments and tasks. When removed, their name may be shown as "Removed" or similar.

Usability

• Task list should have a detailed and a small display mode.
• On click a tasks display mode should change to super detailed.
• The technical admin notification should be the first thing a logged in user always sees.
• UI should be appealing and functional.
• User should be able to switch between easy and detailed task search.

Low Priority

Task/Asset Management

• multiple assigned team members
• general file upload/download
• quick links with target preview in comments/details (e.g. task)

Usability

• in-site tutorial