Ponderings Proposals Plans

Tags: start with a "VIP" tag, which gets extra attention. Possibly periodic scans of unassigned and open tickets to accelerate VIP tagged tickets. Maybe the same for an "Emergency" ticket.

New optional contact setting: SMS-gateway email address for the "service desk manager/lead". This is for escalations and urgent notifications of various sorts.

Convert to decorator notation for handlers in init.py

More 'agent' terminology.

would there be any special value in and/or requirements for an "after-hours" mode? Anything additional mycroft could/should do/not do?

Probably should be a separate skill, [WIP: https://github.com/jrwarwick/skill-corporate-i-t-f-a-q] (or just a collection of facts for one of the fall-backs, or possibly according to beta release blog "Persona More on this soon – it will let Mycroft have opinions and customized knowledge") but anyway: FAQ:

• guest wifi password (with optional RFID scan/read to authorize divulgence)
• corporate login/network domain name
• corporate VPN URL, & general auth scheme
• corporate intranet website homepage URL
• corporate FTP (or similar service) URL and auth scheme
• webmail url
• email attachment size limit
• email mailbox size limit
• spam/mail-filtering service name and management console url

Auto-disconnect/reconnect on credentials change, pianobar-skill has an example:

        self._load_vocab_files()

        # Check and then monitor for credential changes
        self.settings.set_changed_callback(self.on_websettings_changed)
        self.on_websettings_changed()

increase contextual awareness with api features. once contextual awareness is increased: for a specific issue, have the option to

• escalate
• set a duedate
• add a tag
• add participants
• request a callback/update.

alternative/fallback environment variables:

• export JIRA_USER=username
• export JIRA_PASSWORD=secretpassword
• export JIRA_SERVER_URL=

alternative/fallback for people who do not want to put passwords into home.mycroft.ai AND do not want do ssh into mycroft and edit files.

intents for inquiry on license consumption/capacity.

Workflow awareness. (e.g., approval workflow, troubleshooting workflow)

Does the concent of priority-matrix (urgency x impact) need recognition? How will it interact/affect direct priority setting? https://confluence.atlassian.com/servicedeskserver/calculating-priority-automatically-939926661.html

multiple projects awareness, possibly only serving one, but allow to "transfer" ticket out to other project (scenario: someone files a bug on the wrong project)

Compatibility with JIRA's "cloud"/hosted-instance service offering. This would impact/require at least auth and probably project handling.

accept an RFID scan (or rather generalize a serial input on some GPIO pins, spec'd to what ever pins an RFID prox card scan would use) to identify user. Might need some kind of LDAP lookup though.