---
language: "en"
---
# Security & Legal
## Documentation
*
### [Security Practices](https://docs.mobilitystream.com/sec/security-practices.md)
*
### [Privacy Policy](https://docs.mobilitystream.com/sec/privacy-policy.md)
*
### [Service Level Agreement](https://docs.mobilitystream.com/sec/service-level-agreement.md)
*
### [End User License Agreement](https://docs.mobilitystream.com/sec/end-user-license-agreement.md)
### [GDPR](https://docs.mobilitystream.com/sec/gdpr.md)
---
language: "en"
---
# Data Processing Addendum (DPA) – Exhibit for MobilityStream, LLC
**Data Processing Addendum Exhibit: Minimal Personal Data Processing**
This Exhibit describes the scope of personal data processing by MobilityStream, LLC ("Processor") for customers ("Controller") in connection with the Mobility Stream Platform SaaS services.
1. **Categories of Personal Data Processed**
* IP addresses (transient, for authentication, access logging, and security monitoring)
* User account email addresses (for authentication, access control, and support)
* Support ticket metadata (subject, timestamps, user email, system events, if initiated by users)
* System usage metadata (event timestamps, anonymized session IDs, device/browser type)
* Configuration data for MobilityStream apps (non-personal, unless user-provided fields contain PII)
2. **Purposes of Processing**
* User authentication and access control
* Security monitoring and incident response (including intrusion detection and log management)
* Support ticket management (as initiated by users)
* Service usage analytics (aggregated, anonymized)
* System configuration and troubleshooting
3. **Retention and Deletion**
* IP addresses and log data are automatically purged within 30 days via scheduled AWS Lambda jobs.
* Support ticket metadata is deleted upon ticket closure or after 90 days, enforced by SupportPlatform automation.
* Session IDs and analytics data are anonymized and aggregated within 7 days.
* No customer content or other personal data is stored outside these categories.
4. **Subprocessors**
* **Amazon Web Services (AWS)**: Cloud hosting, databases (EC2, RDS, DynamoDB), networking, encryption, backups. Data processed: IP addresses, email addresses, configuration metadata. Location: USA. Transfer Mechanism: DPF/SCCs.
* **AWS GuardDuty**: Intrusion detection, security event monitoring. Data processed: IP addresses, event logs. Location: USA. Transfer Mechanism: DPF/SCCs.
* **AWS CloudWatch**: Log management and alerting. Data processed: authentication logs, system events. Location: USA. Transfer Mechanism: DPF/SCCs.
* **AWS Inspector**: Vulnerability scanning. Data processed: system configuration, event logs. Location: USA. Transfer Mechanism: DPF/SCCs.
* **Bitbucket (Atlassian)**: Source code repository (no customer data). Location: USA. Transfer Mechanism: SCCs.
* **Jira (Atlassian)**: Internal project management and support ticketing. Data processed: support ticket metadata, user emails. Location: USA. Transfer Mechanism: SCCs.
* **Confluence (Atlassian)**: Internal documentation and user guides. Data processed: internal only. Location: USA. Transfer Mechanism: SCCs.
* **SupportPlatform**: Customer support ticketing. Data processed: support ticket metadata, user emails. Location: USA. Transfer Mechanism: SCCs.
* **Microsoft 365**: Identity management, email, office applications. Data processed: user account emails, support communications. Location: USA. Transfer Mechanism: SCCs/DPF.
* **Slack (Salesforce)**: Internal messaging. Data processed: internal only. Location: USA. Transfer Mechanism: SCCs.
* **AnalyticsProvider (MixPanel)**: Aggregated, anonymized usage analytics. Data processed: anonymized session IDs, device/browser type. Location: USA. Transfer Mechanism: SCCs/DPF.
All subprocessors are contractually obligated to comply with GDPR requirements and are reviewed annually for security posture and privacy compliance.
5. **International Transfers**
* Transfers outside the EEA/UK are governed by Standard Contractual Clauses (SCCs) or Data Privacy Framework (DPF) certification.
* Transfer Impact Assessments (TIAs) are maintained for all relevant subprocessors and reviewed annually.
6. **Data Subject Rights**
* MobilityStream, LLC will assist customers in responding to data subject requests for access, deletion, or rectification, as required by GDPR.
* Requests are fulfilled in accordance with documented procedures and within contractual SLAs.
* Data subject requests are handled via [privacy@mobilitystream.com](mailto:privacy@mobilitystream.com) and tracked in Jira Service Management.
7. **Security Measures**
* Encryption at rest and in transit (AWS KMS, TLS 1.2+)
* Role-based access controls, quarterly access reviews
* Multi-factor authentication for production access and administration
* Automated vulnerability scanning (AWS Inspector), annual penetration testing
* Network segmentation and firewall rules (AWS VPC)
* Incident response plan tested annually
* Automated log scrubbing and deletion jobs (AWS Lambda)
* Data classification and retention policies reviewed annually
---
language: "en"
---
# Data Subject Request (DSR) SOP – MobilityStream, LLC
**Data Subject Request (DSR) Handling Procedure -- MobilityStream, LLC**
1. Intake request via [privacy@mobilitystream.com](mailto:privacy@mobilitystream.com) or support portal (Jira Service Management).
2. Verify identity of requester using email confirmation or customer reference.
3. Query relevant systems (AWS logs, Jira tickets, SupportPlatform) for personal data: IP logs, user accounts, support ticket metadata.
4. If data exists, provide copy or delete as requested; if no data retained, communicate outcome to requester.
5. For deletion requests, trigger automated log and ticket deletion jobs; confirm completion.
6. Respond within 30 days; escalate complex requests to privacy lead or DPO.
7. Document request, actions taken, and response in Jira for audit and compliance.
---
language: "en"
---
# End User License Agreement
## End User License Agreement for MobilityStream Products
This End-User License Agreement (this "Agreement") is between you (licensee), as either an individual or as an Entity (defined below), and MobilityStream, LLC.
READ THE TERMS AND CONDITIONS OF THIS AGREEMENT CAREFULLY BEFORE DOWNLOADING, INSTALLING, OBTAINING A LICENSE KEY (IF ANY), OR OTHERWISE ACCESSING OR USING MOBILITYSTREAM'S PROPRIETARY SOFTWARE ACCOMPANIED BY THIS AGREEMENT (THE "SOFTWARE").
THE MOBILITYSTREAM SOFTWARE IS LICENSED TO YOU UNDER THIS AGREEMENT, NOT SOLD TO YOU. BY DOWNLOADING, INSTALLING, OBTAINING A LICENSE KEY (IF ANY), OR OTHERWISE ACCESSING OR USING ANY PART OF THE SOFTWARE, YOU AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS AND CONDITIONS ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY ("ENTITY"), YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS, AND REFERENCES TO "YOU" OR "YOUR" REFER TO USER, THE INDIVIDUAL END-USER, AND THE ENTITY. IF YOU DO NOT HAVE THAT AUTHORITY OR IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, DO NOT DOWNLOAD, INSTALL, OBTAIN A LICENSE KEY (IF ANY), OR OTHERWISE ACCESS OR USE THE SOFTWARE.
IF YOU ARE ACCESSING THE SOFTWARE AS PART OF A HOSTED SERVICE, THEN ALL OF THESE TERMS STILL APPLY. HOSTED SERVICES INCLUDE USING ANY MOBILITYSTREAM SOFTWARE AS A SERVICE, AND ALWAYS MEANS THE VERSION OF THE HOSTED SERVICES DESCRIBED IN MOBILITYSTREAM'S THEN-CURRENT PRODUCT DESCRIPTION. THE TERM "PRODUCTS" AS USED IN THIS END USER LICENSE AGREEMENT INCLUDES BOTH SOFTWARE AND HOSTED SERVICES.
You agree that your relationship with MobilityStream is also governed by MobilityStream's Terms and Conditions and Privacy Policy, which are expressly made part of this Agreement. For more information about our Products and Services or about MobilityStream, please visit [https://www.mobilitystream](https://www.mobilitystream.com/) review the Frequently Asked Questions. You may contact us by visiting and visit the Contact section.
### **1. License.**
Grant of License. Subject to your full compliance with all terms and conditions of this Agreement, MobilityStream grants to you a revocable, nontransferable, nonsublicensable, nonexclusive, limited right and license to use the Products, in object code form only, and the accompanying documentation in accordance with the accompanying documentation and only as authorized by this Agreement, for the Term you selected in your Order Form. For purposes of this Agreement "Products" includes any updates, enhancements, modifications, revisions or additions to the Products made by MobilityStream and made available to you. Notwithstanding the foregoing, MobilityStream may, but is not required to, provide any updates, enhancements, modifications, revisions or additions to the Products.
Scope of Use. Your license allows you to run the Products only as received at the time of download for the number of authorized users and nodes on devices owned, leased or controlled by you. Your use of the Products on mobile devices may be subject to additional terms of use, such as Apple App Store Terms of Service or Google Play Terms of Service. MobilityStream may audit your company's use of the Products at any time and at MobilityStream's expense. If the audit establishes that you have used the Products without a valid license, then the cost of the audit transfers to you.
### **2. Payment and Restrictions.**
You do not have an active license to use the Products unless and until you have paid the requested license fee or service fee. MobilityStream reserves the right to increase license fees or service fees for the Products, including a higher price for new initial licenses, for yearly renewals and for monthly charges. MobilityStream may also charge for software or services that initially included in a license fee or service fee, including support, maintenance, updates or upgrades.
You shall not, nor permit anyone else to, directly or indirectly: (i) copy, modify, or distribute the Products or license key (if any); (ii) reverse engineer, disassemble, decompile or otherwise attempt to discover the source code or structure, sequence and organization of Products, in whole or in part (except that this restriction shall not apply to the limited extent restrictions on reverse engineering are prohibited by applicable law); (iii) assign, rent, lease, or use the Products for timesharing or service bureau purposes, or otherwise use the Products for any commercial purpose; or (iv) create any derivative works from or sublicense any rights in the Products. You shall maintain and not remove or obscure any proprietary notices on the Products, and shall reproduce such notices exactly on all permitted copies of the Products.
You represent, warrant and covenant that you will not use the Products: (i) to infringe the intellectual property or proprietary rights, or rights of publicity or privacy, of any third party; (ii) to violate any applicable federal, state or local law, statute, ordinance or regulation; (iii) to disseminate, transfer or store information or materials in any form or format ("Content") that are harmful, threatening, abusive, harassing, tortious, defamatory, vulgar, obscene, libelous, or otherwise objectionable or that otherwise violate any law or right of any third party; (iv) to disseminate any software viruses or any other computer code, files or programs that may interrupt, destroy or limit the functionality of any computer software or hardware or telecommunications equipment, or violate the security of any computer network; or (v) to run Maillist, Listserv, "bots ", "robots," any form of auto-responder, or "spam," or any processes that run or are activated while you are not logged in. You, not MobilityStream, remain solely responsible for all Content that you upload, post, e-mail, transmit, or otherwise disseminate using, or in connection with, the Products. You acknowledge that all Content you access through use of the Products is accessed at your own risk and you will be solely responsible for any damage or liability to any party resulting from such access.
### **3. Intellectual Property; Content.**
You acknowledge that the Products and its accompanying documentation are protected by copyright and other intellectual property laws and treaties. You further acknowledge and agree that MobilityStream and its licensors shall continue to own all title, ownership rights, and intellectual property rights in and to the Products, and any copies or portions thereof, and any accompanying documentation. You understand that MobilityStream or its licensors may modify or discontinue offering the Products at any time. This Agreement does not give you any rights not expressly and unambiguously granted herein.
### **4. Support.**
Server Version of Products. If you are licensing the server version of the Products, your perpetual license entitles you to contact support, upgrades, patches, enhancements, and fixes (collectively, "Support") for one (1) year following the commencement of a fully paid support term for this version of the Products (or the next version, at MobilityStream's sole discretion, during such one (1) year support term), provided that you comply with all the terms and conditions of this Agreement. Such support is included for the license period in software as a service licenses. The fee for Support after year one will be 50% of the original perpetual license fee, which included one year of Support. Support will be renewed through the Atlassian Marketplace.
Hosted Version of Products. If you are using the Hosted version of the Products, then you are licensing the use of a service which will include access to the then current version of the MobilityStream Software.
If Support is not renewed, users are not allowed to upgrade to a newer version of the product (server add-on and mobile app). It is the responsibility of the licensee to ensure that users do not upgrade after the end date of the maintenance period. Should users upgrade the product (server add-on or mobile apps) to a more current version (beyond the date when the maintenance period expired), the product may stop to work.
### **5. Warranty Disclaimer.**
THE PRODUCTS ARE PROVIDED "AS IS". MOBILITYSTREAM MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, AND MOBILITYSTREAM EXPRESSLY DISCLAIMS ALL WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. FURTHER, MOBILITYSTREAM DOES NOT WARRANT RESULTS OF USE OR THAT THE PRODUCTS ARE BUG FREE OR ERROR FREE OR THAT ITS USE WILL BE UNINTERRUPTED. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS AGREEMENT. ALL THE FOREGOING DISCLAIMERS ALSO APPLY IN FULL WITH RESPECT TO MOBILITYSTREAM'S LICENSORS, SUPPLIERS, DISTRIBUTORS, CONTRACTORS AND AGENTS.
### **6. Indemnity.**
You agree that MobilityStream and its licensors, distributors, contractors and agents (collectively, the "Indemnified Parties") shall have no liability whatsoever for any use you make of the Products. You shall indemnify and hold harmless the Indemnified Parties from any claims, damages, liabilities, costs and fees (including reasonable attorneys' fees) arising from (a) your failure to comply with any term of this Agreement; or (b) use of the Products in combination with other hardware, software or other systems that would have been avoided but for such use or combination. To the maximum extent permitted by applicable law, you hereby release, and waive all claims against, MobilityStream and its licensors, suppliers, employees and agents from any and all liability for claims, damages (actual and consequential), costs and expenses (including litigation costs and attorneys' fees) of every kind and nature, arising out of or in any way connected with use of the Products. If you are a California resident, you waive your rights under California Civil Code § 1542, which states, "A general release does not extend to claims which the creditor does not know or suspect to exist in his favor at the time of executing the release, which if known by him must have materially affected his settlement with the debtor." Residents of other states and nations waive their rights under all analogous laws, statutes or regulations.
### **7. Limitation of Remedies and Damages.**
UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, INCLUDING, BUT NOT LIMITED TO, TORT, CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHERWISE, SHALL THE INDEMNIFIED PARTIES BE LIABLE TO YOU OR ANY OTHER PERSON (I) FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER OR (II) FOR ANY MATTER BEYOND ITS REASONABLE CONTROL. MOBILITYSTREAM'S LIABILITY FOR DAMAGES OF ANY KIND WHATSOEVER ARISING OUT OF THIS AGREEMENT SHALL BE LIMITED TO THE TOTAL FEES PAID BY YOU TO MOBILITYSTREAM, EXCEPT WHERE NOT PERMITTED BY APPLICABLE LAW, IN WHICH CASE MOBILITYSTREAM'SLIABILITY SHALL BE LIMITED TO THE MINIMUM AMOUNT PERMITTED BY SUCH APPLICABLE LAW. ALL THE FOREGOING LIMITATIONS SHALL APPLY EVEN IF MOBILITYSTREAM HAS BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATION AND EXCLUSION MAY NOT APPLY TO YOU.
### **8. Termination.**
Your rights under this Agreement will terminate automatically and irrevocably without notice from MobilityStream if you fail to comply with any term(s) of this Agreement, including any attempt to transfer a copy of the Software or Software license key (if any) to another party except as provided in this Agreement.
Upon termination for any reason, the Agreement granted hereunder shall terminate and you shall immediately discontinue all use of the Products and destroy and remove from all computers, hard drives, mobile devices, networks and other storage media all copies of the Products, but the terms of Section 2 (Restrictions); Section 5 (Warranty Disclaimer); Section 6 (Indemnity); Section 7 (Limitation of Liability); the last sentence of this Section 8 (Termination) and Section 10 (Miscellaneous) of this Agreement will otherwise remain in effect.
### **9. Export Law Assurances.**
In connection with the Products, you agree to comply with all export laws and restrictions and regulations of the Department of Commerce, the United States Department of Treasury Office of Foreign Assets Control, or other United States or foreign agency or authority, and you agree not to export, or allow the export or re-export of the Products in violation of any such restrictions, laws or regulations. By downloading, installing, accessing or using the Products, you agree to the foregoing and represent and warrant that you are not located in, under the control of, or a national or resident of any restricted country.
### **10. Miscellaneous.**
No agency, partnership, joint venture, or employment is created as a result of this Agreement and you do not have any authority of any kind to bind MobilityStream in any respect whatsoever. The failure of either party to exercise in any respect any right provided for herein shall not be deemed a waiver of any further rights hereunder. This Agreement is not assignable, transferable or sublicensable by you except with MobilityStream's prior written consent. MobilityStream may transfer, assign or delegate this Agreement and its rights and obligations without consent. You grant MobilityStream the right to include your name, trademark, logo or similar identifying material ("Your Marks") in a listing of customers on MobilityStream's website and in other promotional material in relation to the Products. Within thirty (30) days of your written request, MobilityStream will remove Your Marks from its website customer list and will make no further use of Your Marks in any future material promoting the Products. This Agreement as well as all disputes arising out of or in connection with this Agreement shall be governed by the laws of the State of Illinois, without regard to or application of choice of law rules or principles. Any dispute arising out of or in connection with this Agreement, or in future agreements resulting therefrom, shall be exclusively resolved before the state or federal courts located in Chicago, Illinois. You further agree not to bring claims on a representative, class member basis, or as a private attorney general, and agree not to assert any claims against us unless such claims are asserted by you in the forum required by this Agreement no later than one year following the date that your claim or cause of action arose.
This Agreement constitutes the entire agreement between you and MobilityStream with respect to the subject matter hereof and will supersede and replace all prior understandings and agreements, written or oral, regarding such subject matter, provided however, you will still be bound by MobilityStream's Terms and Conditions and Privacy Policy. We reserve the right to modify this Agreement at any time by providing such revised Agreement to you or by publishing the revised Agreement. Your continued use of the Products shall constitute your acceptance to be bound by the terms and conditions of the revised Agreement.
YOU EXPRESSLY ACKNOWLEDGE THAT YOU HAVE READ THIS END USER LICENSE AGREEMENT AND UNDERSTAND THE RIGHTS, OBLIGATIONS, TERMS AND CONDITIONS SET FORTH HEREIN. BY CLICKING ON THE ACCEPT BUTTON AND/OR CONTINUING TO INSTALL OR OTHERWISE USE THE PRODUCTS, YOU EXPRESSLY CONSENT TO BE BOUND BY ITS TERMS AND CONDITIONS AND GRANT TO MOBILITYSTREAM THE RIGHTS SET FORTH HEREIN.
Version: January 2020
---
language: "en"
---
# GDPR
* [Data Processing Addendum (DPA) -- Exhibit for MobilityStream, LLC](https://docs.mobilitystream.com/sec/data-processing-addendum-dpa-exhibit-for-mobilitys.md)
* [Records of Processing Activities (ROPA) -- MobilityStream Platform](https://docs.mobilitystream.com/sec/records-of-processing-activities-ropa-mobilitystre.md)
* [Privacy Notice -- Mobility Stream Platform](https://docs.mobilitystream.com/sec/privacy-notice-mobility-stream-platform.md)
* [Subprocessor List -- MobilityStream Platform](https://docs.mobilitystream.com/sec/subprocessor-list-mobilitystream-platform.md)
* [Data Subject Request (DSR) SOP -- MobilityStream, LLC](https://docs.mobilitystream.com/sec/data-subject-request-dsr-sop-mobilitystream-llc.md)
---
language: "en"
---
# Privacy Notice – Mobility Stream Platform
**Privacy Notice: Mobility Stream Platform**
MobilityStream, LLC processes only limited personal data necessary to provide the Mobility Stream Platform services, including transient IP addresses (for authentication and security), user account emails (for login and support), support ticket metadata (if initiated by users), and anonymized usage analytics. No customer content or sensitive personal data is stored or processed by MobilityStream, LLC except as described.
Retention periods are strictly enforced by automated deletion jobs (e.g., 30 days for logs, 90 days for support tickets). Data is encrypted at rest and in transit. Access is restricted by role-based controls and multi-factor authentication.
Subprocessors include AWS (hosting, security, databases), Atlassian (Jira, Bitbucket, Confluence), SupportPlatform (ticketing), Microsoft 365 (email/identity), and AnalyticsProvider (anonymized analytics). All subprocessors are subject to GDPR-compliant contracts and annual reviews.
International transfers are protected by Standard Contractual Clauses or Data Privacy Framework as applicable. Transfer Impact Assessments are conducted annually.
Data subjects may request access, deletion, or rectification of personal data processed by contacting [privacy@mobilitystream.com](mailto:privacy@mobilitystream.com). Requests are handled in cooperation with the customer (controller) and fulfilled within 30 days.
For more details, see our Subprocessor List and Data Protection Policy.
---
language: "en"
---
# Privacy Policy
## Data stored on Mobile Device
When you connect to Jira via Mobility for Jira there is no data stored locally on your mobile device. All data retrieved from Jira via the REST API is used for display purposes only and does not reside on the device permanently. Avatar images and icons are cached for 24 hours, all other data is discarded immediately. Before you connect, make sure your Jira server uses SSL and you connect via https or use a MDM system such as MobileIron or a VPN. Not encrypted connections are not secure. User names and passwords can be stored on the mobile device but are encrypted in both version iOS as well as Android.
## Data stored by Mobility Add-On (server version)
The Mobility add-on stores your user's device identifier within Jira, including their preferences what notifications to receive. No other data is stored. When a user entry is deleted all this information is discarded.
## Data stored by Mobility Add-On (cloud version)
The only data sent to MobilityStream is information about your Jira instance (name, version, install data, license information). After that your users' devices will authenticate once per 12 or 24 hours against the MobilityStream service. MobilityStream will check the license information against the server. No other information is sent to MobilityStream.
Version: July 2020
---
language: "en"
---
# Records of Processing Activities (ROPA) – MobilityStream Platform
**Records of Processing Activities (ROPA) -- Mobility Stream Platform**
| Activity | Purpose | Data Categories | Recipients/Subprocessors | Retention | Lawful Basis | Transfers |
|-------------------------|----------------------------------|----------------------------|--------------------------------|------------------------|---------------------|-----------|
| Authentication Logging | Security, access control | IP address, email address | AWS EC2, GuardDuty, CloudWatch | 30 days | Contractual | DPF/SCCs |
| Support Ticket Handling | Customer support | Email, ticket metadata | Jira, SupportPlatform | Ticket closure/90 days | Contractual | SCCs/N/A |
| Usage Analytics | Service improvement (anonymized) | Session ID, device/browser | AnalyticsProvider | Aggregated | Legitimate interest | SCCs/DPF |
| Vulnerability Scanning | Security, compliance | System config, event logs | AWS Inspector | 30 days | Legal obligation | DPF/SCCs |
| Backup \& DR | Business continuity | Configuration metadata | AWS RDS, DynamoDB | 30 days | Contractual | DPF/SCCs |
| Internal Communication | Support, admin | User email (internal only) | Microsoft 365, Slack | N/A | Contractual | SCCs/DPF |
---
language: "en"
---
# Security Practices
## Overview
At MobilityStream security has number one priority. Many of our employees have come from large, security-conscious organizations and continuously work with organizations in defense, government, banking, and health care have helped us to strengthen our security culture even further. This is a non-comprehensive list of ways we think about security for our process, product, operations, availability, and compliance. We are happy to engage with your security team or a third party to help you assess our products in more depth. Also, if you have specific contractual requirements that go beyond our standard agreement, we are happy to discuss them with you. Please contact us at [security@mobiliystream.com](mailto:security@mobiliystream.com). You can also [visit our Trust Center](https://trust.mobilitystream.com/) for more detailed information.
## Process
### Security Policy
MobilityStream's security policy is an overarching document that governs MobilityStream's handling of data governance and security in general. Clear responsibilities are defined within the organization, vulnerabilities are considered and handled. The policy is generally provided upon demand or during a security review.
### Incident Management
This process lays out how MobilityStream handles security incidents. It defines how MobilityStream is communicating with Atlassian, clients, and other partners during an incident. The process clearly defines responsibilities and sets expectations. Should we detect any incident that potentially exposes client data, we will communicate within 48 hours after identification.
### Bug Bounty Program
All of our products have been participating in a Bug Bounty Program for several years. If a potential vulnerability is detected we will release a fix within 7 days for critical issues.
### Cloud Fortified
The Cloud Fortified program and badge makes it super simple for customers to identify enterprise-ready cloud apps with additional security, reliability, and support. All Mobility Stream apps on the Atlassian Marketplace are Cloud Fortified.
### Penetration Testing
Mobility Stream works with 3rd Parties to perform annual penetration testing on all its apps.
## Product Security
### Building-in security
During our engineering process we consider security of the product at every turn and when we make major decisions of our products. Security requirements are key for us and we do not make any compromises. Code is reviewed and security is always a major consideration. Should a defect slip into production, a fix for the problem always has the highest priority at MobilityStream. We will release a fix for a critical security vulnerability within 7 days.
### Encryption
We encrypt all traffic with internal and external systems. We always try to use the most secure and trusted encryption algorithms. We do not believe in proprietary methods. We encrypt the data on disk where it makes sense and additional safeguards are required to protect sensitive data.
### Security controls
Our products support the most secure controls. For example for our mobile apps, we have been supporting Single Sign-On, Multi-factor authentication, and Mobile Device Management Solutions for many years. In addition our products rely on the underlying security product features of the Atlassian suite.
## Operations
### Security Information Event Management
In particular in our Cloud environment, we employ secure techniques to detect any unusual activity on our network in real-time. We use a SIEM to analyze and identify such activities and threats and neutralize them as soon as they are identified.
### Segregation of duty
In our production environments, we have a clear separation of duties. Responsibilities are clearly defined and access is provisioned accordingly. Our engineers have the access they need to work on problems, but not more.
### Change control
We have been following engineering best practices for change control since our inception. Our team has worked in large organizations and understands the importance of a well-defined process that is still nimble and provides agility for the team. All of our code is version controlled, we use CI/CD practices to move the product to production, and use monitoring to ensure that our products perform as expected.
## Availability and Continuity
### Robust Architecture
Our cloud architecture is designed in a way to make a failure highly unlikely. We pride ourselves to use modern technology and apply it to support high availability and spread the processing across multiple data centers. In the unlikely case of an outage we have means to recover quickly.
### Recovery
We understand the impact a potential outage of add-on vendors may have to your operations. We have a clear and tested plan for restoring our Cloud environment in the unlikely case of failure. We have defined Restore Time Objectives (RTO) and Restore Point Objectives (RPO). Even in the unlikely case of outage, your impact will be minimal.
## Compliance
We understand that your organization may have strict security, privacy and compliance requirements. We have been working with large organizations in government, defense, banking, and health care that need to comply with ISO 27001, HIPAA, FedRamp, PCI, SOC, HITRUST, and other compliance requirements. We pride ourselves to be a very competent partner to help our clients achieve their compliance goals.
Mobility Stream has achieved SOC 2 Type II compliance. You can request the most up-to-date report by e-mailing [security@mobilitystream.com](mailto:security@mobilitystream.com).
Version: May 2025
---
language: "en"
---
# Service Level Agreement
## Overview
This Service Level Agreement applies to all Mobility Stream customers. When creating a support request through Mobility Stream's service desk, we will respond within 48 business hours of your initial request (24 hours for business critical requests). Our goal is to answer the majority of requests within the same business day. Mobility Stream will use reasonable efforts to provide support in accordance with this Service Level Agreement, and will not be responsible for any delays caused by the customer for reasons beyond MobilityStream's control.
## Business Hours and Response Time
MobilityStream's business hours are from 9am to 5pm CST, Monday through Friday. All requests are answered within 48 business hours (24 hours for business critical requests). We are constantly monitoring our support channels to respect the high priority of our enterprise customers and any critical issues.
## Support Channels
You can request support through one of the following channels:
* Submitting a ticket through Mobility Stream's [Service Desk](https://mobilitystream.atlassian.net/servicedesk/customer/portal/2)
* Sending an email to: [support@mobilitystream.com](mailto:support@mobilitystream.com)
* Requests made through open forums such as Atlassian Answers or Add-On Reviews are monitored by our support team and answered on a best-effort basis.
## Mobility Stream's Support Includes
* Assistance with configuring Mobility Stream's products
* Guidelines and best practices on Mobility Stream products
* Help with troubleshooting problems with Mobility Stream's products
* Help with issues arising out of Mobility Stream's product upgrades
## Mobility Stream's Support Does Not Include
* Phone support
* Product training
* Support for Jira configurations not related to a Mobility Stream product
* Support in any language other than English and German
This Service Level Agreement may change at any time.
We also adhere to the [Atlassian Marketplace Trust](https://www.atlassian.com/trust/marketplace?source=app-listing-badge) for all of our Add-ons that carry the Cloud Security Participant \& Cloud Fortified badges.
Version: February 2024
---
language: "en"
---
# Subprocessor List – MobilityStream Platform
**Subprocessor List for Mobility Stream Platform**
| Subprocessor Name | Service Provided | Location | Data Processed | Transfer Mechanism |
|------------------------------|--------------------------|----------|---------------------------------------|--------------------|
| Amazon Web Services (AWS) | Cloud hosting, databases | USA | IP addresses, emails, config metadata | DPF/SCCs |
| AWS GuardDuty | Intrusion detection | USA | IP addresses, event logs | DPF/SCCs |
| AWS CloudWatch | Log management | USA | Authentication logs, system events | DPF/SCCs |
| AWS Inspector | Vulnerability scanning | USA | System config, event logs | DPF/SCCs |
| Bitbucket (Atlassian) | Source code repository | USA | No customer data | SCCs |
| Jira (Atlassian) | Project/support tickets | USA | Support ticket metadata, emails | SCCs |
| Confluence (Atlassian) | Documentation | USA | Internal only | SCCs |
| SupportPlatform | Support ticketing | USA | Support ticket metadata, emails | DPF |
| Microsoft 365 | Identity/email | USA | User account emails, support comms | SCCs/DPF |
| Slack (Salesforce) | Internal messaging | USA | Internal only | SCCs |
| AnalyticsProvider (MixPanel) | Usage analytics | USA | Session ID, device/browser type | SCCs/DPF |
---
language: "en"
---
# Mobility for Jira
## Documentation
*
### [Installation](https://docs.mobilitystream.com/mobility-for-jira/installation.md)
### [Getting Started with Jira (Team Edition)](https://docs.mobilitystream.com/mobility-for-jira/getting-started-with-jira-team-edition.md)
### [Getting Started with Jira Service Management (Portal Edition)](https://docs.mobilitystream.com/mobility-for-jira/getting-started-with-jira-service-management-porta.md)
*
### [Mobile Security](https://docs.mobilitystream.com/mobility-for-jira/mobile-security.md)
### [Frequently Asked Questions](https://docs.mobilitystream.com/mobility-for-jira/frequently-asked-questions.md)
*
### [Video Tutorials](https://docs.mobilitystream.com/mobility-for-jira/video-tutorials.md)
---
language: "en"
---
# Activity Stream Shortcut
|---|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | You can select a combination of issues, projects, issue \& activity types to be included in your stream (all optional) 1. Tap on + icon on top right of home screen 2. Select the Activity Stream shortcut type 3. Specify any items you would like to include in your Activity Stream 1. Issues - pick one or many issues 2. Projects - pick one or many projects 3. Users - pick one or many users 4. Activity - pick one or many Jira events 1. Attachment added 2. Comment added 3. Issue closed 4. Issue created 5. Issue edited 6. Issue opened 7. Issue progress started 8. Issued progress stopped 9. Issue reopened 10. Issue resolved 11. Issue transitioned 5. Issue Type - pick one or many Issue Types 4. Tap on the Add button on the top right of the screen 5. The Activity Stream Shortcut will be added to the Home screen |
---
language: "en"
---
# Add a Comment
## Finding a Request
Go to your request screen by tapping the **Requests** tab on the bottom of the screen. The number indicated on the tab will tell you how many open requests are on the list.
### Commenting
Select the issue you want to comment on. Scroll to the bottom and hit the blue **Comment** label to reveal the comment section. Enter your comment and optionally add an attachment to the comment by tapping the **+** icon on the right side of the comment field.
### Cancel or Escalate
You can cancel or escalate a request by tapping the **...** in the top right of the screen. A menu of options will show up to cancel or escalate the request.
[++Previous++](https://docs.mobilitystream.com/mobility-for-jira/create-a-request.md)
---
language: "en"
---
# Board Shortcut
|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | 1. Tap on + icon on top right of home screen 2. Tap on Board option 3. Find and tap on board that you would like to appear on your home screen 4. Shortcut will be added to home screen |
---
language: "en"
---
# Project Boards
When selecting a Project the Board of the project is displayed. A Board can be displayed for different project types such as Scrum, Kanban, other projects.
If the project is a Jira Service Management project you will see additional menu tabs such as Queues and Organizations. You can learn more about JSM projects [here](https://docs.mobilitystream.com/mobility-for-jira/jira-service-management.md).
## Backlog
You can scroll up and down to view your entire Backlog. The position of each backlog item can be changed by dragging it up or down the list.
Pressing on the **...** button of an issue card will provide additional options such as:
* Move issue to active Sprint
* Move issue to Top of Backlog
* Move issue to Bottom of Backlog
* Add a Flag to issue (mark in yellow)
## Board
The Sprint board will display on the Board tab. Scroll left and right to view other columns. Alternatively you can rotate your device to see more columns in the same view.
To start a new sprint tap on **Create Sprint** , then drag the desired items into the new sprint column to the right. When ready, tap **...** on the new sprint column card and select **Start Sprint**. You can name the sprint and set the proper start and end dates.
## Roadmap
The Roadmap view lets you visualize your items on a Timeline. The view displays the top-level Epics by default and uses available dates (start date, end date, estimates) to put the items correctly on the timeline.
## Issues
Find a variety of predefined ways to search when tapping on **Issues**.
If your search criteria for this project is not listed, select **All Issues** and then refine your search by using Basic or Advanced Search capabilities.
## Components
Components can be created, edited, and viewed for each project.
Tap the **+** button to create a new component. All available fields such as Name, Description, Component Lead, and a Default Assignee can be selected.
To edit a component you can select an entry and start editing any field.
lssues associated to a component can be viewed by tapping the**Issues in this component**button.
## Releases
Each project can have one or many release that may be in an unreleased, released, or archived state.
Tap on **Releases** and adjust the filter by hitting the filter icon. You can view any combination of unreleased, released, or archived versions by selecting the checkbox.
For each Release you can view details such as the description, release data as well as Jira issues to this release by Status. Tapping on a status allows you to see the included issues.
To create a Release, tap the **+** icon and provide a release name, description, start and release date.
|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
|  |  |  |
## Activity Stream
The Activity Stream shows activities for the entire project. You can tap each user to view the user's profile. You can also tap on each issue to see the issue detail view.
---
language: "en"
---
# Capture Geolocation
You can capture the current location of your device into any text field.
This can be done by two ways:
* Tap on any text field and then tapping on the My Location context menu
* Tap on the pin icon of a field that has been configured by your administrator
## Without Configuration
Tapping any text field will bring up the context menu. You might have to scroll to the next entry until you see "My Location". One tap on the context menu will fill the text field with latitude and longitude.
## With Administrator Configuration
Your administrator can configure any text field by adding "(geo)" anywhere on the custom field text label. Once the change has been made and the custom field is displayed on the JSM Portal, the app will then display a pin icon next to the custom field.
The mobile user sees a pin next to the custom text field with "(geo)" on the label. By tapping the pin, the latitude and longitude of the current device location is added to the field. The value can be edited by the user if desired.
Tap the pin icon next to a text field
Current latitude and longitude are populated
---
language: "en"
---
# Cloud Migration
Our Mobility for Jira app can be used for Jira Server, Datacenter and Cloud. Since the app does not store any data on your server the process of migrating between different deployment types is straightforward and does not require any data migration.
Here are the steps for a successful migration to Jira Cloud:
1. Install the [Mobility for Jira](https://marketplace.atlassian.com/apps/1211459/mobility-for-jira-mobile-for-enterprise-teams?hosting=cloud&tab=overview) add-on on your Jira Cloud system
2. Accept the Free Trial
3. Mobile users can now [add this new account](https://mobilitystream.atlassian.net/l/c/HspMjzQH) on their mobile device and enter your new URL
4. Mobile users should go to [Profile \> Notifications](https://docs.mobilitystream.com/mobility-for-jira/push-notification-setup.md) and set their preferred Push Notification preferences
5. Occasionally, mobile users have customized shortcut pages. They can be recreated for the new account by each user, which is a quick [process](https://docs.mobilitystream.com/mobility-for-jira/home-screen-shortcuts.md)
The Mobility for Jira Add-on does not store any of your data. The only exception are Push Notification settings that need to be re-entered by your mobile end users.
---
language: "en"
---
# Create a Request
## Service Desks
Choose your Service Desk if you have access to more than one Service Desks at your organization. Alternatively, you can directly search for Request types across multiple Service Desks on the Help Center screen.
### Request Type
Select the Request types that best matches the issue you need to report. The Service Desk structure, list of Request types, and the Form fields are dependent on your organization's Jira configuration. Many different field types such as drop downs, user picker, text fields, database lookup fields (based on add-ons) are supported.
### Attachments
Optionally you can attach a file to the request ticket by pressing the **+** button. We support a variety of different files such as images, videos, audio files, etc. After filling out all the required fields, press the **Create** button or hit Cancel if you want to stop. Your request will be generated in a Service Desk agent's support queue.
### Forms
If you have Forms (previously ProForma) configured for your Jira Service Management Portal, the forms will be displayed similar to how you would view and edit them in a browser. They are fully editable.
[++Previous++](https://docs.mobilitystream.com/mobility-for-jira/login-to-portal.md) [++Next++](https://docs.mobilitystream.com/mobility-for-jira/add-a-comment.md)
---
language: "en"
---
# Create Issue Shortcut
|---|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Create an issue template 1. Tap on + icon on top right of home screen 2. Tap on Create Issue option 3. Select Project 4. Select Issue Type 5. Fill in fields that should have default values 6. Tap on Add button 7. Give it name you recognize \& tap okay 8. The shortcut will appear on the home screen Use an issue template 1. Tap on your issue template shortcut 2. The create screen with your default values will be displayed 3. Fill in missing values or alter preselected values 4. Tap the create button 5. Your new issue is being created |
---
language: "en"
---
# Dashboard Shortcut
|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | 1. Tap on + icon on top right of home screen 2. Tap on Dashboard option 3. Find and pick applicable Dashboard 4. Dashboard Shortcut will be added to Home screen |
---
language: "en"
---
# Dashboards
On the Dashboards tab you can select a dashboard to display. We display a list of dashboards that you can star like for example on the project list to ensure that your top dashboard show on top.
A dashboard consists usually of several gadgets which you can assemble in Jira itself. A gadget may contain additional links. Links to Jira issues are clickable and the issue will be displayed in Mobility for Jira. Also some diagrams will allow you to tap a section that will bring up a list of Jira issues.
Pie Chart
Assigned to Me
Issue Statistics
Should gadgets not be displayed or not be displayed properly, please let us know. We recently upgraded our app to display native gadgets instead of web views.
---
language: "en"
---
# Does the Portal app support Refined?
The Portal app supports the majority of the functionality offered by Refined for Jira Server and Datacenter, without requiring any additional configuration.
The following Refined features ***are***currently supported:
* Use of the Refined theme, including:
* Header color, gradient, or image in the app bar
* Body color, gradient, or image
* Header/logo display at the top of the screen
* Individual structure and child theme support
* *Sites* menu to allow users to navigate between Refined sites
* Navigation using the Refined structures and their children, including links
* Refined search
* User/group permissions for sites and structures
* Customized layout in Issue Detail view, including comment location and assignee display
The following Refined features ***are not*** currently supported:
* Display of Jira Projects
* Custom HTML and CSS
---
language: "en"
---
# Download IPAs and APKs
## Overview
Security is a key aspect of our app design and we do not cache or store any issue data on the device. Credentials can be stored on the device itself but are encrypted and stored in the keychain for iOS. They are encrypted on Android devices with the AES-256 algorithm. We highly recommend that you use TLS/SSL to connect to your Jira system. This ensures that data in motion is encrypted. Mobility for Jira - Team is Mobile Device Management (MDM) ready and is able to use [MobileIron's VPN tunneling functionality](https://docs.mobilitystream.com/__attachments/a_d0b8c9c5d7f8fe9598aee5605328ec8edd2588b64d21e293fc44c3b63ec98461/Mobility%2520for%2520Jira%2520MobileIron%2520Configuration%2520Guide.pdf.md?cb=fe86ecd1357fa0621414df38da181c9f) or Apple's Per App VPN API as leveraged by AirWatch. Push Notifications are sent via Apple's APN/Google's GCM infrastructure and are not stored on MobilityStream's server.
## IPA and APK Wrapping
If you need an IPA/APK to wrap it for use with your Mobile Device Management (MDM) solution, you can download the most current version from here. This can also be used for distribution on your internal corporate app store. For iOS you will need to [resign the IPA with your Enterprise certificate](https://docs.mobilitystream.com/mobility-for-jira/resign-mobility-ipa-for-enterprise-deployment.md).
| | **Unsigned Package (Intune, AirWatch, etc)** | **MobileIron** | **Intune** |
|---------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| iOS | [mobility-for-jira-team-7.3.ipa](https://www.mobilitystream.com/downloads/mobility-for-jira-team-6.5.1.ipa) | Use App Store version (SDK included) | [See instructions](https://docs.mobilitystream.com/mobility-for-jira/intune-resign-app-and-enable-policies.md) |
| Android | [mobility-for-jira-team-4.7.3.apk](https://www.mobilitystream.com/downloads/mobility-for-jira-team-4.7.3.apk) [mobility-for-jira-team-5.4.4.apk](https://www.mobilitystream.com/downloads/mobility-for-jira-team-5.4.4.apk) [mobility-for-jira-team-5.4.5.apk](https://www.mobilitystream.com/downloads/mobility-for-jira-team-5.4.5.apk) | [mobility-for-jira-team-4.7.3-mi.apk](https://www.mobilitystream.com/downloads/mobility-for-jira-team-4.7.3-mi.apk) (wrapped) | [See instructions](https://docs.mobilitystream.com/mobility-for-jira/intune-resign-app-and-enable-policies-android.md) [mobility-for-jira-team-5.4.4-wrapped-signed.apk](https://www.mobilitystream.com/downloads/mobility-for-jira-team-5.4.4-wrapped-signed.apk) [mobility-for-jira-team-5.4.5-wrapped-signed.apk](https://www.mobilitystream.com/downloads/mobility-for-jira-team-5.4.5-wrapped-signed.apk) |
Please contact us for access: [support@mobilitystream.com](mailto:support@mobilitystream.com)
---
language: "en"
---
# Enterprise Mobility Management (EMM/MDM)
Mobility for Jira support Mobile Device Management and Enterprise Mobility Management solutions. Here is a list of documentation we provide based on our own testing. Please also ensure you have all technical documentation needed from your EMM/MDM vendor.
| **What are you trying to accomplish?** | **Document** |
|--------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Use AppConfig to preconfigure the app for enterprise users | [Mobile Device Management (MDM) - Team app](https://docs.mobilitystream.com/mobility-for-jira/mobile-device-management-mdm.md) [Mobile Device Management (MDM) - Portal App](https://docs.mobilitystream.com/mobility-for-jira/mobile-device-management-mdm-portal-app.md) |
| Deploy app via private app store (w/o MDM/protection policies) | [Resign Mobility IPA for Enterprise Deployment](https://docs.mobilitystream.com/mobility-for-jira/resign-mobility-ipa-for-enterprise-deployment.md) |
| Deploy app via Microsoft Intune with enabled protection policies for iOS | [Intune - Resign app and enable policies (iOS)](https://docs.mobilitystream.com/mobility-for-jira/intune-resign-app-and-enable-policies.md) |
| Deploy app via Microsoft Intune for Android | [Download IPAs and APKs](https://docs.mobilitystream.com/mobility-for-jira/download-ipas-and-apks.md) [Intune - Resign app and enable policies (Android)](https://docs.mobilitystream.com/mobility-for-jira/intune-resign-app-and-enable-policies-android.md) |
| Download the most current IPA or APK for wrapping | [Download IPAs and APKs](https://docs.mobilitystream.com/mobility-for-jira/download-ipas-and-apks.md) |
| Download the wrapped app for MobileIron for Android | [Download IPAs and APKs](https://docs.mobilitystream.com/mobility-for-jira/download-ipas-and-apks.md) |
| Use MobileIron on iOS | Use the Apple App Store version (SDK included) |
---
language: "en"
---
# Extend add-on trial for Jira Datacenter
Go to [my.atlassian.com](http://my.atlassian.com/) and select Licenses. Find the Mobility for Jira add-on then click on New Evaluation License (see screenshot). Copy/Paste the new evaluation key into Jira/Manage Add-ons/Mobility for Jira or any other Mobility Stream product you would like to extend.
Alternatively you can reach out to Atlassian Support.
1. Go to
2. How can we help you? \> **Product Trials - Start or extend your team's product trials**
3. Choose a topic \> **Extend product trials**
---
language: "en"
---
# Extend add-on trial for Jira Cloud
If your Mobility Stream add-on trial expired and you need more time, you can extend your trial by doing the following:
1. Go to
2. How can we help you? \> **Product Trials - Start or extend your team's product trials**
3. Choose a topic \> **Extend product trials**
4. Where is the product hosted? \> **Cloud**
5. Provide the related URL, SEN or EN of the product you wish to extend \> **Select the Mobility Stream product you wish to extend from the list**
6. Your Question \>**Please extend our trial for the Mobility Stream add-on above by 30 days.**
7. Click the **Submit** button
8. You might be asked by Atlassian to add a screenshot of a Mobility Stream approval email. You can email us ([support@mobilitystream.com](mailto:support@mobilitystream.com?subject=Jira%20Cloud%20Addon%20Extension&body=Please%20provide%20approval%20to%20extend%20the%20trial%20of%20the%20Mobility%20Stream%20[ADD_ON_NAME]%20addon%20by%2030%20days.)) and we will send you back the approval.
---
language: "en"
---
# External URL Shortcut
|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | 1. Tap on + icon on top right of home screen 2. Tap on External URL option 3. Enter the name for your Shortcut 4. Enter the URL for your Shortcut 5. Shortcut will be added to the Home screen |
---
language: "en"
---
# Filter Shortcut
|---|---------------------------------------------------------------------------------------------------------------------------------------------------------|
| | 1. Tap on + icon on top right of home screen 2. Tap on Filter option 3. Find and pick applicable Filter 4. Filter Shortcut will be added to home screen |
---
language: "en"
---
# Frequently Asked Questions
* [Open Issue Links with the Mobility for Jira App](https://docs.mobilitystream.com/mobility-for-jira/open-issue-links-with-the-mobility-for-jira-app.md)
* [Mobility for Jira Editions, Team \& Portal](https://docs.mobilitystream.com/mobility-for-jira/mobility-for-jira-editions-team-portal.md)
* [Receive Push Notification for Issue Creation](https://docs.mobilitystream.com/mobility-for-jira/receive-push-notification-for-issue-creation.md)
* [Using 2FA Authentication](https://docs.mobilitystream.com/mobility-for-jira/using-2fa-authentication.md)
* [Push Notification Setup](https://docs.mobilitystream.com/mobility-for-jira/push-notification-setup.md)
* [Does the Portal app support Refined?](https://docs.mobilitystream.com/mobility-for-jira/does-the-portal-app-support-refined.md)
* [Cloud Migration](https://docs.mobilitystream.com/mobility-for-jira/cloud-migration.md)
* [Google Authentication Login Issue](https://docs.mobilitystream.com/mobility-for-jira/google-authentication-login-issue.md)
[Enterprise Mobility Management (EMM/MDM)](https://docs.mobilitystream.com/mobility-for-jira/enterprise-mobility-management-emm-mdm.md)
* [Extend add-on trial for Jira Cloud](https://docs.mobilitystream.com/mobility-for-jira/extend-add-on-trial-for-jira-cloud.md)
* [Extend add-on trial for Jira Datacenter](https://docs.mobilitystream.com/mobility-for-jira/extend-add-on-trial.md)
* [How to send Debugging Information](https://docs.mobilitystream.com/mobility-for-jira/how-to-send-debugging-information.md)
---
language: "en"
---
# Getting Started with Jira Service Management (Portal Edition)
**Mobility for Jira - Portal** is a slick mobile app for [iOS](https://apps.apple.com/us/app/id1418961567) and [Android](https://play.google.com/store/apps/details?id=com.mobilitystream.mobilityjsd) specifically designed to easily create and manage requests on your **Jira Service Management Customer Portal**. You can make requests in different Service Management Portals as long as the Mobility for Jira Marketplace app is installed. You can comment, attach pictures, videos, audio files, and other attachments. You will receive push notifications immediately when your request is changing.
[Login to Portal](https://docs.mobilitystream.com/mobility-for-jira/login-to-portal.md)
[Create a Request](https://docs.mobilitystream.com/mobility-for-jira/create-a-request.md)
[Add a Comment](https://docs.mobilitystream.com/mobility-for-jira/add-a-comment.md)
If you are a service management agent or a regular Jira user please use **Mobility for Jira - Team** ([iOS](https://apps.apple.com/us/app/jira-connect-enterprise/id898500641?ls=1), [Android](https://play.google.com/store/apps/details?id=net.luethi.jiraconnectandroid.jiraconnect)) which is also included in your license.
---
language: "en"
---
# Getting Started with Jira (Team Edition)
The Mobility for Jira - Team is designed for **Jira users, Jira administrators,** and**Jira Service Management Agents** running on [iOS](https://apps.apple.com/us/app/jira-connect-enterprise/id898500641?ls=1) and [Android](https://play.google.com/store/apps/details?id=net.luethi.jiraconnectandroid.jiraconnect). The app supports issue operations (creation, view, editing), basic and advanced searches, filters to be displayed in the app, Agile boards (Kanban and Scrum), Jira Service Management, and Dashboards. It supports a variety of widely used third-party add-on fields. This app is licensed via the [Mobility for Jira add from the Atlassian Marketplace](https://marketplace.atlassian.com/apps/1211459/mobility-for-jira-mobile-for-enterprise-teams). Once the add-on is installed, all users are able to login and use the mobile app.
* [Login](https://docs.mobilitystream.com/mobility-for-jira/login.md)
[Home](https://docs.mobilitystream.com/mobility-for-jira/home-screen-shortcuts.md)
* [Jira Issues](https://docs.mobilitystream.com/mobility-for-jira/jira-issues.md)
* [Project Boards](https://docs.mobilitystream.com/mobility-for-jira/boards.md)
* [Jira Service Management](https://docs.mobilitystream.com/mobility-for-jira/jira-service-management.md)
* [Jira Product Discovery](https://docs.mobilitystream.com/mobility-for-jira/jira-product-discovery.md)
* [Jira Assets](https://docs.mobilitystream.com/mobility-for-jira/jira-assets.md)
* [Dashboards](https://docs.mobilitystream.com/mobility-for-jira/dashboards.md)
* [Profile](https://docs.mobilitystream.com/mobility-for-jira/profile.md)
---
language: "en"
---
# Google Authentication Login Issue
You might be seeing the following screen when trying to login to Jira Cloud when using the Google Authentication option:
This is related to a global change of Google security requirements for apps using only username and password without any additional factors. At this point Jira only requires username and password.
Here is a temporary work around until a fix becomes available. In your Google account you can do the following:
1. Select Manage Account Your Google Account
2. Select the Security tab
3. Scroll to the bottom and click on Less secure app access
4. Set Allow less secure apps to On
We are working on a fix to solve the issue so that the setting won't have to be changed going forward.
[https://support.google.com/accounts/answer/6010255?hl=en\&visit_id=637891669186594132-3111688974\&p=less-secure-apps\&rd=1#zippy=%2Cif-less-secure-app-access-is-on-for-your-account](https://support.google.com/accounts/answer/6010255?hl=en&visit_id=637891669186594132-3111688974&p=less-secure-apps&rd=1#zippy=%2Cif-less-secure-app-access-is-on-for-your-account)
---
language: "en"
---
# Home
## What is a Shortcut on my Home screen?
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| You can now fully configure your home screen by creating powerful shortcuts. Speed up many of your daily tasks and save a lot of time. * Make often-used issues, projects, boards directly accessible on your home screen * Pre-configure templates for fast issue creation and avoid repetitive entries * Configure searches, activity streams, scanners and place them on your home screen * Link external apps for fast access and authentication * Your configured home screen is displayed on all your devices on iPhone, iPad, Android, and Mac You are able to configure multiple shortcuts of the same issue type. Also shortcuts can be renamed or deleted by taping select and then taping on the rename or delete option on the bottom of the screen. Shortcuts can be move by long pressing and then moving them. |  |
## Available Shortcut Types
At the moment, there are about a dozen available Shortcut types. We will continue adding new ones over time.
| **Shortcut Icon** | **Shortcut Type** | **What is it for?** | **How to set it up?** |
|-------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------|
|  | Issue | Pin a frequently-used issue to your home screen for fast access. You can create as many issue short-cuts as you like. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/issue-shortcut.md) |
|  | Create Issue Template | Create a template for fast issue creation. Pre-configure project, issue type, and any field that you would like to pre-fill. When you create an issue just modify the fields that are different from your template. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/create-issue-shortcut.md) |
|  | Project | Create a project shortcut for often-used projects. Each shortcut is displayed with its project icon to make it easily recognizable. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/project-shortcut.md) |
|  | Board | Fast access shortcut to any Agile board directly from the home screen. Most useful for frequently accessed boards. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/board-shortcut.md) |
|  | Queue | Access a Jira Service Management Queue directly with one tap from your home screen instead of having to scroll to the list of available queues. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/queue-shortcut.md) |
|  | Activity Stream | Create a custom activity stream and filter by attributes you need to see. You can filter each stream by issues, projects, activity, and issue types. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/activity-stream-shortcut.md) |
|  | Search | Preconfigure a basic or advanced search (JQL) with this shortcut. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/search-shortcut.md) |
|  | Filter | Any previously created filter can be made accessible on the shortcuts home screen. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/filter-shortcut.md) |
|  | Scan | A scanner can be configured to scan supported codes (such as QR, Data matrix codes) and use the result for searching. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/scan-shortcut.md) |
|  | Dashboard | Set up a dashboard shortcut to access frequently used dashboards. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/dashboard-shortcut.md) |
|  | External URL | Set up other web applications to access directly from your home screen. If you set this up for Atlassian Cloud applications, authentication will be handled for you. | [Show me](https://docs.mobilitystream.com/mobility-for-jira/external-url-shortcut.md) |
## Tutorial Video
Watch this short Tutorial video to learn how to create and use some of the most common Shortcuts.
## Differences between iOS, Mac, and Android
The user interface is very similar on both iOS, Mac, and Android devices. There are a few slight differences:
* **Quick search bar**
* iOS \& Mac: is always visible and provides powerful quick search ability and searches through issues, projects, dashboards, filters, etc.
* Android: the same powerful search is available by tapping on the magnifying glass icon
* **Tile editing**
* iOS \& Mac
* press \& hold for rearranging of tiles
* hit Select then press on a tile and press the trash can icon (single tile only)
* Android
* press \& hold for rearranging of tiles
* hit the Pencil icon then select the tiles you want to remove and press the trash can icon (multiple tiles)
* **Change display to list view**
* iOS \& Mac: press the line icon on top left, press again to toggle back
* Android: currently only tile layout is supported
* **Create Issue Template Shortcut**
* Android: coming soon. Please let us know if you have an immediate need for this.
---
language: "en"
---
# How to send Debugging Information
At times you might be asked to provide debugging information to Mobility Stream. You can perform the following steps:
1. On the login page tap on the mobility stream logo five times.
You should see a confirmation toast. Refer to the screenshot below for guidance.
2. Login and reproduce the issue you are struggling with, this time logs will be collected
3. Log out and should be back on the Login page
4. Tap on the Support link on the bottom of the login screen, hit send (logs should be attached)
---
language: "en"
---
# Installation
## Overview
This page describes how to install the Mobility for Jira add-on for Jira Datacenter and Jira Cloud. It also shows how to install the corresponding apps on iOS and Android devices. The Team and Portal edition apps require the add-on to be install on your Jira Datacenter or Cloud instance. Besides managing the license for all your users, the add-on is also providing advanced functionality such as security and push notifications. Apps can also be pushed by your MDM system so that not every user has to install it individually.
## Install Add-On on Jira Datacenter (Administrator)
1. Log in to Jira Datacenter as a Jira Administrator
2. Select **Settings** from the top left (cog wheel)
3. Click on the **Manage Apps** menu entry
4. Enter ***mobility*** into the search box and hit enter
5. Select either **Free trial** or **Buy now** button on the Mobility for Jira entry
6. Confirm app installation by pressing **Accept \& install**
7. After installation you are redirected to MyAtlassian to get a trial license by pressing **Get license**
8. On MyAtlassian agree to the terms of use and press **Generate License**
9. Apply the generated license to your Jira Server
1. When the license has been generated you can press **Apply License** to copy it automatically.
2. Alternatively copy/paste it manually into the **License key** field found at \>Jira Administration\>Manage apps\>Mobility for Jira.
## Install Add-On on Jira Cloud (Administrator)
1. Log in to Jira Cloud as a Jira Administrator
2. Select **Apps** (from the top menu)
3. Then select **Explore more apps** from the menu, and enter ***mobilitystream*** into the search box and hit enter
4. Select the Mobility for Jira listening
5. Press the **Try it free** button on the top right side of the listing
6. A new screen will load on which you can confirm by hitting the **Start trial** button
## Install App on iOS Device (User)
1. On your iPhone or iPad open the Apple App Store app
2. Tap the **Search** button (bottom right)
3. Enter ***mobilitystream*** into the search field
4. Install the correct App
1. If you are a Jira user, administrator, or JSD agent, scroll to **Mobility for Jira - Team** and tap the **Get** button
2. If you are a Jira Service Management Portal user, scroll to **Mobility for Jira - Portal** and tap the **Get** button
5. After the installation open the application
[Learn how to login](https://docs.mobilitystream.com/mobility-for-jira/login.md)
## Install App on Android Device (User)
1. On your Android device open the Google Play Store app
2. Type into the search bar ***mobilitystream***
3. Install the correct App
1. If you are a Jira user, administrator, or JSD agent, scroll to **Mobility for Jira - Team** and tap the row
2. If you are a Jira Service Management Portal user, scroll to **Mobility for Jira - Portal** and tap the row
4. Hit the **Install** button to download and install the app
5. After the installation open the application
[Learn how to login](https://mobilitystream.atlassian.net/wiki/spaces/MFJA/pages/277970955/Login)
---
language: "en"
---
# Easy Installation and Configuration with Microsoft Intune
Mobility for Jira provides native apps that includes the Intune SDK. Apps do not have to be wrapped and are easy to install and configure.
1. Install app on mobile device
**Apple App Store**
[Mobility for Jira - Intune](https://apps.apple.com/us/app/mobility-for-jira-intune/id6756030757)
[Mobility Jira Portal Intune](https://apps.apple.com/us/app/mobility-jira-portal-intune/id6757196132)
**Google Play Store**
[Mobility for Jira - Intune](https://play.google.com/store/apps/details?id=com.mobilitystream.android.jiraconnect.intune)
[Mobility Jira Portal Intune](https://play.google.com/store/apps/details?id=com.mobilitystream.mobilityjsd.intune)
2. Register app with Intune
3. Admin to Login to
Admin to Grant admin consent
Enterprise apps \> All applications \> Mobility for Jira
Permissions \> Grant admin consent for Mobility Stream
---
language: "en"
---
# Intune - Resign app and enable policies (iOS)
These instructions are deprecated. Mobility for Jira has now a native Intune version, no wrapping required. See this [document](https://docs.mobilitystream.com/mobility-for-jira/login-with-microsoft-intune.md).
These instructions are for Intune and the iOS Mobility for Jira app. You will need the following:
* [IPA file](https://docs.mobilitystream.com/mobility-for-jira/download-ipas-and-apks.md) (input app)
* You need to create three provisioning profile for the app
* App Provisioning profile
* Share Extension Provisioning profile
* Safari Extension Provisioning profile
* Your organization's distribution certificate
In order to resign the app, the following command needs to be used. Please replace the placeholder between ## with the actual values:
Bash
./IntuneMAMPackager/Contents/MacOS/IntuneMAMPackager
-i ##path to input app##
-o ##path to output app##
-p ##path to app provisioning profile##
-c ##distribution certificate SHA1##
-x "
##path to app provisioning profile##
##path to share extension provisioning profile##
##path to safari extension provisioning profile##
"
-e
-v true
Here is some additional information:
To resign the app, three new app IDs should be created. One each for the App, Share Extension, and Safari Extension.
For example:
* com.example.appID
* com.example.appID.Share
* com.example.appID.Safari
---
language: "en"
---
# Intune - Resign app and enable policies (Android)
These instructions are deprecated. Mobility for Jira has now a native Intune version, no wrapping required. See this [document](https://docs.mobilitystream.com/mobility-for-jira/login-with-microsoft-intune.md).
These instructions are for Intune and the Android Mobility for Jira app. We publish [signed and wrapped files for Intune](https://docs.mobilitystream.com/mobility-for-jira/download-ipas-and-apks.md). If you want to wrap and/or sign the APK yourself, you will need the following:
* [APK file](https://docs.mobilitystream.com/mobility-for-jira/download-ipas-and-apks.md) (input app)
* Your organization's distribution key or create a new one
* Windows computer
1. Download \& install the wrapping tool:
2. Download \& install a Java JRE:
3. Run the wrapping tool from step 1 in PowerShell:
1. Import-Module "C:\\Program Files (x86)\\Microsoft Intune Mobile Application Management\\Android\\App Wrapping Tool\\IntuneAppWrappingTool.psm1"
2. invoke-AppWrappingTool -InputPath .\\app\\jiraconnect.apk -OutputPath .\\app_wrapped\\jiraconnect.apk -Verbose
4. Sign the wrapped APK from above step with the apksigner tool
1.
2. `apksigner sign --ks yourkey.jks jiraconnect-wrapped.apk`
**References**
---
language: "en"
---
# iOS app Configuration
Mobility for JIRA - Team can be pre-configured during app resigning.
The configuration object should be inserted into root of the Info.plist for key "CONFIGURATION" as Dictionary before app re-signing.
Info.plist contains an object with key "CONFIGURATION_EXAMPLE" that follows proper format.
Configuration object should follow the following format:
* ADD_ACCOUNT (Bool): ***YES*** , if app allows user to add new accounts. ***NO*** , otherwise. Optional. Default value: ***YES***.
* REMEMBER_CREDENTIALS (Bool): ***YES*** , if app should remember user's credentials by default. ***NO*** , otherwise. Optional. Default value: ***NO***.
* ACCOUNTS (Array): array of account configuration objects. Element type: Dictionary.
Account configuration object should follow the following format:
* UID (String): Unique identifier of the account. If two accounts have same identifier, one of them will be ignored. Required.
* URL (String): Base URL of JIRA instance. Required.
* AUTH_TYPE (String): ***credentials*** , if only login using username and password is allowed. **web** , if only login using web is allowed. any, if both methods are allowed. Optional. Default value: **any**.
* REMEMBER_CREDENTIALS (Bool): ***YES*** , if app should remember user's credentials for the account by default. ***NO***, otherwise. Optional. Default value: value specified for the same key in configuration object.
* CAN_DELETE (Bool): **YES** , if a user can delete the account. ***NO*** , otherwise. Default value: ***NO***.
Example of configuration:
---
language: "en"
---
# Issue Shortcut
|-------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|  | Create Issue Shortcut 1. Tap + icon on top right 2. Select Issue shortcut type 3. Search and select issue that should appear on home screen 4. Selected issue will appear on home screen as a shortcut Rename Shortcut 1. Tap Selection button on top right 2. Select the shortcut to rename 3. Tap Rename button on bottom left 4. Type in the new name and hit done |
---
language: "en"
---
# Jira Assets
## Asset Management
We support [Jira Assets](https://confluence.atlassian.com/servicemanagementserver/getting-started-with-assets-1044784303.html). You can display and edit an Asset, can navigate through the hierarchy, scan a QR code associated with an Asset to either find it or select it as a field option. Watch our [Video Tutorial](https://youtu.be/lvS_19m_UhA).
### Display and Edit Assets
To display an existing Asset, tab on the preconfigured Assets icon on the Home Screen (Home \> Assets) or scan an associated QR code (Home \> Scan). Also, the Quick Search includes now matching Assets objects. You can navigate through the Asset schema hierarchies. Once the Asset is displayed, most fields can be edited by taping on the field.
### Select an Asset as a Field Option
When you have a field from Jira Assets defined on your Jira Request form it will display the field name. You can now select any option available in Assets through the dropdown field. If your Asset Management supports QR codes, you can simply scan the QR code and the correct Assets option will be selected.
### Work with Pre-existing Bar Codes
You might have objects that already come with pre-existing bar codes. Re-tagging all of these objects with the Jira Assets QR code might not be feasible or desired. The Mobility for Jira app allows you to work with your existing bar codes.
For each Jira Asset text field, you can invoke the bar code scanner by double taping on the field. When you tap the **Scan Barcode** option the camera scanner will come up and you can scan an existing bar code. The alpha-numeric representation of the bar code is saved in your text field. After you store it, it will be available for search.
### Geolocation
You may want to track the location of an Asset object. This is easily possible with Mobility for Jira.
On iOS, you can tap on an Asset text field, then pick **Select Location** in the context menu. A map opens with the current location selected. You can change the location by moving the pin on the map. Once you are satisfied press **Save**. Latitude/Longitude values are stored in the text field. Each time the Asset is viewed in the app, a pin shows up next to the value to display the location on the map.
On Android, tap on the three dots on the right side of the field, then pick **Map** to enter the location.
Alternatively, your administrator can add **#geo** to the description of the Asset field. Each mobile users now sees a location pin next to this field and can enter current location information by pressing the pin without have to go to the context menu.
---
language: "en"
---
# Jira Issues
You can work with issues the same way like you are used to within Jira. Issues can be configured depending on issue type and will display the expected field and have the behavior determined by its workflow.
## Find Issues
There are several way in which you can find issues.
### Quick Search
If you know part of the issue key or a keyword you can simply go to your **home screen** and enter it in the top search bar (Android: you will need to press the magnifying glass icon first). The Mobility app will display a matching list of issues, projects, dashboard, and filters. If your Jira instance is large you may want to be more specific to create the result needed.
Use the Search Bar on top of Home
Type in a keyword or partial issue key
### Search Shortcut
On the Home screen, press the Search shortcut.
**Basic Search**
You can use the Basic search mode to find issues. You can provide search criteria by selecting one or multiple values for each field by pressing on the field button underneath the search bar text field. To view more fields swipe the field list to the left. In addition you can enter text into the search bar text field. All values are used in AND search operation.
**Advanced Search**
To find issues using advanced search (JQL), press the Advanced text link to the right of the search bar text field. You can start typing JQL. The app has a type-a-head/autocomplete feature that allows you to select an option without fully typing it. After typing a few characters you will see options appearing on the bottom of the search bar text field. Select one of the options and the JQL portion will be populated in the search bar.
Search Shortcut
Basic Search
Advanced Search
### Search with QR Code
If your organization uses QR codes and real-world objects are tagged with codes that match issues or issue fields in Jira, you can search for issues via QR codes. You will need to configure a Scan Shortcut on your Home screen. View the documentation [here](https://docs.mobilitystream.com/mobility-for-jira/scan-shortcut.md).
## Create Issues
You can create new issues directly in the app. For example, they can be created via
* **Home \> Create Issue** shortcut: select a Project and Issue Type
* **Projects \> Board** by using the + button: select an Issue Type, Project is already pre-populated
After that the correct form for the selected issue type will be displayed and can be filled out. All required fields are marked with a red asterisk \*. When you are done, press the **Create** button on the top right. The issue will be created and displayed on the screen.
Create Issue Shortcut
Project Board Create Issue Button
Create Issue screen
## Edit Issues
Tap on any issue on an issue list or board and its detail view will come up. Fields can be edited by
* tapping on a field for a single field edit
* tapping the **Edit** button on the top right to edit multiple fields
Once you are done, tap the **Save** button. For single field edits, the Save button does not have to be pressed.
Detail screen with Edit button
Edit screen
## Clone Issues
Issues can be cloned between project and issues types. On an issue detail screen press **... \> Clone**. This will bring up the Clone screen that allows you to select the summary, project, and issue type for the newly created issue.
Clone menu option
Clone screen
## Set Reminders for Issues
Set a reminder for an issue on the detail view **... \> Remind Me...**. You will be able to select from a few options or set a custom time and date to be reminded.
The reminder will appear as a Notification on your device at the defined time.
Reminder menu option
Reminder options
## Forms
If you are using [Forms](https://support.atlassian.com/jira-service-management-cloud/docs/what-are-forms/) (previously ProForma) in Jira, you can easily add, view, and edit them in Mobility for Jira. To view a form, pick an issue that has a form attached and scroll to the Forms Section. Each attached form is listed with its name and current status. You will be able to display the form by tapping on the form entry. When pressing edit the form becomes editable. Also you have several other options to make the form internal/external, view it as PDF or XLSX.
Forms and their status on Issue Detail
Filled out form
To attach a new form scroll to **Forms \> Add Forms**then pick an available form. Once a form is filled out it can be closed for customer editing, submitted, made external/internal, deleted, or exported as a PDF or XLSX file.
Add a new form by tapping Add Form
Pick from available forms
Form options
## Geolocation
If you have issue fields that contain geolocations in latitude, longitude format (for example 41.882685, -87.623225), a location pin will be displayed next to it. By pressing the pin, a map is displayed containing the location. There is a share button that allows to share the location with installed apps such as Apple Maps, Google Maps, and Waze.
A Location Pin is displayed if a field contains location data
The location is displayed on a map and can be shared with another mapping application
Similar functionality is available for Jira Assets as well as within our Mobility for Jira - Portal app.
---
language: "en"
---
# Jira Product Discovery
With Mobility for Jira you can work with Jira Product Discovery projects and issues. Once you select a Jira Product Discovery project a list of JPD issues is displayed. You can scroll to view additional fields. Issues are enumerated to allow you to more easily orient yourself when scrolling to the right. Both enumerations and column titles are pinned on the screen.
You can edit some values directly on the table view by tapping on the value. To select a JPD issue and view more details tap on the summary.
Several different views are supported. Some views support grouping of JPD issues.
The JPD issue detail view consists of the Overview section and the Comment section. Overview shows all fields that contain a value. Comments shows all comments added to this issue. On this section you can also add a new comment. You can toggle back and forth by tapping on the Overview and Comments buttons.
Most fields support editing by tapping directly on the field and edit the content inline. For some field types, a popup appears to support the selection.
New ideas/JPD issues can be created by tapping the + button on the top right.
Rich text field entry/editing is currently not supported.
Android is currently not supported but will be available shortly.
---
language: "en"
---
# Jira Service Management
Mobility for Jira is specifically designed to provide strong support for Jira Service Management (JSM). This includes access to Agent functionality as well as mobile access to the JSM Portal.
If you are a JSM Client, you can use our Mobility for Jira - Portal app to access the JSM Portal. Find more information [here](https://docs.mobilitystream.com/mobility-for-jira/getting-started-with-jira-service-management-porta.md).
## Queues
Queues are displayed as defined in the Jira web version. If you would like to add an additional queue, this needs to be done in the Jira web version but will show up immediately in Mobility for Jira. Since Mobility for Jira caches some of the data, the queue view may need to be pulled down to be refreshed. Each Queue shows the number of Jira issues it includes. Tapping a queue displays a issue list.
## JSM Request
Jira issues for a JSM project include a section for SLAs and Service Management Request. The SLA section includes all SLAs for that specific issue. If you need to add additional SLAs you need to do this in Jira itself.
The JSM Request section includes a request type field. A request type can also be selected in Mobility for Jira. The channel field indicates through which channel the issue was reported. This field is not editable.
## Approvals
When you are the approver of a Jira issue, this will be indicated in the header section of an issue. You can simply press **Approve** or **Decline** directly on the notification buttons.
Alternatively, you can tap the **Status** field, which will open up the Transition screen as usual, then select **Approve** or **Decline**.
## Asset Management
We support [Jira Assets](https://confluence.atlassian.com/servicemanagementserver/getting-started-with-assets-1044784303.html). You can display and edit an Asset, can navigate through the hierarchy, scan a QR code associated with an Asset to either find it or select it as a field option. Watch our [Video Tutorial](https://youtu.be/lvS_19m_UhA).
### Display and Edit Assets
To display an existing Asset, tab on the preconfigured Assets icon on the Home Screen (Home \> Assets) or scan an associated QR code (Home \> Scan). Also, the Quick Search includes now matching Assets objects. You can navigate through the Asset schema hierarchies. Once the Asset is displayed, most fields can be edited by taping on the field.
### Select an Asset as a Field Option
When you have a field from Jira Assets defined on your Jira Request form it will display the field name. You can now select any option available in Assets through the dropdown field. If your Asset Management supports QR codes, you can simply scan the QR code and the correct Assets option will be selected.
### Work with Pre-existing Bar Codes
You might have objects that already come with pre-existing bar codes. Re-tagging all of these objects with the Jira Assets QR code might not be feasible or desired. The Mobility for Jira app allows you to work with your existing bar codes.
For each Jira Asset text field, you can invoke the bar code scanner by double taping on the field. When you tap the **Scan Barcode** option the camera scanner will come up and you can scan an existing bar code. The alpha-numeric representation of the bar code is saved in your text field. After you store it, it will be available for search.
To find an Asset with a specific bar code, simply go to the schema, tap on the scanning icon on the top right of the screen. The camera will open, scan the bar code of the object you want to display on your mobile. If you stored this bar code in any text field in any object type of the schema, the correct object will be displayed.
If you have a large number of existing bar codes from other Asset Management systems, you can load these bar codes into Assets with the import function. Make sure the alpha-numeric representation of the bar code is stored in an Asset text field. After that all your Assets will be available to be scanned with your pre-existing bar code. No retagging necessary!
## Customer \& Organizations
On mobile customers and organizations are displayed. Associated open and closed requests as well as customers/users can be viewed.
## Tutorial Video
Watch our JSM Tutorial video to learn how both Jira apps (Team \& Portal) can be used together by your JSM Clients and Agents.
---
language: "en"
---
# Login
## Login with Atlassian ID (Jira Cloud)
When adding an account on your mobile device, you can choose to login via your Atlassian ID. You need to enter your e-mail address and password. The first time, the app will automatically create a Jira API key associated with your account. You will receive a confirmation e-mail. After that you will not have to login again. You can always revoke API tokens by visiting: .
 ' 
## Login with Jira Web Address (Jira Cloud \& Jira Data Center)
You can also login by entering the web address that you use in your web browser to access Jira (without the path information). The address usually starts with [https://.](#) Below are a few examples of correctly and incorrectly formatted URLs. An easy way to determine the correct URL is to log into Jira using your web browser.
### With Single Sign-On
Once you entered your web address, use the "Login with 🌐" button.
The app displays Jira login screen in a web view. Enter your credentials and then press login. After successful authentication with your Identity Provider, the app will log you in. This is also the default login for Jira Cloud. You will be directed to this automatically when typing in a Jira Cloud address.
**Cannot login?**
Should you have problems with other methods, you should try this login method
### Without Single Sign-On
Once you entered your web address, use the "Proceed to Login" button.
You can choose if you want the app to log you in automatically. Should you decide to do so, enable the "Keep me logged in" switch. The app will be storing your credentials in the keychain (iOS) or in encrypted format (Android)
*** ** * ** ***
## Valid Web Addresses
| **Valid** | **Invalid** |
|-------------------------------------------------------------------------|----------------------------------------------------------------|
| [https://jiraconnect.atlassian.net](https://jiraconnect.atlassian.net/) | [jiraconnect.atlassian.net](http://jiraconnect.atlassian.net/) |
| [http://jira.jiraconnect.com:8080](http://jira.jiraconnect.com:8080/) | |
| | [yourcompany.com](http://yourcompany.com/) |
| | 10.0.1.27 |
For Jira Cloud the URL will either end with [atlassian.net](http://atlassian.net/) or [jira.com](http://jira.com/) and starts with https.
## Manage Accounts
On the account page you can add and remove accounts. To remove accounts, left swipe the account name and then tap delete. New accounts can be added by tapping the **Add Account** button. To get to the account page when your account is set to log in automatically, you can simply go to the Profile area and the log out of the application. After that you will get to the Account page.
## CAPTCHA
When the username/password combination was enter wrong a few times in a row, Mobility for Jira may display a CAPTCHA that needs to be solved. It is important to not only correctly type the displayed word but also to correct the wrong username/password. If you like to refresh the CAPTCHA and get a new image, simply hit the **Login** button. The CAPTCHA is produced by Jira itself, the Mobility for Jira app has no control over it.
 
When you receive the CAPTCHA, ensure that you are also correcting the username/password combination in addition to resolving the CAPTCHA. The CAPTCHA is part of Jira itself.
---
language: "en"
---
# Login to Portal
## Sign in
If you already have a service desk user account, simply tap the **Add Account** button. Enter your Jira Service Desk account address into the Jira URL field. The correct format looks like this:
* [https://yourcompany.atlassian.net](https://yourcompany.atlassian.net/)
*
*
Then enter your **username** or **email address** and then **Proceed to Login**. The app will ask for a password either on the Atlassian Account Sign-in page, your Single Sign-On page, or the Atlassian username sign-in area.
### Sign up
You can also sign-up for an account, if the Jira Service Desk configuration allows it, by hitting **Sign-up**. You will receive a link that you can follow to create a Jira Service Desk Portal account.
### Support
When help about the app itself is needed, press **Support** and you will be able to edit a support email that will create a ticket in MobilityStream's service desk. If you are using a branded app, the support email may go to your organization directly.
### Documentation
The documentation link leads you to this Confluence user guide.
[++Next++](https://docs.mobilitystream.com/mobility-for-jira/create-a-request.md)
---
language: "en"
---
# Login with Microsoft Intune
## Overview
Mobility for Jira provides now a version of its app that natively supports Intune, no wrapping required. The app can be distributed to an end user via the Public or a Private App Store. Once a user opens the app, they need to register one-time with Intune and afterwards can use the app normally.
Here are the locations where the latest version of the native Intune apps can be downloaded from:
**Apple App Store**
* [Mobility for Jira - Intune](https://apps.apple.com/us/app/mobility-for-jira-intune/id6756030757)
* [Mobility Jira Portal Intune](https://apps.apple.com/us/app/mobility-jira-portal-intune/id6757196132)
**Google Play Store**
* [Mobility for Jira - Intune](https://play.google.com/store/apps/details?id=com.mobilitystream.android.jiraconnect.intune)
* [Mobility Jira Portal Intune](https://play.google.com/store/apps/details?id=com.mobilitystream.mobilityjsd.intune)
## Step-by-Step Initial Registrationa and Login
**Android-only pre-requisite**
Install the [Microsoft Intune Company Portal app](https://play.google.com/store/apps/details?id=com.microsoft.windowsintune.companyportal&pcampaignid=web_share) from the Google Play Store.
### Register with Intune
Install the app from a public App Store (see above) or via your private App Store. When you open the app for the first time, an Intune registration page is displayed. Tap on the Register button. You will then be prompted to login with your credentials (such as [your-name@company.com](mailto:your-name@company.com)) and your password. Depending on your setup you might be prompted to authenticate via MFA (such as Microsoft Authenticator). Upon successful registration a Get Access page will be displayed.
Register app
Enter your credentials
Enter your password
Confirm access
### Create a PIN
Intune will prompt you to create and confirm a PIN,
Create a PIN
Re-enter your PIN
### Login to App
After successfully completing the steps above you will be presented with the regular app login page. Enter your credentials (Jira Cloud) or your Jira Url and your credentials (Jira Data Center).
Should you want to unregister Intune, log out of the app and tap the Unregister button at the bottom. Please remember, the native Intune app will need to be connected to Intune otherwise it won't work. If you don't require Intune use our regular Team app,
Mobility Login page
---
language: "en"
---
# Mobile Device Management (MDM) - Team app
Mobility for Jira supports the AppConfig standard for Mobile Device Management. This is supported by several MDM systems such as Microsoft Intune, MobileIron, JAMF, AirWatch, etc. With this standard you can control some security features and push out settings to your Mobility for Jira users.
Example configuration:
VERSION
1
ADD_ACCOUNT
CAN_REMEMBER_CREDENTIALS
REMEMBER_CREDENTIALS
ACCOUNTS
UID
account_1
URL
https://jira.yourorganization.com
USERNAME
{{UserPrincipalName}}
REMEMBER_CREDENTIALS
CAN_DELETE
UID
account_2
URL
https://jira.yourorganization.com
AUTH_TYPE
web
REMEMBER_CREDENTIALS
CAN_DELETE
`VERSION`: integer - integer value that represents version of configuration. When value changes clients will remove all previously created accounts and will create new accounts from configuration.
`ADD_ACCOUNT`: bool - if value is set to `false` users will not be able to add account on their own. Only accounts provided by this configuration will be available for them. Default value: `true`.
`REMEMBER_CREDENTIALS`: bool - global setting that defines initial value of `Keep me logged in` switches in the app. Default value: `false`.
`CAN_REMEMBER_CREDENTIALS`: bool - if value is `false`, `Keep me logged in` switches will be disabled in the app and users will not be able to ask app store credentials. Default value: `true`
`SUPPORT_EMAIL`: string - use this parameter if want to provide custom support email for users of your organization. Default value: `support@mobilitystream.atlassian.net`
`SHOW_DESCRIPTION_ON_ISSUE_TABLE`: bool - if value is `true` issue list screen will display up to 5 lines of issue description in each row. Default value: `false`
`ACCOUNTS`: array - list of pre-configured account. Element type: `dict`
Account configuration has the following structure:
`UID`: string (required) - unique identifier of account. If value is missing, account with this configuration will not be created.
`URL`: string (required) - Jira URL. If value is missing, account with this configuration will not be created.
`USERNAME`: string - predefined username. Used only for regular login, ignored if `Login with 🌐` option used.
`AUTH_TYPE`: string, possible values: `credentials`, `web`, `any` - authentication type for this account. With `credentials` auth type, users will not be able to use `Login with 🌐`. With `web` auth type users will not be able to use regular login and will be forced to use web login. Default value: `any`
`REMEMBER_CREDENTIALS`: bool - global setting that defines initial value of `Keep me logged in` switches in the app. Default value: `false`. This value overrides global value for the account.
`CAN_REMEMBER_CREDENTIALS`: bool - if value is `false`, `Keep me logged in` switches will be disabled in the app and users will not be able to ask app store credentials. Default value: `true`. This value overrides global value for the account.
`CAN_DELETE`: bool - if value is `true`, user will be able to use swipe to delete for the account. Default value: `false`.
---
language: "en"
---
# Mobile Device Management (MDM) - Portal App
Mobility for Jira supports the AppConfig standard for Mobile Device Management. This is supported by several MDM systems such as Microsoft Intune, MobileIron, JAMF, AirWatch, etc. With this standard you can control some security features and push out settings to your Mobility for Jira users.
Example configuration:
VERSION
1
ADD_ACCOUNT
ACCOUNTS
UID
account_1
URL
https://jira.yourorganization.com
CAN_DELETE
UID
account_2
URL
https://jira.yourorganization.com
CAN_DELETE
`VERSION`: integer - integer value that represents version of configuration. When value changes clients will remove all previously created accounts and will create new accounts from configuration.
`ADD_ACCOUNT`: bool - if value is set to `false` users will not be able to add account on their own. Only accounts provided by this configuration will be available for them. Default value: `true`.
`ACCOUNTS`: array - list of pre-configured account. Element type: `dict`
Account configuration has the following structure:
`UID`: string (required) - unique identifier of account. If value is missing, account with this configuration will not be created.
`URL`: string (required) - Jira URL. If value is missing, account with this configuration will not be created.
`CAN_DELETE`: bool - if value is `true`, user will be able to use swipe to delete for the account. Default value: `false`.
[Next Page](https://docs.mobilitystream.com/llms-full.txt/1)