Check the current status of our cloud apps.
Have an issue or a bug to report? Have an idea for a new feature? Submit a ticket via our Support Portal!
Support Portal/Service Desk - Planned Maintenance Downtime (29/Jun/2020)
To deliver a better support experience to our users, the TM4J Service Desk will undergo infrastructure migration and upgrade on Monday 29th of June, starting at 9 am UTC (5 am EDT). The Service Desk portal will not be available for up to 3 hours until the migration has finished.
During this maintenance window, the TM4J Service Desk will be read-only, i.e. it will not be possible to create new support tickets or make changes to any of the existing tickets. Please also note, that it could take up to 9h hours after the Service Desk migration for some attachments to appear in the tickets.
All service desk customers will receive a separate email with instructions on how to access the new Service Desk once the migration is complete.
We appreciate your patience and understanding. You can track the progress of the Service Desk migration on the TM4J status page.
Planned Maintenance Downtime (6/Jun/2020)
To ensure uptime and stability of the platform, we are planning to perform an upgrade on our infrastructure on Saturday 6th of June at 1 pm UTC, for up to 4 hours.
During this maintenance window, the TM4J Cloud platform will be inaccessible, including access to the app in Jira or via the REST API. All operations will resume immediately after the maintenance window, however, you may experience some form of performance degradation up to 24 hours after this maintenance period.
Don't worry: TM4J will just get better and faster once the maintenance is done :) Your data will be safe, and you should be able to enjoy TM4J again right after we are done with the under the hood tweaks. Please, read below to understand more about how this might affect you.
We appreciate your patience and understanding. As always, if you have questions or issues, please submit them at our support portal. Additionally, you can track the status and progress of the planned maintenance here.
Can I access the app during the weekend?
During the maintenance window, the whole TM4J Cloud platform will be offline for maintenance, which means that TM4J Cloud won't be accessible from within Jira or from the REST API. After the maintenance window, you might experience some performance degradation over the next 24h hours.
Is the API affected by the maintenance downtime window?
Yes, all services related to TM4J Cloud will be offline for maintenance.
How does this affect my usage of the TM4J public API: https://api.adaptavist.io/tm4j/v2?
During the maintenance downtime window, the public API will be offline. Any requests to TM4J via the public API will fail over the maintenance downtime window. Please ensure that your automated routines are stopped over this period or are prepared to handle connection errors.
Moving forward the base URL of the API will change as well. This should be transparent for you as all the incoming traffic will be redirected from the old URL to the new one, for a reasonable timeframe. We will inform you in advance when it is time to change the URL to the new one, to prevent integrations using the API to break.
How does this affect my usage of the private API: https://avst.connect.adaptavist.com/atm-addon/rest/tests?
During the maintenance downtime window, the private API will be offline. Any requests to TM4J via the private API will fail over the maintenance downtime window. Please ensure that your automated routines are stopped over this period or are prepared to handle connection errors.
The private API is designed exclusively to serve the frontend application. This means that the private API is not supported or designed for any other use, such as external integrations or scripts. Due to not being a publicly supported API, its endpoints can change at any time without any notice. Additionally, if you make any experimental use of the private API, you will be impacted after the maintenance period as well: the private API URL will change with no backwards compatible redirection of traffic.
Anyone using the private API should consider making an upgrade and use the public API instead, which is very reliable, stable and always backwards compatible. Please, check our public API documentation for more information on how to use it.
Rest API Changes for GDPR Compliance (from 29/Apr/2019)
On 29 April 2019, Atlassian made changes to the data that they supply via their API in order to be GDPR compliant.
Please read below to learn about changes to REST API and the importing/exporting of user data that Test Management for Jira (TM4J) Cloud is introducing in conjunction with these changes.
REST API Changes
Previously, API definitions used Atlassian User Keys to identify users. This has been deprecated by Atlassian and was removed on April 29, 2019.
Atlassian Account IDs have replaced User Keys to represent users, so TM4J Cloud has also made this change by replacing any fields that require User Keys with Account IDs.
To interact with the API going forward, you must use these new fields. For example, if you have written a script that uses a userKey field, such as owner, you must change it to use a corresponding accountId field instead, such as ownerId.
Import and Export Data
We have added a new field named Owner (Account ID) to all data exported from Test Management for Jira, and, in addition, the import provides this extra field for field mapping.
If you wish to import any previous backup data after 29 April 2019, you will need to export your data once again to make sure you will have the new Account ID field included in your exported file.
Find Your Atlassian Account ID
To find your Atlassian Account ID, go to your profile in the Jira menu.
Your Account ID appears in the page URL.