Should be an optional CharField, similar to telephone. Make sure that the DepartmentUserResource API endpoint outputs the extension field value, too.

Change to allow the BPay biller code for individual applications to be managed in the CMS.

Attempting to add a new registers.hardware record fails with an error, form also seems to be missing the Name field

The Freshdesk v1 API is being deprecated, need to refactor this view.
http://developer.freshdesk.com/api/#create_ticket

Possible: select list of CC, division, site, etc.

Legacy IT Assets system: https://assets.dpaw.wa.gov.au/admin/
Legacy project repo: https://github.com/parksandwildlife/it-assets

Create a utility script in the assets app (assets/utils.py) to import data from the old system into the CMS. Easiest way would be to assume that the data is available as dumped, serialised fixtures.

Model map (old -> new):

• Supplier -> Vendor
• Model -> HardwareModel
• Location -> Location
• Invoice -> Invoice
• Asset -> HardwareAsset

Test the upgrade from 1.9.9 to 1.10.2(?). Check the following:

• Unit tests
• Content admin authoring (create, update, publish)
• Django admin functions (create, update, delete, reports)

Make a note of required deployment steps (migrations, etc.)

More fields: org chart, business manager, location details, etc.

Update the DepartmentUser to include a non-editable NullBoolean field called exchange_licensed (default=None). Review the C:\cron\Get-365LicensedUsers.ps1 Powershell script to see how it outputs a list of licensed O365 user accounts. Add a step to the C:\cron\directory_wrangler.ps1 script to set the exchange_licensed field to True for each O365 licensed account (via the REST API).

OIM staff should be able to use the following apps in the admin (these users will have is_staff = True set) if they are a member of a defined Group (OIM Staff):

• Approvals
• Organisation
• Registers
• Tracking

Users with is_superuser = True should see everything, as normal.

• add unit test to check that a defined user returns true or false

To be added to output:
From CMS fields:
Given Name, Surname, Cost centre, Org unit name, Position Type, Parent (to be renamed Reports to), Section, Office location name, Location address,
From Alesco read-only data:
SECOND_NAME, SURNAME, PAYPOINT, PAYPOINT_DESC, POSITION_NO

Also link tickets & conversations to DepartmentUser objects.

Allow custodians to edit the following fields: description, notes, documentation, technical_documentation, system_reqs, workaround, recovery_docs, system_creation_date, critical_period, alt_processing, technical_recov, post_recovery, user_notification, unique_evidence, point_of_truth, legal_need_to_retain

Add a function for users to upload a photo

Modify DepartmentUserResource class to:

1. Have a clean division between "Create" and "Update" methods (see restless docs: http://restless.readthedocs.io/en/latest/)
2. Undertake logging for create/update actions (what changed, by whom) to new file: logs/ad_sync_actions.log

The main intent of this issue would be to analyse the Radio Comms asset system with regards to the current data model to determine what field(s) would need to be added/changed in the current model. Undertake with regards to the data model outlined here: https://confluence.dpaw.wa.gov.au/display/OIM/Asset+System

List format: APPLICATION NAME (#SYSTEM ID)