| page_type | languages | products | description | urlFragment | ||
|---|---|---|---|---|---|---|
sample |
|
|
Microsoft Teams bot and messaging extension to search & report incidents and connect with specialists immediately |
microsoft-teams-apps-incidentreport |
| Documentation | Deployment guide | Architecture |
|---|
Reporting and management of incidents in an organization is often a manual process ripe for some efficiency gains. Users rely on chat based messaging, e-mail and/or other ad-hoc channels to inform necessary parties about new incidents. Additionally, the information isn't easily audit-able for root cause analyses/postmortems due to transient or one-off nature of e-mail or chat based messaging systems.
The Incident Reporter bot in Microsoft Teams, helps you to easily and quickly respond to, report and document incidents which helps in dealing with an incident with alacrity. The key features of this bot include:
- Automated collection of the time, date and location of every incident
- Customizable incident reporting form based on your workplace needs
- Incidents reports in specialists team which allows for quick collaboration and notification to the relevant stakeholders to track it to completion
This app template is provided under the MIT License terms. In addition to these terms, by using this app template you agree to the following:
-
You, not Microsoft, will license the use of your app to users or organization.
-
This app template is not intended to substitute your own regulatory due diligence or make you or your app compliant with respect to any applicable regulations, including but not limited to privacy, healthcare, employment, or financial regulations.
-
You are responsible for complying with all applicable privacy and security regulations including those related to use, collection and handling of any personal data by your app. This includes complying with all internal privacy and security policies of your organization if your app is developed to be sideloaded internally within your organization. Where applicable, you may be responsible for data related incidents or data subject requests for data collected through your app.
-
Any trademarks or registered trademarks of Microsoft in the United States and/or other countries and logos included in this repository are the property of Microsoft, and the license for this project does not grant you rights to use any Microsoft names, logos or trademarks outside of this repository. Microsoft’s general trademark guidelines can be found here.
-
If the app template enables access to any Microsoft Internet-based services (e.g., Office365), use of those services will be subject to the separately-provided terms of use. In such cases, Microsoft may collect telemetry data related to app template usage and operation. Use and handling of telemetry data will be performed in accordance with such terms of use.
-
Use of this template does not guarantee acceptance of your app to the Teams app store. To make this app available in the Teams app store, you will have to comply with the submission and validation process, and all associated requirements such as including your own privacy statement and terms of use for your app.
Begin with the Solution overview to read about what the app does and how it works.
When you're ready to try out Incident Reporter bot, or to use it in your own organization, follow the steps in the Deployment guide.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.