--- version: "latest" variant: "Golive Cloud" language: "en" --- # Apwide Golive ## Apwide Golive Test Environment \& Release Management for Jira Cloud [Get Started](https://golive.apwide.com/doc/latest/cloud/getting-started.md) ### Release Notes * #### [2026-07-30](https://golive.apwide.com/doc/latest/cloud/2026-07-30.md) July 29, 2026 * #### [2026-06-23](https://golive.apwide.com/doc/latest/cloud/2026-06-23.md) June 24, 2026 * #### [2026-05-22](https://golive.apwide.com/doc/latest/cloud/2026-05-22.md) May 21, 2026 ### Topics * #### [About Golive](https://golive.apwide.com/doc/latest/cloud/about-golive.md) * #### [Get Started](https://golive.apwide.com/doc/latest/cloud/getting-started.md) #### [Navigate Golive](https://golive.apwide.com/doc/latest/cloud/browse-your-environments.md) #### [Environment Concepts](https://golive.apwide.com/doc/latest/cloud/environment-concepts.md) * #### [Build the Environment Inventory](https://golive.apwide.com/doc/latest/cloud/build-the-environment-inventory.md) #### [Work with Environments](https://golive.apwide.com/doc/latest/cloud/organizing-environments.md) #### [Manage Environment Details](https://golive.apwide.com/doc/latest/cloud/manage-environments-information.md) #### [Track Environments](https://golive.apwide.com/doc/latest/cloud/track-your-environments.md) #### [Schedule Environments](https://golive.apwide.com/doc/latest/cloud/scheduling-environments.md) #### [Timelines](https://golive.apwide.com/doc/latest/cloud/timelines-in-jira.md) #### [Jira Automation](https://golive.apwide.com/doc/latest/cloud/automation-for-jira.md) #### [Rovo Agent](https://golive.apwide.com/doc/latest/cloud/rovo-agent.md) #### [Integrations](https://golive.apwide.com/doc/latest/cloud/integrations.md) #### [Administrate](https://golive.apwide.com/doc/latest/cloud/administrator-guide.md) #### [Glossary](https://golive.apwide.com/doc/latest/cloud/glossary.md) * #### [Troubleshooting](https://golive.apwide.com/doc/latest/cloud/troubleshooting.md) #### [Release Notes](https://golive.apwide.com/doc/latest/cloud/what-s-new.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2022 * [2022-11-24](https://golive.apwide.com/doc/latest/cloud/v-9-6-x.md) * [2022-09-21](https://golive.apwide.com/doc/latest/cloud/v-9-5-x.md) * [2022-09-07](https://golive.apwide.com/doc/latest/cloud/v-9-4-x.md) * [2022-08-25](https://golive.apwide.com/doc/latest/cloud/v-9-3-x.md) * [2022-07-18](https://golive.apwide.com/doc/latest/cloud/v-9-2-x.md) * [2022-06-27](https://golive.apwide.com/doc/latest/cloud/v-9-1-x.md) * [2022-06-01](https://golive.apwide.com/doc/latest/cloud/v-9-0-0.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2023 * [2023-12-19](https://golive.apwide.com/doc/latest/cloud/v-9-20-x.md) * [2023-12-05](https://golive.apwide.com/doc/latest/cloud/v-9-19-x.md) * [2023-11-23](https://golive.apwide.com/doc/latest/cloud/v-9-18-x.md) * [2023-10-12](https://golive.apwide.com/doc/latest/cloud/v-9-17-x.md) * [2023-09-26](https://golive.apwide.com/doc/latest/cloud/v-9-16-x.md) * [2023-08-24](https://golive.apwide.com/doc/latest/cloud/v-9-15-x.md) * [2023-07-11](https://golive.apwide.com/doc/latest/cloud/v-9-14-x.md) * [2023-06-21](https://golive.apwide.com/doc/latest/cloud/v-9-11-13-x.md) * [2023-05-03](https://golive.apwide.com/doc/latest/cloud/v-9-10-x.md) * [2023-03-03](https://golive.apwide.com/doc/latest/cloud/v-9-9-x.md) * [2023-02-09](https://golive.apwide.com/doc/latest/cloud/v-9-8-x.md) * [2023-01-16](https://golive.apwide.com/doc/latest/cloud/v-9-7-x.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024 * [2024-12-10](https://golive.apwide.com/doc/latest/cloud/2024-12-10.md) * [2024-10-30](https://golive.apwide.com/doc/latest/cloud/2024-10-30.md) * [2024-09-26](https://golive.apwide.com/doc/latest/cloud/2024-09-26.md) * [2024-08-13](https://golive.apwide.com/doc/latest/cloud/2024-08-13.md) * [2024-07-18](https://golive.apwide.com/doc/latest/cloud/2024-07-18.md) * [2024-07-07](https://golive.apwide.com/doc/latest/cloud/2024-07-07.md) * [2024-06-05](https://golive.apwide.com/doc/latest/cloud/2024-06-04.md) * [2024-04-25](https://golive.apwide.com/doc/latest/cloud/2024-04-25.md) * [2024-04-09](https://golive.apwide.com/doc/latest/cloud/v-9-23-x.md) * [2024-02-29](https://golive.apwide.com/doc/latest/cloud/v-9-22-x.md) * [2024-02-07](https://golive.apwide.com/doc/latest/cloud/v-9-21-x.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-04-25 Released on **April 25, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New features ### Multiple Environments Creation The **Multiple Environments Creation** empowers you to create several Environments at once. Just select the Applications, Categories and Attributes, and start the creation process. Golive takes care of everything else, saving you time and effort when setting up multiple Environments. For detailed instructions on how to create multiple Environments, refer to the [Manage Environments](https://golive.apwide.com/doc/latest/cloud/manage-environments.md) page. ![image-20240423-141849.png](https://golive.apwide.com/__attachments/a_d0f013ac5b2c24afa2c85457b06c31664b4e1e14180173f204078f661abe9be1/image-20240423-141849.png?cb=278939b7fcfe13e2443d486fbfaa6937) ### Get Started Revamp Golive's revamped **Get Started** page improves the onboarding process for new users. It provides a clear, step-by-step guide to setting up Golive's core functionalities: tracking, scheduling, and orchestrating your environments. Access it from the **Get Started** menu entry. ![image-20240424-161817.png](https://golive.apwide.com/__attachments/a_3e894e9136d187dc8063fd2efd098bec425d9a0973d831fe2b11fe8d189d23fe/image-20240424-161817.png?cb=3714e70be8501c669ffa737a9d32fb71) *** ** * ** *** ## Improvements * We've updated the **+Add Environment** button to **+Create Environment** to better align with the actual action being performed. * We've renamed the list of **Default Views** that are automatically created upon installing Golive. * We've enhanced the **Project Onboarding Screen** to match the renaming of **Pin Views**, which was introduced in the previous Golive version. * We've improved the **Day** and **Timestamp** options in the **Scheduling Configuration** screen. *** ** * ** *** ## Bug fixes * We've addressed an issue that was causing the system timeline (without an owner) from updating properly. * We've restricted the **Dependent Environments** field selection to only allow multi-select Golive custom fields in the **Scheduling Configuration** screen. * We've fixed an issue that prevented setting the deployment date when you use drag-and-drop to move deployments in the **Last Deployment** **View**. We appreciate your feedback, and these updates are designed to enhance your workflow. Thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-06-05 Released on **June 5, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New features ### Rescheduling Screen When there is a need to reschedule a booking, change, or blackout, it is important to ensure that the request is reevaluated for potential conflicts. The best practice is to mark the fields as read-only and require users to use a "Reschedule" transition. However, this approach prevents rescheduling from the Golive timeline. That's why we implemented a brand-new **Rescheduling Screen**. Now, users can reschedule events directly from the timeline using drag-and-drop, and the rescheduling screen opens automatically to let them confirm the changes. The Jira issue is then transitioned to the "In Review" status, allowing for approval (automated or manual) to take place. ![image-20240605-091526.png](https://golive.apwide.com/__attachments/a_a8d06b9c9f0f77de6c41ee2b91699023a414176cc3cdfbcabaa1f8b210804790/image-20240605-091526.png?cb=0143909ed9f246cd488c0cc48d61a619) ### Scheduling Template Until now, you could create your Scheduling Timeline by adding one Scheduling Calendar per event type defined in your Scheduling Configuration. But what if we could simplify that process? With the new **Environment Scheduling Timeline** template, Scheduling Calendars are created automatically based on your Scheduling Configuration. This includes calendars for your Bookings, Changes, Blackouts, and any related dependencies (if configured). ![image-20240605-093350.png](https://golive.apwide.com/__attachments/a_72331d16e6b94ea9d31e140550dbf81512fc22ce14d6070c0f3251bda45b7dcb/image-20240605-093350.png?cb=8dc47d187d7c4e034d466822afd43a12) ![Scheduling Template.gif](https://golive.apwide.com/__attachments/a_8a5a24a4b64145886ed1612e0c69d8620daab1af710c649e846a65e2a8fdcc65/Scheduling%20Template.gif?cb=5012a290224ceea38da6d0687b26c680) ### Kubernetes Agent We've added the ability to integrate your Kubernetes cluster with Golive. This integration helps you maintain up-to-date environment statuses, leverage historical insights, improve incident management, and track everything in real-time for optimal visibility. [Refer to the Kubernetes Integration Article](https://golive.apwide.com/doc/latest/cloud/kubernetes), install the agent, and share your thoughts with us! ![Kubernetes-Golive Integration (1).gif](https://golive.apwide.com/__attachments/a_3ce62ea0460e524d2b0a2e9e6aa62be0e7df8f6342dc88675f3a220b55cb8219/Kubernetes-Golive%20Integration%20(1).gif?cb=8ccec13e378d6636269d181d8dc32ec7) ### Sub-tasks Scheduling Support Some of you are managing your Changes in Jira Subtasks, which was not supported by our **Scheduling Configuration**. Now you have the option to select Jira Subtasks as Bookings, Changes or Blackouts in your Scheduling Configuration. Rescheduling Subtasks is possible from the timeline, however creating new Subtasks must be done from the parent Jira issue. ![Subtask Scheduling.gif](https://golive.apwide.com/__attachments/a_c5aaf8e7b193e548c56ef5ed0a78125de392cd81e105523b37d47f9490b30960/Subtask%20Scheduling.gif?cb=cb34c893a29787b93f01f0be0e387565) *** ** * ** *** ## Improvements * We've enhanced the **Environment List Views** with the capability to add more columns displaying **Deployment Attributes** , easily identifiable by a *ship* icon next to them. * The current *active* **View** , whether **Pinned** or **Favorite**, is now highlighted in bold for better clarity. This improvement makes it easier to identify the View you are currently using. * We've removed the tags next to calendar names on the Calendar section of the Timeline. This improvement enhances the overall design, making it cleaner and less cluttered. * Now, the **Add more columns** drop-down menu is automatically closed after selection, enhancing usability. * We've improved the **Matrix** and **List Views** to load all environments at once, eliminating the need to click *load more* to find the desired environment. * The **No Environment** info message now includes actionable instructions, providing clearer guidance for users when Golive can't locate environments. * The Environment Description field is now searchable in the Environment Filter (funnel icon). *** ** * ** *** ## Bug fixes * We've adjusted the **Environment List View** to prevent *resizing* and *re-dimensioning* of page elements when hovering the mouse. This fix ensures a stable and predictable user experience. * We've fixed an issue where the auto-scroll function was not working when adding a *dependency*to an Environment. Now, when you add a dependency, the system automatically scrolls to the corresponding and relevant field. * We've updated the display of links in *email deployment notifications*. Now, only the link itself appears instead of the complete URL. * We've fixed an issue where the *Environment Detail* dialog was sometimes displayed under the *Timeline Event* dialog. * We've adjusted the layout of the **Environment Details** buttons by adding space between them. Now, the buttons are no longer placed side-by-side and are easier to see and click. * We've fixed an issue that prevented users from *deleting* previously created **Views**. * We've fixed an issue where the **Save** button was not displayed after removing a *Confirmed Status* value in the **Scheduling Configuration** screen. We appreciate your feedback, thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-07-07 Released on **July 7, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) [https://www.youtube.com/watch?v=zsneWJ0SwFw\&cc_load_policy=0](https://www.youtube.com/watch?v=zsneWJ0SwFw&cc_load_policy=0) ## New features ### Scheduling Quick Setup Setting up Jira for scheduling is no longer a time-consuming task exclusive to those with Jira administration skills. Our latest update, **Scheduling Quick Setup**, allows you to create a Jira project pre-configured for scheduling with just one click. This new project includes the correct issue types, custom fields, screens, and workflows, making the process quick and straightforward. For more information, refer to our [Configure Jira for Scheduling](https://golive.apwide.com/doc/latest/cloud/configure-jira-for-scheduling.md) article. ![image-20240703-165505.png](https://golive.apwide.com/__attachments/a_40749611e474bb64cdc7357efecc8c3820701f0c832d55b8c60a2a09cfdab7be/image-20240703-165505.png?cb=f75969d8290440a25aefb12000ec7f60) ### New Single Select Attributes Our new **Single Select** attributes allows users to choose from pre-defined options, ensuring consistent data entry. This reduces the risk of errors often found with free-form text entry. ![Single Select Attribute.gif](https://golive.apwide.com/__attachments/a_6bff6462f5d9a9bf2e24a2a12daf92c0d51a626eb2bf611840e6cffc790e2076/Single%20Select%20Attribute.gif?cb=673b071ff9eb2a2a93997ff33e604fed) Previously, we offered **Markdown** for multi-line text and **Secured**for secured single-line text attributes. **Info** You can safely convert your existing attributes to **Single Select** without losing their current values. ![Attribute Selection.gif](https://golive.apwide.com/__attachments/a_33f8bbb21f9327d02b26cdb659137c30d41ddbb99dfabdfdd6dd4bdabd3f4979/Attribute%20Selection.gif?cb=24553be604dc3e765438806e070c9b99) ### Create Calendar Revamp Creating calendars from the timeline is now easier with our latest revamp. We've improved clarity between adding *existing* calendars and creating *new ones*. Additionally, calendar type tags have been replaced with icons for better understanding. ![image-20240703-172648.png](https://golive.apwide.com/__attachments/a_af76e44f46909be9582c7bf15bb6d93e4b4103843bf3a7bacc3fea1a1c88aabf/image-20240703-172648.png?cb=79dba4fa512e5678ed9df610bbfbfdd3) ### Get Started Improvements We've enhanced the **Get Started** section to better support both new and existing Golive users. Golive **Project Pages** are now disabled by default, with an added step for clear guidance on enabling and configuring these pages. Additionally, a new introductory video has been included to familiarize users with key Golive concepts such as **Views** , **Templates** , **Issue Panels** , and**Deployments**. ![Get Started Improvements.gif](https://golive.apwide.com/__attachments/a_73895cd03191395f3411adf629e8d5ce07f31a9db5f78343c5d1d6b431d634fa/Get%20Started%20Improvements.gif?cb=630dcf0a35c21e97373d55671b47a320) *** ** * ** *** ## Improvements * We've improved the consistency of text definitions on the screen when creating a new **View** from a **Template**. * We've updated the error message for *Calendar loading failures* to provide clearer information about the cause, ensuring users understand why it occurred. * **Matrix** **Views** now display the last deployment date when you hover over an **Environment**. * We've added the **Unsaved Scheduling Configuration** warning to remind users to save their scheduling configuration settings and avoid losing changes. * We've improved the **Markdown** editor to prevent layout shifts during inline editing. ## Bug fixes * We've fixed an unexpected behavior in the **Scheduling Calendar** where events with conflicts of less than a day were automatically approved. Now, overlapping events are correctly rejected as expected. * Newly edited **Environment attributes** are now displayed immediately after editing. * We've fixed a bug where clicking on a linked timeline from a shared calendar did not always open the linked timeline. * We've fixed an issue on the **Reschedule**screen where some error messages were not displayed to users when rescheduling an event. * Rescheduling an event from one swimlane to another now correctly updates the linked environment. * The **Scheduling Configuration** screen now shows an error message if the **Issue type** field is empty when saving settings. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-07-18 Released on **July 18, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Scheduling Environment Panel Now, the **Scheduling Quick Setup** automatically adds a **Scheduling** panel in your default Environment Panels, making your *Bookings* , *Changes* , and *Blackouts* visible in your **Environment Details**. To add this panel manually: 1. Create a new timeline from the [Environment Scheduling Timeline](https://golive.apwide.com/doc/latest/cloud/environment-scheduling-timeline.md) template. 2. Add the new timeline as a Scheduling panel in your [Environment Panels](https://golive.apwide.com/doc/latest/cloud/environment-panels.md). ![Scheduling Panel (1).gif](https://golive.apwide.com/__attachments/a_9dc98d3f2cf83c1c5ab444bf8a9d9a87213296a89b66b3f492e19a9748f9ba9d/Scheduling%20Panel%20(1).gif?cb=e62902aa7613f397fd0badffa0ee7a9e) ### Calendar List Revamp To enhance user interaction with **Calendars**, we've made the following improvements: ![Calendar Improvements (5).gif](https://golive.apwide.com/__attachments/a_4f49bf823f4c6367f27cefdcf9c65a7969e322964ede1f99f9d11be6d8906559/Calendar%20Improvements%20(5).gif?cb=7047ad90164d760fa3c0cd49e4bfbcd2) #### Plan Event * A **+** appears on the calendar's color tag when it's correctly configured for event creation and when the user has the permissions to plan events. * Drag-and-drop the calendar name onto the timeline for scheduling. #### Show/Hide Events * Manage event visibility by clicking the new **eye** icon next to each calendar. #### Sort Calendars * Sort your calendars by dragging and dropping them vertically. #### 3-Dot Menu * **Create Event:** Creates a new event (greyed out if permission is denied). * **View / Edit:** Opens the event for editing (read-only if permission is limited). * **Remove:** Removes the calendar from the timeline. You can add it back using the "Add Calendar" button. * **Delete:**Deletes the calendar (greyed out if permission is denied). These improvements focus on simplifying interactions and providing clear visual cues, for a more intuitive scheduling experience. ### GitHub Actions We've introduced new **GitHub Actions** designed to integrate your GitHub workflows with Golive. This new integration allows you to: * **Easily Connect Repositories:** Instantly capture ongoing deployments, build/version contents, statuses, and environment details directly from your GitHub workflows. * **Real-time Updates:** Keep testers, release managers, scrum masters, and other stakeholders informed with up-to-the-minute updates, all accessible through Jira and Golive. #### New GitHub Actions: * [golive-send-release-info action](https://github.com/marketplace/actions/golive-send-release-info) for sending version information to Jira * [golive-send-environment-info action](https://github.com/marketplace/actions/golive-send-environment-info) for sending environment information to Jira and Golive For detailed information, refer to our [GitHub Actions](https://golive.apwide.com/doc/latest/cloud/github.md) article. ![GitHub-Golive Integration.gif](https://golive.apwide.com/__attachments/a_69cad1cf06618b1cc784cf1a6afe63282737f8c4f378f9355e44039184942de6/GitHub-Golive%20Integration.gif?cb=5b17e22af0b198d8960101a818641f7f) ### Get Started Improvements Golive's **Get Started** now offers additional information for completing configuration steps. To access the instructions, simply click on the step you want to complete. Currently, this feature is available only for the **Environment Inventory** section, and it will soon be extended to other sections as well. ![Get Started Steps (3).gif](https://golive.apwide.com/__attachments/a_c1d6e01128ece1251cef501241d1ca620cfb152c9a24eee113491c6976c0fe3a/Get%20Started%20Steps%20(3).gif?cb=224cb5eb657326010d68b224ad7936b0) *** ** * ** *** ## Improvements * **Environment Page** : We've simplified the **Environment Page** for a better user experience, and added a banner to encourage using **Environment List** Views for editing Environments. * **Demo data**: We've removed timelines (Bookings, Changes, and Environment Activities) from our demo data, in order to avoid any confusion with the new scheduling features. * **Scheduling Activity Panel** : In Golive Data Center, we've removed the scheduling activity panel for Jira **Issue types** that are not specified in the **Scheduling Configuration**. ## Bug Fixes * **Scheduling Experience:** * We've fixed an issue in the Scheduling Quick Setup that was duplicating Golive Custom Fields. * We've fixed a bug where it was impossible to schedule new issue events from the timeline panels in the Environment Details. * We've resolved an issue where scheduling conflict checking failed due to empty values in dependent Environment custom fields. * We've resolved an issue where boards were not displayed in the Jira Project created by the Scheduling Quick Setup. Now, the Scheduling Quick Setup creates the Jira Projet based on the Kanban template. * We've fixed two links from the contextual help, referring to the old Get Started page. * We've resolved a caching issue where a Pinned View continued to appear in the View Browser, even after it was removed. * We've added a clear error message when the deployment can't be updated in case of an invalid select list option. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-08-13 Released on **August 13, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Golive Settings Revamp **Golive Settings** are now presented as an intuitive administration panel. The redesigned interface enhances navigation and simplifies identification of permissions that may be missing. ![Golive Settings (1).gif](https://golive.apwide.com/__attachments/a_6d44db48c4cd1c0ee4ea2ef0c9b0c0ace7fb09467476bdd43d49c286c7600b8b/Golive%20Settings%20(1).gif?cb=4294954c5a1ac39a19acf1037f419af0) Golive Settings Revamp ### New Help Center Widget The **Help Widget** located in the bottom corner has been replaced with a new one. This updated widget consolidates all contextual help in one location and now also displays your **Get Started** progress, making it easier to access the guidance you need. ![Golive Widget (1).gif](https://golive.apwide.com/__attachments/a_a02737aaf644b23e73b1da686c5b504028b9a228dc862746bd3859eeb3155158/Golive%20Widget%20(1).gif?cb=0391e86ce26d272c5933b2d9e25c4956) New Help Center Widget ### Teams Integration Upgrade Microsoft will retire the "Incoming Webhook" connector in December 2025, and starting December 31, 2024, it will *no longer be possible to create new connectors* . For detailed information, refer to the [Microsoft Retirement of Office 365 connectors within Microsoft Teams](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/) post. To address this change, we have added a new option to our Teams Automation rules in Golive: * **Teams Incoming Webhook**: this is the legacy behavior, supporting "Incoming Webhook" connectors. * **Teams Workflows**: this is the new behavior, supporting "Teams Workflow" flows. We recommend choosing the Teams Workflows option when creating new Teams Automation Rules, and migrating existing rules to Teams Workflows as well. Please note that this migration requires a different setup in your Teams configuration. Refer to our [Teams integration article](https://golive.apwide.com/doc/latest/cloud/ms-teams.md) for more information. ![MS Teams Notifications.gif](https://golive.apwide.com/__attachments/a_02e6ed6e7638e06dbae9cdf040c7171c88b766b1fef18491a802749efc1bfb3b/MS%20Teams%20Notifications.gif?cb=453556a43d2f68f9ed386bcafb84abc5) MS Teams Automation Configuration Screen ![image-20240813-144803.png](https://golive.apwide.com/__attachments/a_a93e084564ccb857e8d012d85069a3c0f7ee5736fb91e08d3f6fdab75c086cbc/image-20240813-144803.png?cb=fb6950d96355e909a9eafac4d6e921c9) Example of MS Teams notification ### Color Palette Update We've refreshed the color palette in our **Calendars** to align with the official **Atlassian** color scheme. We have made efforts to minimize any impact on your user experience; however, please note that some **Calendar**colors may have changed significantly during the transition. ![Golive Color Palette.gif](https://golive.apwide.com/__attachments/a_f16c46212000c257b2d4014d904fa1788d428977733e00ccaf3d0ebfd2dd126a/Golive%20Color%20Palette.gif?cb=fd5122d0a85c4dc3aa08dc207c82955b) *** ** * ** *** ## Improvements * **Read-only Application Screen** : Users without the Manage Applications permission can now access the Applications screen in *read-only* mode. * **Get Started Improvements**: Users can now disable non-mandatory sections within the Get Started guide, by closing them. Closed sections will be excluded from Get Started progress tracking. * **Scheduling Quick Setup**: We've updated the Scheduling Quick Setup with new colors and improved sorting options for the calendars. Additionally, the swimlanes' configuration has been refined. * **Scheduling Rules Verification**: Scheduling rules are now verified sequentially and not in parallel. This means that conflicting requests can't both be approved when created simultaneously, preventing potential scheduling conflicts. (Golive Cloud only) * **Calendar Discard Changes Prompt:**A new prompt has been added to the Calendar feature, asking users if they want to discard changes when they have unsaved modifications. This prevents accidental loss of changes. * **Markdown Editor**: We've made the Markdown editors wider in narrow Environment List columns, enhancing usability. * **Horizontal Scroll Bar Visibility**: In the Environment List Views, the horizontal scroll bar now appears above the fold instead of at the very bottom. This ensures users can always see and use the scroll bar when needed. * **Version Display:** Versionswith too many characters weren't being displayed entirely on some Golive screens. We're now using the maximum space, and the entire version is always visible on mouse over. * **Terminology Update**: For more clarity, we've renamed 'Point' to 'Dot' in the Deployment Logs and Status Changes Logs Calendars display options. ## Bug Fixes * **Scheduling Experience:** * The Scheduling Quick Setup now correctly uses the Kanban template when creating Jira projects. * We've addressed an issue where the conflict checking would fail if the Dependent Environments Custom Field had no available values. * We've fixed an issue where newly created events weren't displayed immediately in the Environment Detail modal. * The drag-and-drop function in the Calendar now correctly prevents issue creation in unauthorized timeline areas. * We've fixed an issue where dragging and dropping an event a second time on the Calendar failed to trigger any action. * The Calendar color tag wasn't displaying correctly when the calendar name spanned two lines. * **General Fixes:** * We've fixed some attributes in the Environment List Views that weren't aligned correctly in the page layout. * Unchecking a Get Started checkbox now saves properly, opening the step modal as expected. * The 'Failed to Clone' error message now displays the attribute name instead of the ID. * We've fixed a caching issue where unpinned views were reappearing as pinned. * Matrix Views now show up-to-date information in the on-hover dialog. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-09-26 Released on **September 26, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Edit Mode for Views We've continued to enhance the [View Types](https://golive.apwide.com/doc/latest/cloud/golive-views.md), offering users various controls to customize their views on the fly. The new **Edit Mode** optimizes this process by moving all editing options under a dedicated **Edit** button, similar to the approach used in Jira Dashboards. ![Edit Mode - Edit button.gif](https://golive.apwide.com/__attachments/a_c16af894e5c9415ce2bf2d8a2e26ea8777fd283612afec54b2f8a4c3919db421/Edit%20Mode%20-%20Edit%20button.gif?cb=b419d308c735c14e8d9c8bf16ad19389) This change provides a cleaner and more focused interface for browsing Environment information and timelines. Users can enjoy fewer distractions, with easy access to powerful customization features when needed. Controls related to the View have been moved to the gear menu. The **Copy** button replaced the **Save As** button, for more consistency. ![Edit Mode - Gear menu (1).gif](https://golive.apwide.com/__attachments/a_22d111c13a6f426bfa833a1db052358ba4191320b026e596dceada3d0115e981/Edit%20Mode%20-%20Gear%20menu%20(1).gif?cb=6a5d61905c61254eeabb417a06c1e405) For more information about the changes impacting the user interface, including a before-and-after comparison, refer to the [Edit Mode UX](https://golive.apwide.com/doc/latest/cloud/edit-mode-ux.md) article. ### Simplified Jira Project Setup For a better experience, we've merged the **Golive Project Settings** (in your Jira Project Settings) and the **Project Get Started** page (displayed when opening Golive in a new Jira Project). The new unified interface includes: * **Project Settings** : Control the visibility of the **Project Page** and **Environment Issue Panel** with toggles. * **Map Applications** : Easily map Golive **Applications** to your Jira project. * **Pin Views** : Pin specific views in the Jira Project **View Browser** for quick access. ![Project Settings Revamp.gif](https://golive.apwide.com/__attachments/a_db65f69b046b770be9e75d7c7b5823de7a73d5247426c9ed1721c000c0c7f1cf/Project%20Settings%20Revamp.gif?cb=68003f544427fe1f2f7c897ac0f4ab86) Configuring Golive for a Jira Project ### New Icons for View Types For a more intuitive user experience, we've updated the icons in the **View Browser** to better distinguish between different [View Types](https://golive.apwide.com/doc/latest/cloud/golive-views.md). ![image-20240925-163605.png](https://golive.apwide.com/__attachments/a_0e070bb997184850e6f2b0b4d7d787740a15b2a03372cf704142b13991b3eefc/image-20240925-163605.png?cb=a383ade806265b87bf00fff6589627db) New icons in the View Browser *** ** * ** *** ## Improvements * **Clarity \& Usability:**We've made key updates to enhance clarity and usability across Golive, featuring improved redirects to relevant pages, clearer contextual help messages, and renamed labels for better understanding. * **UX Improvements:** The user interface has been enhanced by repositioning notifications to the bottom left corner of the screen (for consistency with Jira), replacing the **SHARED** tag with a **User Group** icon, and adjusting colors for improved visibility. * **Get Started:** We've refined the **Get Started** feature by enhancing demo data, updating default attribute types, and improving the instructions and flow to better guide users through the process. * Addition of an **ID** column to the **Custom Fields Settings** page. * Display of the **Deployed Version** field on the **Create Environment**page, even if no Jira project is linked for versions. *** ** * ** *** ## Bug Fixes * **Deployments:** We've resolved an issue related to the concurrent creation of deployments that were being duplicated, as well as another issue where **Deployment Attributes** were sometimes overwritten when updating a deployment. * **Environment Details:** We've addressed several issues, including fixing the default **Quick Filter** on the Timeline panel, ensuring the **Scheduling Quick Setup** shows tiers correctly, improving layout spacing for **Environment Attributes**, and enabling automatic display of events on the Timeline panel without requiring a refresh. * **Views:** * The **View Browser Tour** no longer appears when modals are open. We've also resolved issues with the checkboxes for adding to **Pinned Views**. * **Timeline Views:** We've resolved layout issues in the swimlanes configuration and fixed the redirection so that using the **Quick Setup** now correctly leads to the newly created **Scheduling Timeline**. * **Environment Views:** We've fixed sorting functionality in the Detail Environment View and improved layout style and alignment. * **Golive Settings** : We've resolved issues with field focus when adding **Categories** or **Statuses** , as well as improved multi-application selection and the positioning of the **Action** dropdown for better usability. * We've fixed an issue where the **Environment List Gadget** was not displaying correctly in Golive DC. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-10-30 Released on **October 30, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Usage \& Availability KPIs We've added Environment Key Performance Indicators (KPIs) in Golive to provide you with better insights into your environment's reliability and utilization. * **Environment Availability KPI** See the percentage of time an environment has been operational. This metric reflects uptime, based on "available" and "unavailable" status mappings, helping you monitor stability and quickly identify downtime patterns. * **Environment Usage KPI** Track how often environments are actively in use. This KPI calculates the percentage of time each environment was engaged based on its [Scheduling Configuration](https://golive.apwide.com/doc/latest/cloud/scheduling-configuration.md), giving you an understanding of utilization efficiency. These KPIs are available in different timespans, and you can access them in the [Environment Details Views](https://golive.apwide.com/doc/latest/cloud/details-view.md) and the [Environment Details Dialog](https://golive.apwide.com/doc/latest/cloud/golive-pages.md). For more information about these new KPIs, refer to our [Environment KPIs article](https://golive.apwide.com/doc/latest/cloud/environment-kpis.md). ![image-20241030-111608.png](https://golive.apwide.com/__attachments/a_2f745440968dd5ee6162dbb5bff69db670e494335f43d41fb6c0b8bbc0fcb21a/image-20241030-111608.png?cb=b11b597c8a5dfe8f0d110297b56894e6) Availability and Usage KPIs in the Environment Details *** ** * ** *** ## Improvements * We've improved the stability and loading performance for **Matrix Views**, especially for those displaying more than 2,000 Environments. * The **Share Timelines** permission has been renamed to **Share Views**. It now applies to all your Views and not only to the Timelines. * To provide a better understanding, descriptions have been added to **Exclusive** and **Environments** custom fields, when creating them with the **Scheduling Quick Setup**. * In the **Last Deployments View** , the **+Deployment** button is now replacing the **+Environment** button, to better align with the View's purpose. * The **Delete View** warning message has been updated to provide clear information and emphasize that this action can't be undone. * We've refined demo data to include only the most relevant **Environment Attributes** and **Deployment Attributes**. * We've enhanced the View Browser and Golive gear menu, allowing **menu entries to open as links** in new tabs or windows for easier navigation. * For Golive Cloud, we've added a new setting, **Synchronize Golive deployments with Jira deployments** , to the **Golive Application** setup, so that you can enable or disable deployment synchronization with Jira. *** ** * ** *** ## Bug Fixes * The **Deployed Version** update now prevents concurrent modifications to the same Environment, resolving previous crashes. Simultaneous changes are now sequenced, allowing edits to process one after the other. * We've resolved an error in the drag-and-drop function in **Timeline Views**, where events sometimes displayed incorrectly and stuck to the timeline. * We've fixed the issue with the **Name** in **Matrix Views**, where clicking on a row or column label didn't work properly. Now it opens in a new tab as expected. * We've resolved the issue where **Event Fields** were not automatically filled the first time users planned with the drag-and-drop function. * **Get Started** page has been fixed to ensure that all links function properly. * We've fixed the issue where a **Calendar** added to a **Timeline**wasn't consistently saved. * We've fixed an issue where the **View Browser** spotlight occasionally covered the survey, blocking new users from filling it out on their first app launch. * We've fixed an issue where the **Edit** button was missing in certain Views. Now, it's displayed in all Views, as expected. * We've resolved a bug preventing the creation of applications and environments through the **Java API** . (Golive DC only) * We've fixed an error preventing the loading of **Deployment Attributes**. (Golive DC only) * We've resolved an error displayed when adding more than one environment in the **rescheduling screen**. (Golive DC only) We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2024-12-10 Released on **December 10, 2024** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Advanced Settings for Disabling KPIs You can now control the visibility of the **Usage** and **Availability KPIs** displayed on the [Environment Details](https://golive.apwide.com/doc/latest/cloud/golive-pages.md) through Golive's **Advanced Settings**, allowing you to hide or display them as needed. ![image-20241210-161701.png](https://golive.apwide.com/__attachments/a_200047f8156e742d4b6b28bf46dde3d216c9561f51252e49d453453bb0dfab0c/image-20241210-161701.png?cb=9b980ca1394a415a73afb624483f9459) Usage and Availability KPIs display options *** ** * ** *** ## Improvements * To enhance your experience, the **Applications** field is now automatically saved in both the **Golive Project Settings** and **Project Get Started** sections. * We've added demo Environments' status changes to provide a better representation of the **Last Status Changes View** and the **Availability KPI**. * We've reduced the height of the **Deployment Description** field to ensure other fields, like **Issues**, are visible even on smaller screens. * We've improved **Deployment** search performance for faster and more efficient results. *** ** * ** *** ## Bug Fixes * We've resolved an issue where newly pinned views in Golive's **Get Started** were not displaying as expected. * We've improved the layout of **Markdown Attributes**, ensuring proper alignment and a better visual display. * The option to access **Environment Details** while in Edit mode has been removed for the List Views. This change guarantees that any modifications made are not inadvertently lost. * We've adjusted the display of **Single Select**attributes, ensuring the drop-down selection is wide enough for better readability. * We've fixed an issue causing **Markdown Attribute** links to open improperly. * Now, **Environment Attributes** update without temporarily reverting to the previous value, in both the **Environment Details** and **Environment List** views. * We've resolved an issue that blocked the deletion of **Applications** and failed to provide instructional messages or additional context. * We've fixed an issue where **Categories** were not displayed correctly when creating multiple **Environments** at once. **Categories** now appear as expected. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025 * [2025-11-26](https://golive.apwide.com/doc/latest/cloud/2025-11-26.md) * [2025-05-20](https://golive.apwide.com/doc/latest/cloud/2025-05-20.md) * [2025-04-29](https://golive.apwide.com/doc/latest/cloud/2025-04-29.md) * [2025-04-08](https://golive.apwide.com/doc/latest/cloud/2025-04-08.md) * [2025-03-05](https://golive.apwide.com/doc/latest/cloud/2025-03-05.md) * [2025-01-24](https://golive.apwide.com/doc/latest/cloud/2025-01-24.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025-01-24 Released on **January 24, 2025** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Display issue links on Issue Calendar events The **Issue Calendar** now displays linked issues directly within **Event Details** , making it easier to track related tasks. A new **Issue Links** field can be added to your event layout. When opening the event dialog, the list of linked issues is shown, including the issue type icon, issue key, and issue summaries. If the field is added as **Event Title** or **Event Tag**, a link icon will also appear on the event layout, indicating one or more related issues. This update allows you to view and manage related issues without leaving the event screen. ![Golive Issue Links.png](https://golive.apwide.com/__attachments/a_2338b7d9ec505cd2af02aeb77741edc122b11385b1f06115c38e4d3e205add6b/Golive%20Issue%20Links.png?cb=334f8dc1a9f4fcdc105d1b3c093259d5) Issue links displayed on Calendar events ### New Template: Last Deployed Versions The [Last Deployed Versions](https://golive.apwide.com/doc/latest/cloud/last-deployed-versions.md) view template offers a clear timeline of all recent Jira versions deployed to your Environments. It helps you easily track when and where linked Jira versions were deployed, keeping you informed about the status of your deployments. **Setup**: * From your View Browser, click on **+ Create View**. * In the Deployment Management templates, choose **Last Deployed Versions**. * **Project Selection**: Select one or more projects to track. This template makes it simple to stay on top of your deployment history and ensures that version information is always accessible. Refer to the [Last Deployed Versions](https://golive.apwide.com/doc/latest/cloud/last-deployed-versions.md) article for more information. ![Apwide Golive Media - Last Deployed Versions.png](https://golive.apwide.com/__attachments/a_2935f1f3b741b95ecfe4782cb36352aad0ac5d19bbb20ba3ded40ec8fede90b4/Apwide%20Golive%20Media%20-%20Last%20Deployed%20Versions.png?cb=b087e4f2c8a1ccee594128c9cbce5ef7) Example of the Last Deployed Versions template *** ** * ** *** ## Improvements * **Scheduling Quick Setup:** * To prevent configuration issues, the **Start Time** and **End Time** fields will now be automatically defined as **required**. * A dedicated **Permission Scheme** will be created, so that any logged-in user will be able to browse and create/edit/transition issues in the new project. * **Last Deployed Issues:**The dialog in will now be aligned directly under the cloud icon. This alignment helps you easily identify the effective date of the deployment. * **Scheduling Calendar:** Events will now be mapped to version swimlanes using the **fixVersion** field, so that events appear under the correct version when their fixVersion field is populated. * **Matrix Views:** We've improved **Matrix Views** performance by limiting excessive data loading and requiring filters for large Environment sets. Additionally, a loader or progress indicator and a database Environment count have been added to enhance responsiveness and reduce load times. *** ** * ** *** ## Bug Fixes * The **with tiers** checkbox now appears immediately if at least one **Environment Tier** exists, resolving caching and display issues. * We've resolved an issue where the **Project** field wasn't visible when creating an [Issues Timeline template](https://golive.apwide.com/doc/latest/cloud/issues-timeline.md). * We've fixed our **Kubernetes Agent** helm chart, so that the status would not be switched to NONE after every update. * We've resolved an issue where deployments were displayed on top of each other after refreshing a timeline. * We've fixed an issue where using **Expand/Collapse All** incorrectly flagged the timeline as unsaved and triggered a confirmation message. * We've resolved an issue where the **Jenkins Shared Library** was unable to correctly capture the changeset. * We've fixed an issue where the zoom level in **Last Deployments** views automatically changed after scheduling a deployment. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025-03-05 Released on **March 5, 2025** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## GitLab Integration via Components ![GitLab-Golive Integration.gif](https://golive.apwide.com/__attachments/a_c03c506102a2dcc32d99d1613cbd69a23ade3439d4cf9f261400506153147746/GitLab-Golive%20Integration.gif?cb=a1c2e01fedfeb30a0046b300c96ab60a) We're introducing a new integration for GitLab, allowing teams to connect their GitLab pipelines with Golive using **GitLab Components**. With this integration, changes in GitLab--- such as builds or deployments---are automatically reflected in Jira and Golive: **Jira versions** * Automatically creates missing Jira versions in relevant Jira project(s). * Updates version scope based on GitLab deployments. **Jira work items** * Retrieves Jira work items (aka Jira issues) from your GitLab commit history. * Updates **FixVersion** fields with relevant Jira versions. * Displays deployments in: * The **Golive Issue Panel**. * The **Jira Deployments Panel** (Jira Cloud only). **Golive dashboards** * Updates Environment statuses during deployments. * Updates Environment deployed versions based on the relevant deployment scope (Jira work items). For setup instructions, refer to the [GitLab Integration article](https://golive.apwide.com/doc/latest/cloud/gitlab.md). *** ** * ** *** ## Bug Fixes * We've fixed an issue where the **Usage KPI** incorrectly displayed 0% when first loaded. It now shows the correct percentage. * Now, users with the **Browse Environment** permission on at least one Environment **Permission Scheme** can access the **Environments List** section. * We've fixed an issue where an extra zero was incorrectly added to the**Deployment Time** when scheduling deployments. * Now, the **Last Deployed Issues View** loads correctly when the **with tiers**checkbox is enabled, preventing the "Swimlanes loading failed" error. * We've fixed an issue where **Environment Attributes** occasionally failed to display in the **Environment List View**. * App icons have been updated to improve support for both dark and light modes. * We've fixed an issue where the **Scheduling Quick Setup failed** to work properly on Jira Free instances. * **Environment Search**now works as expected when no values are provided in the project search criteria or when multiple project search criteria are applied, even if at least one yields no data. * We've fixed an issue where **Event Search** returned no results when certain Environment **Quick Filters** were applied. We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025-04-08 Released on **April 8, 2025** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Dark Mode is Here Working late? Cutting down on blue light? Just love a sleek look? We heard you. Golive now supports**Dark Mode.** Switch your Jira theme, and Golive will match automatically. Give it a try and let your eyes rest for a bit. ![output-20250408-090659.gif](https://golive.apwide.com/__attachments/a_40a565b64afa904c86a893340208c0a99652660fbf3f13f5502d52edaa1acb7f/output-20250408-090659.gif?cb=46dd8b01bd171a57c63f149648c64df0) Golive Dark Mode ### Inline Environment Name Editing Renaming Environments got easier. You can now update Environment names directly from the **Environment List** view. Just filter, click, and edit. Done. It's that simple. ![env-name-edition.png](https://golive.apwide.com/__attachments/a_fea1187c5643fce69088a03452e9509d88f4c91436321f893b0615296bef69e3/env-name-edition.png?cb=03e7c3457d4253bc74ae52d1582ccfab) Environment Name Editing ### Environment \& Deployment Attributes Creation No more jumping between screens. Now you can create **Attributes** directly from the **Environment Details** page and **Application Details** dialog. No detours. No distractions. Just focus on what you need to do.​ ![output-20250408-092101.gif](https://golive.apwide.com/__attachments/a_aadc975436c7bd852c212b2b893564dc7d7ac0d699f930292f8ba6672b903039/output-20250408-092101.gif?cb=d69d300a8df7907388133ca97e521a63) Environment Attributes Creation *** ** * ** *** ## Bug Fixes * We've improved **Timeline Drag \& Drop** behavior when creating events from the **Calendar** menu. Drag actions are now correctly blocked when event creation is not allowed. * Changes to **Timeline Display Settings**, such as toggling vertical event lines, now apply consistently when switching forward and backward. * Scheduling **Bookings** , **Changes** , or **Blackouts** now correctly updates custom fields, even if some dependent Environments are unavailable. * We've fixed an issue where cloned**Environment** **Tiers** were incorrectly linked as dependencies of both the original and the clone. * After completing the **Scheduling Quick Setup** , clicking **Start Scheduling** now correctly opens the **Scheduling Timeline**. *** ** * ** *** We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025-04-29 Released on **April 29, 2025** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### New Environment Creation Flow We've revamped the **Environment Creation** process and introduced updated terminology to better reflect how Applications and Environments are structured. **New Terminology:** * **Application** refers to an Application without tiers. * **Application Landscape** is an Application that includes tiers. * **Environment** is an Environment without tiers. * **Environment Landscape** is an Environment that includes tiers. * **Tier** remains unchanged. **Updated Environment Creation Process:** When creating a new Environment, you now start by selecting the **Application** or **Application Landscape** , followed by the **Category**. If you're creating an **Environment Landscape**, a banner will display the tiers that will be created automatically. You also have the option to update the name of the Environment (or landscape) during creation, and any tier names will be updated accordingly. You can now also create an **Application Landscape** directly, making it easier to build tiered application structures from the start. ![Environment Creation Flow.png](https://golive.apwide.com/__attachments/a_f1a2f2be8df199fa2d69864f029b61a9d60fa74fe6363503888c97ddabd73c66/Environment%20Creation%20Flow.png?cb=9d5c9af2d30887df07119af9cb6ccdaa) New Environment Creation Flow ### Guess Dependencies and Tiers We've added **Guess Dependencies** and **Guess Tiers** buttons. Now, instead of manually defining dependencies and tiers for your Environments, you can populate them automatically with one click. When you use this new feature, Golive pulls the dependencies and tiers from the **Application** configuration and applies them to your Environment. This saves you time and reduces the chance of missing critical links. ![Guess Dependencies.png](https://golive.apwide.com/__attachments/a_ad206cc204bfefced5c08b95b5d8d5c6af213f07998ff9d28a8150feb9f6f00f/Guess%20Dependencies.png?cb=c44123948c1d2367cf688e8382af82df) Guess Dependencies *** ** * ** *** ## Improvements * **Removed Application Titles in Tiers and Dependencies** : The **Application** titles have been removed from the **Tiers** and **Dependencies**sections. Now, only the names of your tiers and dependencies are displayed. This avoids duplicate information and keeps the interface more focused and clean. * **Improved Notification When Deleting Applications:** When attempting to delete an **Application** linked to one or more Environments, a notification message now appears listing the linked Environments that prevent the deletion. * **Updated Default Environment Attributes:** We've updated the **Environment Attributes** created automatically when installing Golive: *Database* , *Hosting* , *Location* , *OS* , *Group* , *CPU* , *Storage* , *Memory*. *** ** * ** *** ## Bug Fixes * We've fixed an issue where **Timelines** became unresponsive after opening an Environment. * We've resolved an issue where Jira Administrators didn't automatically receive the **Golive Administrator** permission. This permission is now granted automatically. * The layout of the **Open Golive** button on the **Project Settings** page has been improved with better spacing, ensuring visual consistency. * We've fixed an issue when creating Environments from an **Detail**view displayed an error message. * Previously, **Calendar** results were limited to **100 events**, with no feedback when the limit was reached. This limit was removed, so that all results are now displayed. To avoid performance issues, users should apply additional filtering to their Environments if experiencing problems. *** ** * ** *** We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025-05-20 Released on **May 20, 2025** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## Improvements * The [Scheduling Activity Tab](https://golive.apwide.com/doc/latest/cloud/scheduling-configuration.md) is now hidden from Jira work items that are not part of the **Scheduling Configuration**. * We've removed the breadcrumb navigation from the **Golive Project page** when the new Jira UI is enabled, to avoid duplication. * After cloning a calendar from a Timeline, the Timeline **Edit Mode** is now automatically enabled. This prevents the cloned calendar from disappearing from The Timeline after the user refreshes the page. * Hovering over a [Scheduled Events Calendar](https://golive.apwide.com/doc/latest/cloud/scheduled-events.md) event now displays its description. ![image-20250521-075040.png](https://golive.apwide.com/__attachments/a_1f8b4057d2af427fda30c0883df688ad0735dc8ff274fcad74c17e8042073cbf/image-20250521-075040.png?cb=27119ec645d4fbbcd69420fb970bad7d) Description in the event title *** ** * ** *** ## Bug Fixes * We've optimized **calendar event loading** to properly handle nested swimlanes. Users will now see the visible events up to the maximum allowed, and can then click to load them all when needed. If loading all events impact browser performance, consider applying more filters or zooming in to reduce the visible timeframe. * We've fixed an issue for **Versions Calendars**, where refreshing the Timeline didn't update the version's status. * Scrollbars that appeared unnecessarily in the **Deployments** dialog have been removed for a cleaner interface. * The **Tiers** column on **Environment List** views now shows complete tier names, making them easier to read without hovering. * Events now display on the Timeline as soon as they are created, without needing to refresh. *** ** * ** *** We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2025-11-26 Released on **November 26, 2025** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Full-Screen Dependency Map You can now open the **Environment Dependency Map** in full-screen mode. This view makes complex relationships easier to read and navigate. ![Map Expand.png](https://golive.apwide.com/__attachments/a_bc2881d0aa6422ee23fc7bdda9249153aef12de3ba84cc4c1993bf812d0ac8ba/Map%20Expand.png?cb=cf276716f4a67e0962ae431e34160a92) Full screen button in the Dependency Map ### Status Filter in the Status Change Calendar The [Status Change Logs Calendar](https://golive.apwide.com/doc/latest/cloud/status-changes.md) now includes a **Statuses** filter. It helps you focus on relevant updates, improves performance when many events are displayed, and lets you export only the filtered status changes. ![Status Change Logs Filters.png](https://golive.apwide.com/__attachments/a_061afe73ced26bd662a4243d5f738949e272a1a235217c563985698ee60f287c/Status%20Change%20Logs%20Filters.png?cb=6c6568018f3c99e75383045594327252) Status Filter in the Status Logs *** ** * ** *** ## Improvements * On [Timeline Views](https://golive.apwide.com/doc/latest/cloud/timeline-views.md), the **Environment Swimlane** tooltip now shows the deployed version, current status, and full Environment name (if truncated). * In [MS Teams Golive Automations](https://golive.apwide.com/doc/latest/cloud/ms-teams.md), the deprecation banner is now hidden when **Teams Workflows** is selected. *** ** * ** *** ## Bug Fixes * Fixed an issue where the **Environment export** button did not work in Last Deployments and Last Status Changes calendars. * Resolved an issue where disabling **Check conflicts on dependencies** in the **Scheduling Configuration** wasn't working as expected. * Fixed an exclusive field validation error that appeared when saving **Scheduling Configuration**. * Improved readability of webhook payload previews in **Automations** (including Jira light mode). * Pebble loop variables (e.g., `loop.first`, `loop.last`) now work properly in **Golive Automations**. * Resolved an issue where deployments linked to an issue were not fully loaded in the **Issue Deployments** view. * Fixed a rendering issue that prevented the Agile rapid board from displaying when the matrix panel was enabled. *** ** * ** *** We appreciate your feedback and thank you for your continued support. --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2026-01-13 Released on **January 13, 2026** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) **Action Required** This release upgrades Golive to a new Forge-based version. This is a **technical upgrade only** and does not introduce any functional changes. There is no impact on how users work with Golive. To complete the upgrade, a Jira Administrator must follow these steps: 1. Go to **Settings → Marketplace apps** 2. Click **Take me here** 3. Locate **Golive** and click **View app details** 4. Click the **Update** button If the upgrade is not completed by **February 8, 2026**, the Golive app will stop working until it is updated. **Golive URLs have changed** This technical upgrade introduces a new set of URLs for Golive pages. As a result, any existing browser bookmarks or shortcuts pointing to Golive pages will no longer work and should be updated. ## New Features ### New Forge Custom Fields Golive custom fields are moving to the Forge platform. This brings richer Environment details into Jira issues, including status colors and deployed version tooltips. These new fields also lay the foundation for future features, such as Environment suggestions. ![image-20251231-121923.png](https://golive.apwide.com/__attachments/a_4e7a82fb733a3dd048535807690d5a1e089f8395d5b12479ff552d605ca221ba/image-20251231-121923.png?cb=cab7175d0cf6128d8aa440f52c3ecae8) New Golive custom field To benefit from these improvements, all legacy Golive custom fields must be migrated: 1. In **Golive Settings** , open the the **Custom Fields** section. 2. Click **Migrate** next to a legacy field. 3. Follow the wizard to create the corresponding Forge new field. 4. If applicable, update custom automations and integrations to use the new field. 5. Delete the legacy field. A snapshot of its configuration is kept for reference. **Action Required** If the migration is not completed by **February 15, 2026**, it will run automatically. This may impact your scheduling configuration and custom automations. If you need help, [schedule a call with our support team](https://meetings.hubspot.com/marcin-wojtkowski). **Environment IDs shown in Jira Boards** With the new Forge-based Golive custom fields, Jira boards may display environment IDs instead of names (columns, swimlanes, cards, filters). This is a **current Jira limitation with Forge custom fields**. Boards can only display the stored value (the ID) and cannot resolve environment names. * This is expected behavior today * It only affects board display * Issue view always shows the correct environment names **What we are doing:** We are working on a **Golive Jira Automation action** that will resolve environment metadata (name, application, group) and let you populate board-friendly text fields automatically. This improvement will be available soon. ![image-20260106-132601.png](https://golive.apwide.com/__attachments/a_75da87ce893d300cbdac1718f7607388ef24e4cb2f174d146399e97cc80cc1fc/image-20260106-132601.png?cb=9ee686179ce7779bab24b8dfe162c059) Golive Custom Fields Settings ### Instance Data Reset You can now reset all Golive data in your Jira instance. This action is **irreversible** and cannot be rolled back. All Golive product data is permanently deleted, except for: * REST API tokens. * Golive custom fields and their values. * Jira Project Settings. After selecting **Instance Data Reset** in **Golive Settings** , you can choose whether to include sample data after the reset. For step-by-step instructions, refer to the [Instance Data Reset](https://golive.apwide.com/doc/latest/cloud/instance-data-reset.md) documentation. ![image-20251231-123632.png](https://golive.apwide.com/__attachments/a_c0f5c7280c4fc7e3a596e13195fa703864d7192f3ce22f351b8031ffaf377cbf/image-20251231-123632.png?cb=9e17ce4dbc46daf9489751f004d9130c) The reset reinitializes all permissions and all Jira administrators and Jira users are assigned the **Golive Administrator** permission. Review the [Permissions Settings](https://golive.apwide.com/doc/latest/cloud/security-permissions.md) documentation after completing the reset. *** ** * ** *** ## Improvements * We improved color contrast in the **Golive Automation** editor to ensure readability in both light and dark Jira themes. ## Bug Fixes * Fixed an issue where a booking could be incorrectly auto-approved when it started after and ended before an already approved booking. * Fixed broken in-app documentation links that redirected to incorrect documentation articles. *** ** * ** *** We appreciate your feedback and thank you for your continued support. [Give feedback](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/149) · [Get support](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1) · [Request a feature](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/6) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2026-03-24 Released on **March 24, 2026** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Golive Custom Field Improvements We have improved the Golive custom fields to provide clearer and more accessible deployment information. * Tooltip displaying key environment details (Environment name, Last deployed version, Last deployment date and time, Status). * Button to open the Environment details in a new tab. Due to Jira limitations, the Environment cannot currently be opened in a dialog on the same page. ![image-20260324-104626.png](https://golive.apwide.com/__attachments/a_6965510f2bfd98594810f6e7139c390e8dceffbb99a83f151419fca243ac8ff6/image-20260324-104626.png?cb=5308c55de883cb62c8bc6a7b0257cc08) Example of Golive Custom Field ### Golive Jira Automation Actions We have introduced three new Jira Automation actions to help you retrieve Golive environments and use them in your automation rules. * **Find Golive Environments** Retrieve environments based on search criteria such as application, category, status, or attribute values. * **Get Golive Environments by ID** Retrieve one or more environments using their IDs. * **Get Golive Environments by Name** Retrieve one or more environments using their names. [Learn more about Golive Jira Automation Actions](https://golive.apwide.com/doc/latest/cloud/golive-jira-automation-actions.md) ![image-20260324-105224.png](https://golive.apwide.com/__attachments/a_b8d4d8112e77ab662ac5f1351a546e847d47590cad43b28a87f62594a082abcb/image-20260324-105224.png?cb=bc223ca3c6d6676c222fabc63ec5c0f4) Example of Golive Jira Automation ### List View Selective Export You can now export only the columns currently visible in your [List Views](https://golive.apwide.com/doc/latest/cloud/list-views.md). * Export environments using the **listed fields only**. * Choose between **XLSX** and **CSV** formats. ![image-20260324-110139.png](https://golive.apwide.com/__attachments/a_7331adc6907972354f3f22c814762e67b6525ad716205d3ae032746a948485d6/image-20260324-110139.png?cb=c7af52a583653291ed51760f133c0fbb) Listed Fields Export ### Environment Search: Tier and Dependency Criteria We have added new search criteria to help you filter environments based on their tiers and dependencies. * `hasTier=` Find environments that include a specific environment tier. * `tierOf=` Find environments that are tiers of a specific environment. * `dependsOn=` Find environments that depend on a specific environment. * `dependencyOf=` Find environments that are dependencies of a specific environment. [Learn more about searching Environments](https://golive.apwide.com/doc/latest/cloud/search-environments.md) ![85425d29-a3b8-4e42-b2d9-a59b71ab6139.png](https://golive.apwide.com/__attachments/a_9e47aae369d30b2cdf322564afc6a782390ae8677ff2ce40d001ffd995c786bb/85425d29-a3b8-4e42-b2d9-a59b71ab6139.png?cb=ac16d246e5b17121d1b9bd5e9bf7eda6) Finding Environments that have a specific Environment as Tier *** ** * ** *** ## Improvements * Renamed the **Create Environment** page to **Create Environment Tier** when creating a tier environment to improve clarity. *** ** * ** *** ## Bug Fixes * Fixed issues where clicking tiers or dependencies from the Environment details or breadcrumb did not open them in the current dialog. * Fixed an issue where Golive Automation linked and unlinked issue triggers did not work correctly with the new Golive custom fields. * Fixed an issue where the usage KPI was incorrectly calculated with the new Golive custom fields. *** ** * ** *** We appreciate your feedback and thank you for your continued support. [Give feedback](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/149) · [Get support](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1) · [Request a feature](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/6) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2026-05-22 Released on **May 22, 2026** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Version Comparison Template You can now compare deployed versions across your environments for the same application in a dedicated Matrix View. The template uses color-coded labels to instantly highlight version differences, making it easier to spot inconsistencies and understand deployment progress across your landscape. The template is powered by the new **Deployed Version Comparison** label, which is available in any Matrix View. It works with any row and column configuration, allowing you to compare versions by environment, customer, region, application, or any other dimension relevant to your organization. [Learn more about the Version Comparison Template](https://golive.apwide.com/doc/latest/cloud/version-comparison.md) ![image-20260603-153814.png](https://golive.apwide.com/__attachments/a_5fbb7a0306018932af1435835839ec9d879e84a8259a60bafad5a553f61b6632/image-20260603-153814.png?cb=34437eda474842d30b9561405b95b670) Example of Version Comparison template *** ** * ** *** ## Improvements * We've disabled the View Browser and event scheduling actions in Timeline Edit Mode. This UX improvement helps users save their changes before returning to the timeline for event scheduling. * Shared calendar pages now hide calendars when the user does not have view permission. Users without permission can no longer open the calendar dialog. * We've improved Matrix Views to display `` when an environment exists but the field selected as the matrix label has no value. This makes it easier to distinguish environments with missing data from environments that do not exist. *** ** * ** *** ## Bug Fixes * Fixed an issue where the "New deployment" button was not working in the Last Deployment view. * Fixed an issue where deployment items were not always fully displayed when the related environment was not in cache. * Fixed a conflict between calendar reordering in Edit Mode and dragging new events in View Mode. * Fixed an issue where dragging new events from a standard calendar did not always respect the calendar's environment filter. *** ** * ** *** We appreciate your feedback and thank you for your continued support. [Give feedback](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/149) · [Get support](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1) · [Request a feature](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/6) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2026-06-23 Released on **June 23, 2026** \| [Golive Marketplace Listing](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub?hosting=cloud&tab=overview) \| [Version History](https://marketplace.atlassian.com/apps/1212239/golive-environment-management-hub/version-history) ## New Features ### Application Custom Fields The new **Application Custom Field** allows users to select one or more Golive Applications directly from a Jira work item. You can configure the field to display all Applications or only those associated with the current Jira space. [Learn more about Application Custom Fields](https://golive.apwide.com/doc/latest/cloud/application-custom-fields.md) ![image-20260624-173144.png](https://golive.apwide.com/__attachments/a_9ed89445e73397b35e494f3349500eaa5c573341a0fbe8c02b0bec21da6e11ac/image-20260624-173144.png?cb=08daa3d3da4b06f24af21a94160147e5) Application custom field configuration ![image-20260624-172954.png](https://golive.apwide.com/__attachments/a_6964c4317913f1bbcd185b9bccbdb0e4f8468405d8235ae7df27a2f0d626d704/image-20260624-172954.png?cb=d5906721bb7afbbd0dd78d354dc8662d) Application and Category custom fields ### Category Custom Fields The new **Category Custom Field** allows users to select one or more Golive Categories directly from a Jira work item. The selected Categories can then be used in Jira Automation rules. For example, a request could automatically book all environments belonging to a selected category. [Learn more about Category Custom Fields](https://golive.apwide.com/doc/latest/cloud/category-custom-fields.md) ![image-20260624-173321.png](https://golive.apwide.com/__attachments/a_5d9a9a61bfa1f280cbeeda085881eef92447a7e67237bc21b6202188eed9d850/image-20260624-173321.png?cb=58ec17552cc63fc099c51169f19c9d2c) Category custom field configuration *** ** * ** *** ## Improvements * **Enhanced Environment filtering** - Environment filtering criteria can now contain multiple `categoryId` or `applicationId` values, separated by commas. This improvement makes it easier to create Jira Automation rules using the new Application and Category Custom Fields. For example, you can [Populate Environments from Application + Category fields](https://golive.apwide.com/doc/latest/cloud/populate-environments-from-application-category-fields.md). * **Connect cleanup** - We have fully removed the remaining legacy Connect code from the Custom Fields screen. It now displays only the new Forge Custom Fields. * **Jira field schemes compatibility** - Compatibility with the recent [++Jira field configuration improvements++](https://developer.atlassian.com/changelog/#CHANGE-3019). *** ** * ** *** ## Bug Fixes * Fixed an issue where Jira versions were not automatically created in synchronized Jira spaces when the version already existed in the primary Jira space. * Fixed an issue where a dot appeared over cloud icons when the Event Display option was set to Dot, in [Deployment Logs Calendars](https://golive.apwide.com/doc/latest/cloud/deployments.md). *** ** * ** *** We appreciate your feedback and thank you for your continued support. [Give feedback](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/149) · [Get support](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1) · [Request a feature](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/6) --- version: "latest" variant: "Golive Cloud" language: "en" --- # 2026-07-30 Version 3.22 released on **July 30, 2026** Version 4.0 released on **August 4, 2026** **Action Required** The version 4.0 needs new Rovo permissions and requires **manual approval** . To complete the upgrade, a Jira Administrator must go to **Manage apps** and click **Update**. ## New Features ### KPIs in List and Matrix Views Environment KPIs can now be displayed directly in your Golive views: * As columns in [List Views](https://golive.apwide.com/doc/latest/cloud/list-views.md) * As labels in [Matrix Views](https://golive.apwide.com/doc/latest/cloud/matrix-views.md) This makes it easier to compare environments and identify availability or usage patterns without opening each environment individually. KPI results are cached for one hour. When a KPI is displayed, Golive automatically recalculates it if the previous calculation is more than one hour old. KPIs may also be recalculated when Golive performs a conflict check for environment scheduling. [Learn more about Environment KPI](https://golive.apwide.com/doc/latest/cloud/environment-kpis.md) ![image-20260730-085831.png](https://golive.apwide.com/__attachments/a_2ec457b7df36645bee5b1eabc4688fb21b7ba88b00e64105a55134b0bf0de563/image-20260730-085831.png?cb=dc42aab4f1ae1517b5dd359dcc9b183c) Environment KPIs in the List View ![image-20260730-090045.png](https://golive.apwide.com/__attachments/a_16ef4e8dd3e84c9ccf3fc651c87e68308455b86d26b6ab865de0f9529fd5ac01/image-20260730-090045.png?cb=836e5bb88c3d9cec08be1e8b1bc07c35) Environment KPIs in the Matrix View ### Disable Golive Automations Jira administrators can now enable or disable Golive Automations for the entire Jira site from **Golive Settings → Security Settings**. When Golive Automations are disabled, users can no longer access or execute automation rules. This gives organizations greater control over automations that may interact with external services through web requests, custom URLs, headers or payloads. Security Settings are restricted to Jira administrators. The **Golive Administrator** permission alone does not provide access to these settings. [Learn more about Security Settings](https://golive.apwide.com/doc/latest/cloud/security-settings.md) ![image-20260729-172019.png](https://golive.apwide.com/__attachments/a_2f001653c393830b2c8a91042d8a0b8a255bc5f5c3cdf62f3288ba120de91b4d/image-20260729-172019.png?cb=15e1e836012c63150303e4f647d71ad4) New option in the Security Settings ### Rovo Agent \& Rovo Skills A new **Golive Environment Manager** Rovo Agent is now available to help users retrieve useful environment information using natural language. For example, users can ask: * "What version is currently deployed on eCommerce Staging?" * "Which production environments are unavailable?" * "Show me all staging environments for the Payment application." * "What does eCommerce Production depend on?" * "Show me the tiers of Payment Production." * "Where is Customer Portal Staging hosted?" The agent can search by name, application, category, status, attributes, tiers, and dependencies, and combine multiple searches when needed. [Learn more about the Golive Rovo Agent](https://golive.apwide.com/doc/latest/cloud/rovo-agent.md) Three Golive Rovo Skills are also available for use in custom Rovo Agents created with Atlassian Studio: * **Find Golive Environments** * **Get Golive Environments by id** * **Get Golive Environments by name** These skills let custom agents retrieve current environment information from Golive and combine it with other Rovo capabilities and data sources. [Learn more about the Golive Rovo Skills](https://golive.apwide.com/doc/latest/cloud/rovo-skills.md) *** ** * ** *** ## Improvements ### Auto-create missing versions across Jira spaces We have redesigned the **Jira Versions** tab in the application configuration. When a primary Jira space is configured, Golive now always creates missing deployed versions in that space, provided the user has permission to create versions. This also applies when the deployment does not reference any work item from the primary space. You can also choose how Golive updates the **Fix Versions** field of Jira work items included in a deployment: * **Do not update Fix Versions** * **Update Fix Versions in the primary Jira space only** * **Update Fix Versions in all deployed work item spaces** With the third option, Golive also creates a missing version in another Jira space when: * The deployment references at least one work item from that space * The user has permission to create versions in that space Jira's dedicated **Manage Versions** permission can be granted to users without making them space administrators. [Learn more about Managing Applications](https://golive.apwide.com/doc/latest/cloud/applications.md) The **Synchronized Jira Spaces** setting is now deprecated. Use Jira Automation when versions need to be synchronized with additional spaces independently of the work items included in a deployment. [Learn how to synchronize Jira versions with Automation](https://community.atlassian.com/forums/Jira-articles/How-to-Sync-Jira-Versions-Across-Projects-Using-Jira-Automation/ba-p/3045656) Existing configurations will continue to work until **October 30, 2026**. Once all values are removed from the deprecated field, it will disappear and cannot be configured again. ![image-20260729-172300.png](https://golive.apwide.com/__attachments/a_80246542885fda882df7fe35c109d361656bfb583ba4acef90bbe63de1496d17/image-20260729-172300.png?cb=50fc734c35609bc986e4a015818b6116) Improved Jira Versions tab in the Application screen ### Filter suggestions order Filter suggestions are now ordered based on the options customers use most frequently. Common filters such as **Application** , **Category** and **Status**now appear before less frequently used options, such as tiers, dependencies, or permission schemes. ### Jira working hours retrieved automatically The **Jira working hours per day** option has been removed from Golive Advanced Settings, as Golive can now retrieve this setting directly from Jira. If the values previously configured in Golive and Jira were different, you may notice changes in duration fields such as estimates and time spent. *** ** * ** *** ## Bug Fixes * Fixed an issue that prevented users from selecting multiple environments when rescheduling an event from a [Scheduling Calendar](https://golive.apwide.com/doc/latest/cloud/scheduling-calendar.md), even when the environment custom field was configured to allow multiple selections. *** ** * ** *** We appreciate your feedback and thank you for your continued support. [Give feedback](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/149) · [Get support](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1) · [Request a feature](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/6) --- version: "latest" variant: "Golive Cloud" language: "en" --- # About Golive Golive is a Test Environment Management (TEM) solution that helps teams manage the full lifecycle of their **Environments** directly from Jira. It organizes Environment data and automates common tasks, giving teams visibility and control over the **past** , **present** , and **future** states of their Environments. ## What Golive Does Golive treats Environments as time-aware assets. It provides tools to track changes (past), monitor status (present), and plan usage (future). By integrating with Jira and DevOps tools, Golive helps teams coordinate, automate, and document their Environment management processes. ### Tracking Environments and Deployments *(Past and Present)* Golive centralizes Environment information so teams can monitor changes over time and access the current state of each Environment. * **Past**: Golive stores historical data, including deployment records, configuration changes, and status logs. This supports audit requirements, troubleshooting, and root cause analysis. * **Present**: Teams can view up-to-date details such as configuration, ownership, infrastructure, and deployed versions. Dashboards and issue panels in Jira display the current Environment status. Notifications can be configured to alert teams of any changes, such as deployments or status updates. Tracking supports traceability by linking Environments to Jira issues. This helps teams understand where and when testing or deployments occurred. For details, refer to the [Track Environments](https://golive.apwide.com/doc/latest/cloud/track-your-environments.md) section of this documentation. ### Scheduling Environments *(Future)* Golive provides scheduling features to coordinate the planned use of Environments. * **Future**: Teams can create bookings for upcoming tests, deployments, or maintenance activities. Visual tools like shared calendars and timelines help identify available time slots. * Golive automatically detects overlapping bookings and helps prevent conflicts. * Environment usage data supports forecasting, allowing teams to anticipate future demand and plan capacity accordingly. This scheduling functionality helps avoid resource conflicts and improves coordination across teams. For details, refer to the [Schedule Environments](https://golive.apwide.com/doc/latest/cloud/scheduling-environments.md) of this documentation. ### Orchestrating Environments *(Automation and Integration)* Golive connects with infrastructure, CI/CD systems, and monitoring tools to support automation of Environment-related tasks. * Teams can configure workflows in Jira to automate deployments, refreshes, and provisioning processes. * Environment self-service options can be enabled through Jira automation, reducing dependencies on operations or DevOps teams. This orchestration capability helps standardize and streamline Environment management, especially in complex or fast-paced delivery pipelines. For details, refer to the [Integrations](https://golive.apwide.com/doc/latest/cloud/integrations.md) section of this documentation. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Administrate Golive provides a dedicated page for administrators to manage and configure the app to align with your business needs. *** ** * ** *** ## Accessing Golive Settings 1. Click the **gear** icon located in the upper-right corner of any [Golive Page](https://golive.apwide.com/doc/latest/cloud/golive-pages.md). 2. From the drop down menu, select **Golive Settings**. *** ** * ** *** ## Golive Settings You'll find the following categories available in **Golive Settings**: ### Applications * [Applications List](https://golive.apwide.com/doc/latest/cloud/applications.md): Manage your applications, such as eCommerce platforms, payment systems, and ERP tools. * [Deployment Attributes](https://golive.apwide.com/doc/latest/cloud/manage-deployments.md): Configure Attributes for your Deployments. * [Jira Project Settings](https://golive.apwide.com/doc/latest/cloud/project-settings.md): Map Applications with Jira Projects and enable Golive Project Pages and Issue Panels. ### Environments * [Environments List](https://golive.apwide.com/doc/latest/cloud/manage-environments.md): Manage all your Environments, including Dev, eCommerce, and ERP Staging. * [Attributes](https://golive.apwide.com/doc/latest/cloud/attributes.md): Configure Attributes for your Environments. * [Panels](https://golive.apwide.com/doc/latest/cloud/environment-panels.md): Customizes Panels in Environment Details. * [Categories](https://golive.apwide.com/doc/latest/cloud/environment-categories.md): Define Environment Categories such as Dev, Staging, and Production. * [Statuses](https://golive.apwide.com/doc/latest/cloud/environment-statuses.md): Set Environment Statuses (Up, Down, etc.) * [Custom Fields](https://golive.apwide.com/doc/latest/cloud/environment-custom-fields.md): Configure custom fields for Environments to be used in your Jira issues. ### Scheduling * [Scheduling Configuration](https://golive.apwide.com/doc/latest/cloud/scheduling-configuration.md): Manage configuration for Environment bookings, changes, and blackouts. * [Shared Calendars](https://apwide.atlassian.net/wiki/pages/createpage.action?spaceKey=goliveserver&title=Working%20with%20Events%20and%20Calendars%20in%20a%20Timeline&linkCreation=true&fromPageId=23792615): Set up and manage shared calendars to coordinate timelines across teams. ### Settings * [Integration Hub](https://golive.apwide.com/doc/latest/cloud/integrations.md): Integrate Golive with your toolchain (GitHub, GitLab, Kubernetes, etc.). * [Automations](https://golive.apwide.com/doc/latest/cloud/automations.md): Configure automated triggers to send notifications or webhooks via email, Teams, or Slack. * [Permissions](https://golive.apwide.com/doc/latest/cloud/security-permissions.md): Manage user roles and permissions. * [Security Settings](https://golive.apwide.com/doc/latest/cloud/security-settings.md): Configure the security controls available for your Golive instance. * [Advanced Settings](https://golive.apwide.com/doc/latest/cloud/global-settings.md): Adjust advanced configurations, such as working hours per day or date formatting. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Advanced Automations & Scripts Coupling Golive \& Jira with automation and scripting apps like Script Runner or Automation for Jira gives you endless integration possibilities between Golive and your existing Jira issues/workflows. Check some examples here: * [ScriptRunner for Jira](https://golive.apwide.com/doc/latest/cloud/scriptrunner-for-jira.md) * [Jira Automation](https://golive.apwide.com/doc/latest/cloud/automation-for-jira.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # API Golive is equipped with a suite of diverse APIs, designed to empower you to create customized integrations with Jira and a range of other tools. From RESTful APIs to Java APIs and Environment Custom Field Rest APIs (for Jira Cloud), we provide the necessary building blocks to tailor your integration needs to your unique operational context. Explore each API in greater detail through our dedicated sub-pages. Each option below provides comprehensive guides, helping you leverage these APIs to optimize your tool integrations and workflows. * [Rest API](https://golive.apwide.com/doc/latest/cloud/rest-api.md) * [Environment Custom Field Rest API](https://golive.apwide.com/doc/latest/cloud/environment-custom-field-rest-api.md) ## Webhooks Golive's capabilities extend beyond local operations, enabling you to execute remote webhooks to effectively control and manage external systems. This feature ensures seamless interoperation, bolstering the automation and responsiveness of your infrastructure. Discover more about how Golive webhooks can be utilized to drive your external systems: [Trigger Custom Webhooks](https://golive.apwide.com/doc/latest/cloud/webhooks.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Application An Application represents a software service hosted within a specific environment. This service can be categorized as: * **Business Applications:** These support various business functions, such as *eCommerce* platforms, payment processing systems, or *Enterprise Resource Planning* (ERP) software like SAP. * **Technical Services:** These provide technical functionalities to support other applications. Examples include container orchestration platforms like Kubernetes or operating systems (OS) themselves. *** ** * ** *** ## Relationships and Structure * **Dependencies:** Applications can rely on other Applications to function properly. These dependencies create connections between them within the Environment. For details, refer to the [Environment Dependencies](https://golive.apwide.com/doc/latest/cloud/environment-dependencies.md) documentation. * **Tiers:** Complex Applications are often structured with multiple tiers, each performing specific tasks. When an Application includes tiers, it is classified as an **Application Landscape** . For more information, refer to the [Environment and Application Landscapes](https://golive.apwide.com/doc/latest/cloud/environments-tiers.md) documentation. * **Deployment:** Refers to the specific version of an Application currently running in a particular Environment. This ensures everyone is working with the same version and facilitates tracking changes. For details, refer to the [Deployment](https://golive.apwide.com/doc/latest/cloud/deployment.md) section in our Glossary. ![Environment Model - Concepts Connections V2.png](https://golive.apwide.com/__attachments/a_787ac225514b8966d30afffb56219e6f10da5cac0b953d636218622aaae3a791/Environment%20Model%20-%20Concepts%20Connections%20V2.png?cb=963ce8956bcfe7280cfef07bc9b0299c) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Application Custom Fields **Application Custom Fields** are used to link **Jira work items** and **Service Management Requests** with Golive Applications. This article explains why to use them, how to create them, and how to configure and use them. *** ** * ** *** ## Why Use Application Custom Fields Application Custom Fields allow teams to associate Jira work items with Golive Applications. This helps you track [accurate statistics](https://golive.apwide.com/doc/latest/cloud/gadgets.md), such as the number of issues created, reproduced, or tested for specific Applications. **Info** **Application Custom Fields** work similar to the **Version** concept in Jira. Like Versions, where multiple fields (e.g., Fix Version/s and Affects Version/s) use the same inventory, Application Custom Fields draw from a single list of Applications but can appear in multiple fields on the same issue. *** ** * ** *** ## Create an Application Custom Field ### Requirements You must have the **Jira Administrator** permission to create new custom fields from the **Fields** section. ### Steps 1. On the Jira **Fields** page, click **Create new field**. 2. In the **Field type** field, select **Apwide Golive Application**. 3. In the **Name** field, type the name of your new custom field, for instance "Application". 4. Click **Create**. ![image-20260624-175248.png](https://golive.apwide.com/__attachments/a_76a032d72b53051c66f14126b27c382d3af7fc3d0a03ce574d27c7dc512195de/image-20260624-175248.png?cb=010ec7029422158682bee0a68814ee5a) Create field form To make the **Custom Field** visible in work types, add it to your screens: * For **company-managed projects** , refer to: [Add a custom field to a screen](https://confluence.atlassian.com/adminjiracloud/add-a-custom-field-to-a-screen-991923749.html). * For **team-managed projects** , refer to: [Add a custom field to a team-managed project](https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/). *** ** * ** *** ## Update the Configuration of a Field By default, an Application Custom Field includes all Application linked to the Jira project. You can restrict this behavior if needed. ### Requirements You must be a **Jira Administrator**. ### Steps 1. On the Jira **Fields** page, search for the field you want to configure. 2. Next to the field, open the three-dots menu and click on **Contexts and default values**. 3. For the relevant context, click **Edit custom field config**. ![image-20260624-175456.png](https://golive.apwide.com/__attachments/a_68f71fcb649d59bafa4c146cb208268f526c8e4cb006718d152211bd576653c6/image-20260624-175456.png?cb=6e9f914ff1f9e843929660dc9a5bff50) Edit custom field configuration ![image-20260624-175628.png](https://golive.apwide.com/__attachments/a_acee761634b014ad05282a334657ca79de47a52aadfe51f0db3178f7eaf8ec7d/image-20260624-175628.png?cb=2b2bf7cd359b8f60351bbb98df1f35cd) Application custom field configuration *** ** * ** *** ## Select Applications on the Issue Screen Once you've configured an **Application Custom Field** and added it to a screen, you can easily select Applications directly from your work item in Jira. ### Requirements * Available Environments depend on your Project and Application setup. * By default, Jira shows only applications mapped with the current space. ### Steps 1. Open the **Jira work item**you want to edit. 2. Locate the **Application field**. 3. Search for and select one or more **Applications**. **Tip** To remove an Application, click the **x**icon next to it. ![image-20260624-180239.png](https://golive.apwide.com/__attachments/a_5b31ad90fb90e35926ff056bbcfdf976105cf12a4aacb71ce4952e3632caa8da/image-20260624-180239.png?cb=25cf0ac6c984a3860e85ee7540ff65d6) Application custom field edition *** ** * ** *** ## Automation To update Golive custom fields automatically, refer to our [Jira Automation examples](https://golive.apwide.com/doc/latest/cloud/automation-for-jira.md) and our [Rest API documentation](https://golive.apwide.com/doc/latest/cloud/rest-api.md#Jira-Cloud-REST-API). --- version: "latest" variant: "Golive Cloud" language: "en" --- # Manage Applications In this article, you'll learn how to set up applications and deployments in **Golive** . For a deeper understanding about these concepts, refer to the [Understand Environment Core Concepts](https://golive.apwide.com/doc/latest/cloud/understand-environment-core-concepts.md) article. *** ** * ** *** ## Requirements You'll need **Manage Applications** global permission to perform operations on applications. For more details on permissions, refer to the [Permissions](#) article. *** ** * ** *** ## Setting up an Application To set up an application in Golive, follow these steps: 1. In **Golive** , Click the**gear** icon located on the upper right corner of **Golive Pages**. 2. From the drop-down menu, select **Golive Settings**. 3. In the **Applications** section, select **Applications List**. 4. Click the **Add Application** button located at the top right corner of the **Applications**page. **Info** To make modifications to an existing application, click the **Edit** button represented by a pencil icon. 4. Choose a name for your new application. 5. Click **Create**. *** ** * ** *** ### Jira Versions Tab The **Jira Versions** tab controls how application versions are mapped to Jira Versions, also called Jira Releases, and how Golive updates the **Fix Versions** field of deployed work items. #### Primary Jira Space Select the Jira space that acts as the source of truth for the application versions. When a primary Jira space is selected and a new deployment is created from Golive: * Golive suggests versions from that space. * Golive creates a new version in that space when the user recording the deployment has the **Manage Versions** permission. This happens even when the deployment does not contain any work item from the primary space. Leave this field empty if the application versions should not be managed in a specific Jira space. #### Version Name Prefix Optionally define a prefix used to create and match Jira Versions. Golive only suggests versions whose names start with this prefix. When Golive creates a version, it automatically adds the prefix if it is not already included in the version name. Trailing spaces are significant. For example, with the prefix `ECOM `, the application version `1.2` is created as `ECOM 1.2`. #### Fix Version Updates Choose how Golive updates the **Fix Versions** field when deployments are recorded: * **Do not update Fix Versions:** Golive does not modify the Fix Versions field of deployed work items. * **Update Fix Versions in the primary Jira space only:** Golive updates work items belonging to the primary Jira space. * **Update Fix Versions in all deployed work item spaces:** Golive updates work items in every Jira space referenced by the deployment. With the last option, Golive automatically creates the missing Jira Version in another space when: * The deployment contains at least one work item from that space. * The user has permission to create versions in that space. * The matching version does not already exist. The selected primary Jira space remains the source of truth for the application versions. The **Synchronized Jira Spaces** setting is now deprecated. Use Jira Automation when versions need to be synchronized with additional spaces independently of the work items included in a deployment. [++Learn how to synchronize Jira versions with Automation++](https://community.atlassian.com/forums/Jira-articles/How-to-Sync-Jira-Versions-Across-Projects-Using-Jira-Automation/ba-p/3045656) Existing configurations will continue to work until **October 30, 2026**. Once all values are removed from the deprecated field, it will disappear and cannot be configured again. **Info** To learn more about Jira Versions and Releases, refer to the [Atlassian documentation](https://support.atlassian.com/jira-cloud-administration/docs/manage-versions/). *** ** * ** *** ### Deployments Tab The **Deployment Settings** tab allows you to choose how you want to manage deployments of your application in Golive. Follow these steps to configure your application deployment management. 1. Within the **Application** dialog, navigate to the **Deployments** tab. 2. Choose which information should be displayed and editable when performing a new deployment from Golive screens: * **Show build number** : Enable this option when you need to *distinguish different builds* of a same version. * **Show description** : Enable this option to set a *description for your deployment*. This field supports basic HTML tags for rich content, and is unlimited in size. * **Enable edition of deployed issues** : When enabled, users will be able to *add/remove deployed issues*when creating or editing a deployment in Golive. 3. Define customizable **Deployment Attributes** to store additional information in each of your application deployments. **Info** If the **Deployment Attribute** you need isn't listed, click **+ Create**at the bottom to add a new one. 4. Choose whether to enable **Track re-deployments of the same version**. By default, Golive merges two successive deployments of the same version with the same build number to a a given environment. **Warning** Activate the **Track re-deployments of the same version** option only if you *absolutely need* to keep track of every successive re-deployment of the same version and the same build number in your deployment history. ![:light_bulb_on:](https://golive.apwide.com/__attachments/a_beecf40031648ae715952068cc9ac9e6f85674981b7271ba0e387d2636adeb2c/atlassian-light_bulb_on?cb=485b9fcaee6e0d0eefa559cab514727e) **Tip** The best practice is to use different build numbers to track successive deployments of the same version (e.g., common when working with "snapshot" releases). *** ** * ** *** ### Application Tiers Tab To configure an application composed of multiple tiers, tenants, components, modules or markets, follow these steps: **Info** For detailed information about multi-tiers and multi-tenancy applications, refer to the [Understand Environment and Application Landscapes](https://golive.apwide.com/doc/latest/cloud/environments-tiers.md) article. 1. Within the **Application** dialog, navigate to the **Applicaton Tiers** tab. 2. Add, remove and re-order the list of application tiers in the **Application Tiers** field. 3. Once *at least one* application tier is set up at the application level, you'll be able to add a **Tier** at the environment level. After adding tiers, you can browse and edit the created application tiers from the list of applications on the **Applications** page To manage all existing application tiers, including orphaned ones, click **Application Tiers** located at the top of the **Applications** page. This will allow you to manage all your application tiers from the **Application Tiers** page. *** ** * ** *** ### Dependencies Tab To set up dependencies of a current application, follow these steps: **Info** For detailed information about dependencies, refer to the[Environment Dependencies](https://golive.apwide.com/doc/latest/cloud/environment-dependencies.md) article. 1. Within the application dialog, navigate to the **Dependencies** tab. 2. Enter a dependency. 3. When *at least one* dependency is setup at application level, you'll be able to add dependencies at the environment level. *** ** * ** *** ## Converting Application Tiers ↔︎ Application **Important** Ensure you have a solid understanding of tiers and dependencies before restructuring your environments and converting your applications. For more information, refer to the following articles: * [Environment and Application Landscapes](https://golive.apwide.com/doc/latest/cloud/environments-tiers.md) * [Environment Dependencies](https://golive.apwide.com/doc/latest/cloud/environment-dependencies.md) ### Convert an Application into Application Tiers **Info** You must first remove any existing application tiers from an application before converting it to application tiers. To convert existing applications into application tiers, follow these steps: 1. Go to the **Applications** page. 2. Locate the application you want to convert. 3. Click the **Convert to tier**button corresponding to the application. This button is located in the last column of the application row. ### Convert Application Tiers into an Application **Info** You can only convert application tiers that are not already used by an application. To convert existing application tiers into applications, follow these steps:: 1. Go to the **Applications** **Tiers**page. 2. Locate the application tier you want to convert. 3. Click the**Convert to application** button corresponding to the application tier. This button is located in the last column of the application tier row. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Golive Core Concepts ![Environment Model - Concepts Connections V2.png](https://golive.apwide.com/__attachments/a_787ac225514b8966d30afffb56219e6f10da5cac0b953d636218622aaae3a791/Environment%20Model%20-%20Concepts%20Connections%20V2.png?cb=963ce8956bcfe7280cfef07bc9b0299c) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Archive Environments Archiving Environments allows you to hide inactive or deprecated Environments from [Golive Views](https://golive.apwide.com/doc/latest/cloud/golive-views.md) without deleting them. This article explains how to exclude part of your Environments from Golive Views by archiving them. **Info** Archiving is managed through a custom Environment Attribute and View filtering in Golive. *** ** * ** *** ## Archive Environments To exclude specific Environments from your Golive Views, follow these steps. ### Step 1: Create an Archived Attribute Create a **Single Select Environment Attribute** named **Archived** with a single value **Yes** . For detailed instructions, refer to the [Environment Attributes](https://golive.apwide.com/doc/latest/cloud/customize-environment-attributes.md) documentation. ### Step 2: Update Golive Views In your Golive Views, add the `Archived = !` filter. This filter excludes all Environments marked as Archived. For more details, refer to the [Search Environments](https://golive.apwide.com/doc/latest/cloud/search-environments.md) documentation. ### Step 3: Archive an Environment 1. Go to the **Environment Details** view. 2. Add the **Archived** attribute to the archived Environment. 3. Select **Yes**. The Environment is now archived and no longer appears in Golive Views using the `Archived = !` filter. *** ** * ** *** ## Unarchive Environments To unarchive an Environment: 1. Go to the **Environment Details** view. 2. Remove the **Archived** attribute from the Environment entirely. **Important** Do not just clear the value. The attribute itself must be removed for the Environment to reappear in Golive Views. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Attributes **Attributes,** like**Jira Custom Fields** ,enable users to store and share specific information relevant to their context.They offer a structured approach for customizing and extending a system's functionality, similar to how Jira Custom Fields capture additional data for issues. ## Types of Attributes ### Markdown **Markdown Attributes** support multiline editing and utilizes [Markdown syntax](https://www.markdownguide.org/basic-syntax/), making it easy to format text with various styles. This attribute type is ideal for adding descriptions, notes, or instructions that require more than plain text. ### Secured Attributes **Secured Attributes** are particularly useful for storing credentials or any sensitive data that shouldn't be accessible to all users authorized to view an Environment or a Deployment. We do not recommend using secured attributes for storing highly sensitive information like production secrets. Secured attributes values are stored in plain text in the Golive database. By using the **Secured** option, you can limit the visibility of sensitive attributes. Only users with the *View Secured* *Attributes* or *Edit Secured Attributes* permissions will have access to view or update these attributes. For detailed information, refer to the [Security \& Permissions](https://apwide.atlassian.net/wiki/spaces/GOLIVESERVER/pages/434274612/Manage+Environment+Attributes#) documentation. ### Single Select **Single Select** attributes allows you to determine pre-defined options that users can choose from, ensuring consistent data entry. This type of attribute is designed to reduce the risk of errors often found with free-form text entry. You can safely convert your existing attributes to **Single Select** without losing their current values. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Golive Automations Harness the power of Golive Automations to facilitate streamlined operations within your organization. From dispatching real-time notifications to instigating the deployment of a new version, or even provisioning a fresh environment - all can be achieved at the click of a button. Embrace the convenience of automated processes and watch as your workflow becomes more efficient and responsive. * [Manage Automations](https://golive.apwide.com/doc/latest/cloud/automations.md) * [Trigger Custom Webhooks](https://golive.apwide.com/doc/latest/cloud/webhooks.md) ## Golive Automation Examples ![10 minutes to get a new Jenkins](https://golive.apwide.com/__attachments/a_9b8822f2266c9e45a95168a625436a180922266e944b0fa572c42d05cd340e00/10min_to_get_a_new_Jenkins.png?cb=061806e82921916652cb97b9c0b3db8a) [**How the largest food company provisions Jenkins instances in less than 10 minutes**](https://www.apwide.com/on-demand-jenkins-provisioning-jira-kubernetes/) ![Blog-Post-Top-4-recipes-Jira-Docker.png](https://golive.apwide.com/__attachments/a_cfb265fbe4726a9dc607ab1503eb4f6f7f8a88e77adc564859bd164db8353652/Blog-Post-Top-4-recipes-Jira-Docker.png?cb=a002849d336d821c1dfc6456e7db5f17) [**Top 4 recipes to deploy Jira with Docker in a single click**](https://www.apwide.com/top-4-recipes-deploy-jira-with-docker-rancher-kubernetes/) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Jira Automation Use [Jira Automation](https://marketplace.atlassian.com/apps/1215460/automation-for-jira-server) to keep your Golive environment data current and reduce manual updates by automatically syncing [Environment Custom Fields](https://golive.apwide.com/doc/latest/cloud/environment-custom-fields.md). *** ** * ** *** ## Use Cases * [Jira Automation Actions](https://golive.apwide.com/doc/latest/cloud/golive-jira-automation-actions.md) * [Create a Booking on a Specific Environment](https://golive.apwide.com/doc/latest/cloud/create-a-booking-on-a-specific-environment.md) * [Create a Jira Ticket When an Environment Attribute Is Updated](https://golive.apwide.com/doc/latest/cloud/create-a-jira-ticket-on-environment-attribute-upda.md) * [Use Jira Tickets to Drive Deployments](https://golive.apwide.com/doc/latest/cloud/use-jira-tickets-to-drive-deployments.md) * [Configure Automatic Deployments After Environment Change Completion](https://golive.apwide.com/doc/latest/cloud/configure-automatic-deployments-after-environment-.md) * [Edit Deployed Work Items](https://golive.apwide.com/doc/latest/cloud/edit-deployed-work-items.md) * [Populate Environments from Application + Category fields](https://golive.apwide.com/doc/latest/cloud/populate-environments-from-application-category-fields.md) * [Sync Attributes Between Environments of the Same Application](https://golive.apwide.com/doc/latest/cloud/sync-attributes-between-environments-of-the-same-a.md) * [Populate Jira Approvers from Golive Environment Configuration](https://golive.apwide.com/doc/latest/cloud/populate-jira-approvers-from-golive-environment-co.md) * [Jira Forms: Sync a Golive Environment Field with a Jira Field](https://golive.apwide.com/doc/latest/cloud/jira-forms-sync-a-golive-environment-field-with-a-jira-field.md) ### Additional Use Cases * [Use Jira tickets to drive Deployments](https://golive.apwide.com/doc/latest/cloud/use-jira-tickets-to-drive-deployments.md) * [Autofill Jira Versions](https://golive.apwide.com/doc/latest/cloud/version-autofill.md) *** ** * ** *** ## Need Assistance? For support with integrating Golive and Jira Automation, reach out to our [help center](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1). --- version: "latest" variant: "Golive Cloud" language: "en" --- # Manage Automations Golive Automation can trigger execution of actions when something happens to environments or to Jira tickets linked to environments. You must be a **Golive Administrator** to manage Automations. For more information, refer to [Permissions](https://golive.apwide.com/doc/latest/cloud/security-permissions.md). ## Automations Page All Automations are managed on Automations Page. You can access it from any [Golive Page](https://golive.apwide.com/doc/latest/cloud/golive-pages.md): ![image-20260616-135846.png](https://golive.apwide.com/__attachments/a_00bf622c74c81bdc3008218c9d4100a359dc82c007b288ae48989e23ec45ab23/image-20260616-135846.png?cb=a19cb91e29d7634deafd4ff6fac71746) The main Automations screen lists existing automations: ![image-20260616-140152.png](https://golive.apwide.com/__attachments/a_091b6cb8f6e1c49d83cf03dc0978665eaffc2a229be63c0c4936560318fe7547/image-20260616-140152.png?cb=5d9fd5b9bb540978ba052f3b6261118d) From here, you can: * enable/disable an Automation using the *Active* toggle * click on the *Name* of an Automation to show its details * click on the *Executions* status to open the Automation execution logs ## Create an Automation Click "Add Automation" button on the top right corner and choose the type of action that you want to perform: ![spaces%2F-MWcvo1Q5iQLYT9dKP7d-855039963%2Fuploads%2Fgit-blob-8ad9eb570f27a5343c9eb36899b74b9d3c69e04c%2F119439693%20(1).png?alt=media](https://golive.apwide.com/__attachments/a_74e8640448d960d7c08e27befac93fdc6bd62c15d4215c3a06c46aa4b03edf6f/spaces%252F-MWcvo1Q5iQLYT9dKP7d-855039963%252Fuploads%252Fgit-blob-8ad9eb570f27a5343c9eb36899b74b9d3c69e04c%252F119439693%2520(1).png%3Falt=media?cb=0486583180c2091d32e06a167f050099) ## Configure the Trigger Choose what kind of event should trigger the action: ![spaces%2F-MWcvo1Q5iQLYT9dKP7d-855039963%2Fuploads%2Fgit-blob-3e8429309dbd6dd3e54cb27d9cc42d0927ba40ea%2F119439699%20(1).png?alt=media](https://golive.apwide.com/__attachments/a_600422930d6983e7d89b0ebb77dabd50097e7a5884eff09576bd150ee4d23708/spaces%252F-MWcvo1Q5iQLYT9dKP7d-855039963%252Fuploads%252Fgit-blob-3e8429309dbd6dd3e54cb27d9cc42d0927ba40ea%252F119439699%2520(1).png%3Falt=media?cb=cf19ad772b3529ddd374c1aa479fd465) ## Configure the Action The setup of the action to execute depends on the type of Automation selected: * [Email Automation](https://golive.apwide.com/doc/latest/cloud/custom-emails.md) * [Slack Automation](https://golive.apwide.com/doc/latest/cloud/slack.md) * [MS Teams Automation](https://apwide.atlassian.net/wiki/pages/createpage.action?spaceKey=goliveserver&title=Send%20MS%20Teams%20Messages&linkCreation=true&fromPageId=74285061) * [Webhook Automation](https://golive.apwide.com/doc/latest/cloud/webhooks.md) ## Execution Logs You can access the logs of latest executions of your automation from the automations home page: ![spaces%2F-MWcvo1Q5iQLYT9dKP7d-855039963%2Fuploads%2Fgit-blob-9d8a4324b43e72e6e16edf7fb8be89ed6b4696ff%2F119439705%20(2).png?alt=media](https://golive.apwide.com/__attachments/a_30e85bb35ad8d181aed00b4a528f1c1aea5f075a470c80f4b6d786fcbf4eb03b/spaces%252F-MWcvo1Q5iQLYT9dKP7d-855039963%252Fuploads%252Fgit-blob-9d8a4324b43e72e6e16edf7fb8be89ed6b4696ff%252F119439705%2520(2).png%3Falt=media?cb=145149d9f1c1d92e86de5ace48e97b59) Or from a given automation: ![spaces%2F-MWcvo1Q5iQLYT9dKP7d-855039963%2Fuploads%2Fgit-blob-baa120897f1db2aac0b0e535b8dd9323e7cbc499%2F119439711%20(2).png?alt=media](https://golive.apwide.com/__attachments/a_e87adb26b1bd02c2f18309e9cc7fb6d3acc796d826bce2e09fbf7cd9f23e80a6/spaces%252F-MWcvo1Q5iQLYT9dKP7d-855039963%252Fuploads%252Fgit-blob-baa120897f1db2aac0b0e535b8dd9323e7cbc499%252F119439711%2520(2).png%3Falt=media?cb=b42bb3a2dea4213843e49c89ae074eab) ### Executions Details In order to help you to debugging your automations, you can access the detailed logs of latest executed actions: ![spaces%2F-MWcvo1Q5iQLYT9dKP7d-855039963%2Fuploads%2Fgit-blob-b2dbbe833712149d02d1a35b9c0761abb5817920%2F119439717%20(1).png?alt=media](https://golive.apwide.com/__attachments/a_b0a55bc5b506d422df2a9b2c64bca21e54b53aa56930245fca620ed7fb563d82/spaces%252F-MWcvo1Q5iQLYT9dKP7d-855039963%252Fuploads%252Fgit-blob-b2dbbe833712149d02d1a35b9c0761abb5817920%252F119439717%2520(1).png%3Falt=media?cb=86f0bd33d544b68fcd0b16560c98a63e) Click on the Payload icons to open details of Error, Request and Response: ![image-20220531-162154.png](https://golive.apwide.com/__attachments/a_653ea4b880ba1d721cf8d4faf5236dc16077fe4fc5e317d3462c9d05554760da/image-20220531-162154.png?cb=c90343d59ea025eae906a7b9e06f4695) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Azure DevOps (TFS, VSTS) We provide a [free extension](https://marketplace.visualstudio.com/items?itemName=Apwide.ApwideGoliveForJira) that is compatible with both on-premise Azure DevOps Server (Team Foundation Server, TFS) and cloud based Azure DevOps Services (Visual Studio Team Services, VSTS). *** ** * ** *** ## Benefits of the Apwide Golive Azure DevOps Marketplace Extension With the Apwide Golive and Azure extension, you can leverage the robust capabilities of Azure DevOps and combine them with the comprehensive test environment management features of Apwide Golive for Jira. This integration enables you to easily connect your Azure DevOps projects with Apwide Golive. This connection establishes a bridge between the two platforms, enabling smooth data exchange and synchronization. Deployments and relevant environment information required by testers, release managers,... and other teams, are automatically pushed to Apwide Golive and Jira from your Azure DevOps pipelines. Learn how automatically send deployment and environment information to Golive/Jira from your Azure DevOps pipelines in [Apwide Golive Azure Extension Documentation](https://marketplace.visualstudio.com/items?itemName=Apwide.ApwideGoliveForJira). *** ** * ** *** ## Common use cases Environment Tracking * [Track Application Deployments](https://golive.apwide.com/doc/latest/cloud/push-deployment-information-to-jira-and-golive.md) * Track Application Releases \& Builds * [Track Environment Statuses](https://golive.apwide.com/doc/latest/cloud/track-environment-statuses.md) ## Contact us We are at your disposal if you have question or need support regarding Apwide Golive and this integration with Azure DevOps: --- version: "latest" variant: "Golive Cloud" language: "en" --- # Bamboo *** ** * ** *** Learn how to integrate Atlassian Bamboo CI with Golive with particular focus on: *** ** * ** *** ## Video Tutorial *** ** * ** *** ## Relationships between Bamboo and Golive concepts | **Bamboo concept** | **Detail** | **Golive equivalence** | **Detail** | |--------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Project | Group logically **build plan** together. | - | - | | Build Plan | Define the build process of your software and usually result in output binaries named **artefacts** | - | - | | Artefacts | Output result of a build, usually a "physical" binary (jar, zip, war...) of your application that can be added to a **release** for being deployed on an **environment** | - | - | | Stage | Represents a specific step in your **build plan** . It's composed of **jobs** that can be run in parallel. **Plan** can be composed of several stages and you can **trigger** different action on its successful execution (eg: deployment, trigger another plan...). A stage could be used to group the different **jobs** used to compile your software, and another stage could be used to group all the testing **jobs**. | - | - | | Job | A job contains the sorted list of **tasks** (shell scripts, ant, maven, command) used to build your software. | - | - | | Task | An atomic operation. Could be a shell script, an ant or maven command, a git operation... | | Tasks are used to publish data from Bamboo to Golive using the [Rest API](https://golive.apwide.com/doc/latest/cloud/rest-api.md) that can be called by a script task (eg: curl) | | Release | Releases are used to track exactly what software was deployed to an environment. In essence, a release is a snapshot of any number of artifacts that will be used in the deployment process. Releases are versionned and they follow a naming convention that can be used by Bamboo to automatically generate the next available version number when the full chain is fully automated. | Deployment | In Golive, current version of a specific application on a specific environment is tracked by a Deployment object. Golive provides a [Rest API](https://golive.apwide.com/doc/latest/cloud/rest-api.md) that can be called to create a new deployment and update the deployed version of an environment. By synchronising Bamboo releases with Golive deployments, your Jira users will be able to always get the current up to date deployment information + all history of past deployments. | | Deployment Project | Deployment project is the container that holds: * Environments that represent the physical environments, such as QA, Staging and Production * Releases. | - | In some ways, you can see Bamboo deployment projects and projects as something that can be easily mapped with Golive application concept, more details below. | | Environment | An environment is the mapping of a deployed release on a specific subset of machines. Environment contains its deployment plan (similar to build plan but to deploy a release on a specific machine/environment) which defines how a specific release (a set of artefacts) will be published on its environment (that can be composed of several machines). It's in this deployment plan that we are going to add additional steps to publish/synchronise the release version between Bamboo and Golive | Environment (Application-Category) | Golive Environment is the equivalent of Bamboo Environment. It's defined by the combination of an Application (eg: eCommerce) and a Category (eg: Prod, QA, Demo...). An environment can have one status and one release number deployed at a time. In Bamboo, even if an environment is described as "Staging", it may be composed by several applications. In Golive you may split this environment into several environments per application (ex: eCommerce Staging and ERP Staging) if you want to easily differentiate their technical requirements, lifecycle,... That's why in Golive environments are defined by the combination of a category (eg: Staging, Prod...) and an application (eg: eCommerce, ERP...). You can naturally freely decide how you want to model and map environments in both tools. | | | | Application | Golive provides to Jira the concept of Application, that you can use to map your applications to your Jira projects and Jira versions. | *** ** * ** *** ## Continuous Integration Use Case In our use case, you will learn how to automatically push deployment information to Golive when a deployment is triggered in Bamboo. To achieve this, you have to add one task to your existing build process. This task will publish new release version to Golive using the [Rest API](https://golive.apwide.com/doc/latest/cloud/rest-api.md). ### Screen flow In Bamboo, we can see how project and environment have been structured: ![Bamboo-Env.png](https://golive.apwide.com/__attachments/a_3efcc1bed2d5de4e9c44d5cf8c75b76d5edae167715566ef85bef8a4ccf7824b/Bamboo-Env.png?cb=79c9a16d2f23e759ced1a6be481cafbb) Here the equivalent environment structure in Golive: ![Apwide-Env.png](https://golive.apwide.com/__attachments/a_71a10551d0ef3dfd3d85b0c313364e9b74fb437f5d56b673952402c09ce916b9/Apwide-Env.png?cb=9328a61c107b97321524eb68f5fdfcf6) Now, if we look at the deployment plan in bamboo for the dev environment, we can see the following tasks: ![Bamboo-Deploy-Task.png](https://golive.apwide.com/__attachments/a_1343500e19998917bdbf47b1e4b1cfacc4187dc4d126e122393cc4eb457b192a/Bamboo-Deploy-Task.png?cb=34fb0c3b2ab91a26c2cb2d4f9c622863) We have added a curl script to call the Golive [Rest API](https://golive.apwide.com/doc/latest/cloud/rest-api.md) Script samples to call Golive Rest API from Bamboo: ### Update status to "deploy" Bash curl --user ${bamboo.apwide.user}:${bamboo.apwide.password} -X PUT \ '${bamboo.apwide.url}/status-change?application=${bamboo.deploy.project}&category=${bamboo.deploy.environment}' \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ -d '{ "name": "Deploy" }' ### Update deployed version Bash curl --user admin:admin -X PUT \ 'http://localhost:8080/rest/apwide/tem/1.1/deployment?application=${bamboo.deploy.project}&category=${bamboo.deploy.environment}' \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ -d '{ "versionName": "${bamboo.deploy.release}", "deployer": "bamboo" }' ### Update environment attributes Bash curl --user ${bamboo.apwide.user}:${bamboo.apwide.password} -X PUT \ '${bamboo.apwide.url}/environment/${bamboo.apwide.environment.id}' \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ -d '{ "url": "${bamboo.application.url}", "attributes": { "Last Deploy Result URL": "${bamboo.resultsUrl}", "Bamboo Environment URL": "${bamboo.bamboo.url}/deploy/viewEnvironment.action?id=1245188", "Bamboo Application URL": "${bamboo.bamboo.url}/deploy/viewDeploymentProjectEnvironments.action?id=1146883", "Owner": "${bamboo.environment.owner}", "Database": "${bamboo.environment.database}", "OS": "${bamboo.environment.OS}", "# servers": "${bamboo.environment.servers}" } }' ### Update status back to "up" Bash curl --user ${bamboo.apwide.user}:${bamboo.apwide.password} -X PUT \ '${bamboo.apwide.url}/status-change?application=${bamboo.deploy.project}&category=${bamboo.deploy.environment}' \ -H 'Accept: application/json' \ -H 'Content-Type: application/json' \ -d '{ "name": "Up" }' ### Bamboo variables You can use variables from: * [default bamboo variables](https://confluence.atlassian.com/bamboo/bamboo-variables-289277087.html) * or create your own custom [global variables](https://confluence.atlassian.com/bamboo/defining-global-variables-289277112.html): ![Bamboo-Global-Variables.png](https://golive.apwide.com/__attachments/a_f1b8913fd5989328880889fc685f33a20a1aa9a2bf9b5b5e383de15d83a10d4d/Bamboo-Global-Variables.png?cb=1a6ff3be9f8a85772169b4e5a3cfed53) * or even create some [environment specific variables](https://confluence.atlassian.com/bamboo/variables-for-deployment-environments-342754180.html): ![Bamboo-Env-Variables.png](https://golive.apwide.com/__attachments/a_c76a38dfcc20db71a1e7c02c4eb1ca39b5e4655d8d9b83a75d2774797e45adf3/Bamboo-Env-Variables.png?cb=3f2add1854b1470f61de8117e685b677) ### Build and Deployment Process Example 1. A commit is triggered on an SCM 2. Build plan, located in a specific project (eg: eCommerce) is triggered 3. When build is successful, artefact is generated and made available to other build/deploy plans 4. In a deployment project (eg: eCommerce), a trigger is configured to trigger deployment to an environment (eg: Dev) when the corresponding project build plan was successfully built 5. A release (following the naming convention scheme) is generated containing the artefacts 6. The deployment plan deploy the release to the environment 7. The last task of the deployment plan updates de the deployed version of the corresponding environment in Golive *** ** * ** *** ## Recommendations * In Bamboo, if a deployment plan is triggered several times with the same release on the same environment (with the same version number), Golive will not consider this deployment as a new deployment. You should add something different (ex: build number) in the name of the deployed version in order to track this kind of change in Golive deployment history. * If you proceed with the following mapping, you can easily reuse Bamboo variables to complete the call to the Golive [Rest API](https://golive.apwide.com/doc/latest/cloud/rest-api.md) : * Bamboo **deployment** **project** to a Golive **application** * **Environment name** to **Category Name** * **Release name** to **deploy version name** * Golive Rest API credentials should never be declared in clear in the tasks (use global variables). *** ** * ** *** ## Resources * [Understanding deployment releases](https://confluence.atlassian.com/bamboo/understanding-deployment-releases-357335182.html) * [How to create a deployment workflow](https://confluence.atlassian.com/bamboo/deployment-projects-workflow-362971857.html) * [How to define global variables in Bamboo](https://confluence.atlassian.com/bamboo/defining-global-variables-289277112.html) *** ** * ** *** --- version: "latest" variant: "Golive Cloud" language: "en" --- # Bitbucket Our future integration with Bitbucket will allow teams to connect their Bitbucket pipelines with Golive. With this integration, changes in Bitbucket - such as builds or deployments - will be automatically reflected in Jira and Golive. *** ** * ** *** ## Benefits * **Automated Updates**: Keep your environment and deployment information always up-to-date in Jira, without manual intervention. * **Enhanced Visibility**: Track deployments of your Jira tickets easily and accurately. * **Streamlined Processes**: Reduce the need for cross-platform checks and manual updates. *** ** * ** *** ## Integration Use Cases ### Automated Environment Status Updates Sync Apwide Golive with Bitbucket Pipelines to automatically update the status of environments in Jira. For instance, when a deployment is successfully completed in Bitbucket, Apwide Golive reflects this change in the corresponding environment within Jira, ensuring real-time accuracy in environment tracking. ### Pull Request Deployment Tracking Integrate Bitbucket pull requests with specific environments in Apwide Golive. This allows teams to see which Jira tickets (features or fixes), represented by pull requests in Bitbucket, are currently deployed in specific environments managed in Jira. It's key for understanding the deployment status of new features or bug fixes. ### Release Management Coordination Use Bitbucket's release and tagging features to inform environment status in Apwide Golive. When a new release is tagged in Bitbucket, Apwide Golive updates the status of related environments in Jira, aiding in synchronized release planning and execution. *** ** * ** *** ## Get Early Support We are currently in the process of creating comprehensive documentation that will provide step-by-step examples of how to set up and use this integration. These examples are designed to guide you through the process, making it smooth and hassle-free. If you are interested in setting up this Bitbucket integration before the release of our full documentation, we are here to help with our professional services. Click on the link below, explain your use case, and our team will reach out to you to schedule a session and get you started with integrating Golive with Bitbucket. [**Request Bitbucket Integration Assistance**](https://apwide.atlassian.net/servicedesk/customer/portal/1/group/1/create/1?summary=Bitbucket%20Integration%20Assistance) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Blank Timeline The **Blank Timeline** template offers an empty timeline. This template is especially useful if you are already familiar with the timeline features and need to build your timeline from scratch. After its creation, you can customize swimlanes and add calendars. In this article, you'll find step-by-step instructions on how to create a view using it. For additional information on how **Timeline Views** function, refer to the [Timeline Views](https://golive.apwide.com/doc/latest/cloud/timeline-views.md) article. ![Apwide Golive Media - Blank Timeline.png](https://golive.apwide.com/__attachments/a_c736d178476d7f4ce317b9bda68ef302ef6b6917493702e98a694a84617fd179/Apwide%20Golive%20Media%20-%20Blank%20Timeline.png?cb=88d2d0dc1b9f79ce9d5dea49f8f4fe16) Example of a View using the Blank Timeline Timeline template. *** ** * ** *** ## Set up the Blank Timeline Template To set up the Blank Timeline template, follow these steps: 1. In **Golive** , locate and click the [View Browser](https://golive.apwide.com/doc/latest/cloud/view-browser.md). 2. From the dropdown menu, select **+ Create View**. 3. From the options provided, select the **Blank Timeline**template. 4. Give your new Timeline a descriptive name for easy identification. 5. Click **Create** to generate the new Timeline. The newly created Timeline based on the **Blank Timeline** template will be displayed. You can always access it from the **View Browser** (More views) and mark it as favorite by clicking the star icon next to the View title. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Navigate Golive *** ** * ** *** Learn how to move around Golive and customize what you see so you can easily browse and update your Environment information. This section covers: * [Golive Pages](https://golive.apwide.com/doc/latest/cloud/golive-pages.md) * [Golive Views](https://golive.apwide.com/doc/latest/cloud/golive-views.md) * [View Templates](https://golive.apwide.com/doc/latest/cloud/view-templates.md) * [Spider Map](https://golive.apwide.com/doc/latest/cloud/spider-map.md) *** ** * ** *** --- version: "latest" variant: "Golive Cloud" language: "en" --- # Build the Environment Inventory Your **Environment Inventory** is the foundation of Golive. It brings together the systems you want to manage, the categories that describe them, and the attributes that capture their details. This article acts as a *map of the process* . It outlines the key steps to build your Environment Inventory and provides links to detailed instructions for each step. You can also use the **Get Started wizard** in-app to guide you through the process. ![:light_bulb_on:](https://golive.apwide.com/__attachments/a_beecf40031648ae715952068cc9ac9e6f85674981b7271ba0e387d2636adeb2c/atlassian-light_bulb_on?cb=485b9fcaee6e0d0eefa559cab514727e) **Tip** Click the **Get Started** widget in the bottom-right corner of any Golive page to access the setup guide at any time. *** ** * ** *** ## Steps to Build the Environment Inventory ### Step 1: Set up Applications **Applications**represent the business systems or services you want to track. They are the anchor for everything else in Golive. Applications can connect to Jira Versions, define deployments, and include multiple tiers when your system is structured that way. For instructions, refer to the [Manage Applications](https://golive.apwide.com/doc/latest/cloud/applications.md) article. ### Step 2: Set up Environment Categories **Categories** describe the purpose of an Environment, such as *Development, Testing, Staging,* or *Production*. They give context to your Environments and help teams understand how each one is meant to be used. For instructions, refer to the [Environment Categories](https://golive.apwide.com/doc/latest/cloud/environment-categories.md) article. ### Step 3: Define Environment Attributes **Attributes** store additional information about your Environments --- such as URLs, owners, database versions, or other custom details. They ensure every Environment follows a consistent structure and provides the context your teams need. For instructions, refer to the [Environment Attributes](https://golive.apwide.com/doc/latest/cloud/customize-environment-attributes.md) article. ### Step 4: Create Environments and Environment Landscapes **Environments** are the actual instances where your applications live. Each Environment is tied to an application and category, and enriched with attributes. **Environment Landscapes** extend this concept: they represent multi-tier setups, grouping related Environments together under a single structure. For instructions, refer to the [Create Environments](https://golive.apwide.com/doc/latest/cloud/create-environments.md) and [Create Environment Landscapes](https://golive.apwide.com/doc/latest/cloud/create-environment-landscapes.md) articles. ### Step 5: Add Environment Dependencies Dependencies capture the relationships between Environments. They show when one system relies on another, making it easier to coordinate changes, reduce risks, and understand the impact across teams. For instructions, refer to the [Environment Dependencies](https://golive.apwide.com/doc/latest/cloud/environment-dependencies.md) article. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Calendar A **Calendar** functions as a repository for events, offering flexibility in customizing its *name* , *color* , and *permissions* . Each **Calendar Type** also provides additional settings, allowing you to further customize how events are retrieved and displayed. --- version: "latest" variant: "Golive Cloud" language: "en" --- # Calendar & Events Learn how to use and work with Calendars and Events in a Timeline. * [Create Events in the Timeline](https://golive.apwide.com/doc/latest/cloud/create-events-in-the-timeline.md) [Calendar \& Event Types](https://golive.apwide.com/doc/latest/cloud/calendars-events.md) * [Reschedule an Event](https://golive.apwide.com/doc/latest/cloud/reschedule-an-event.md) * [Customize Displayed Event Information](https://golive.apwide.com/doc/latest/cloud/customize-displayed-event-information.md) * [Filter Events](https://golive.apwide.com/doc/latest/cloud/filter-events.md) * [Share a Calendar](https://golive.apwide.com/doc/latest/cloud/share-a-calendar.md) * [Set Calendar Permissions](https://golive.apwide.com/doc/latest/cloud/set-calendar-permissions.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Calendar Swimlanes **Calendar Swimlanes** organize events by **Calendar Type** , improving event readability and Timeline management. For more information on Swimlanes, refer to the [Work with Swimlanes](https://golive.apwide.com/doc/latest/cloud/working-with-swimlanes.md) documentation. ![image-20251204-210411.png](https://golive.apwide.com/__attachments/a_bc744b9e3e33256d28f0b01b1edc85f9f8f3800a6cc4d19ca49155b9f383f18c/image-20251204-210411.png?cb=0bd43418815619ccdf63657de9edfe49) Timeline using the Calendar Swimlanes *** ** * ** *** ## Using Calendar Swimlanes ### Reordering You can rearrange Calendars and Calendar Swimlanes using drag-and-drop functionality to customize the event display. **Important** To reorder Calendars and Calendar Swimlanes, enter Edit mode by selecting the **Edit** button. This function is only available to **Golive Administrators** or **Timeline Owners**. ### Vertical Orientation Option For increased horizontal space and enhanced visibility, enable the **Vertical Orientation** option. This setting can display more events across the timeline. ![image-20251204-210603.png](https://golive.apwide.com/__attachments/a_fb06142eef1951ad0ee0f6f1a12a60436f9a3b7f6c8acd332c471aa8887960c8/image-20251204-210603.png?cb=99af92d76db2fbef6f281c0799f98ccc) Vertical Orientation Option --- version: "latest" variant: "Golive Cloud" language: "en" --- # Calendar & Event Types *** ** * ** *** Learn more about the different types of events and calendars your can use: * [Deployment Logs Calendar](https://golive.apwide.com/doc/latest/cloud/deployments.md) * [Jira Issues Calendar](https://golive.apwide.com/doc/latest/cloud/issues.md) * [Scheduled Events Calendar](https://golive.apwide.com/doc/latest/cloud/scheduled-events.md) * [Scheduling Calendar](https://golive.apwide.com/doc/latest/cloud/scheduling-calendar.md) * [Status Change Logs Calendar](https://golive.apwide.com/doc/latest/cloud/status-changes.md) * [Jira Versions Calendar](https://golive.apwide.com/doc/latest/cloud/versions.md) *** ** * ** *** --- version: "latest" variant: "Golive Cloud" language: "en" --- # Category Custom Fields **Category Custom Fields** are used to link **Jira work items** and **Service Management Requests** with Golive Categories. This article explains why to use them, how to create them, and how to configure and use them. *** ** * ** *** ## Why Use Category Custom Fields Category Custom Fields allow teams to associate Jira work items with Golive Categories. This helps you track [accurate statistics](https://golive.apwide.com/doc/latest/cloud/gadgets.md), such as the number of work items created, reproduced, or tested for specific Environment Categories. **Info** **Category Custom Fields** work similar to the **Version** concept in Jira. Like Versions, where multiple fields (e.g., Fix Version/s and Affects Version/s) use the same inventory, Category Custom Fields draw from a single list of Categories but can appear in multiple fields on the same issue. *** ** * ** *** ## Create a Category Custom Field ### Requirements You must have the **Jira Administrator** permission to create new custom fields from the **Fields** section. ### Steps 1. On the Jira **Fields** page, click **Create new field**. 2. In the **Field type** field, select **Apwide Golive Category**. 3. In the **Name** field, type the name of your new custom field, for instance "Category". 4. Click **Create**. ![image-20260624-180833.png](https://golive.apwide.com/__attachments/a_ac64cc0f097dda04e2fb3c54714d661e5b1a42888854b17a59363da0f483e636/image-20260624-180833.png?cb=888dba231cf9986f124132b6e0e29441) Create a Category custom field To make the **Custom Field** visible in work types, add it to your screens: * For **company-managed projects** , refer to: [Add a custom field to a screen](https://confluence.atlassian.com/adminjiracloud/add-a-custom-field-to-a-screen-991923749.html). * For **team-managed projects** , refer to: [Add a custom field to a team-managed project](https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/). *** ** * ** *** ## Update the Configuration of a Field By default, all categories can be added to your Category Custom Fields. You can restrict to a maximum number of categories if needed. ### Requirements You must be a **Jira Administrator**. ### Steps 1. On the Jira **Fields** page, search for the field you want to configure. 2. Next to the field, open the three-dots menu and click on **Contexts and default values**. 3. For the relevant context, click **Edit custom field config**. ![image-20260624-181209.png](https://golive.apwide.com/__attachments/a_bd055f3c86e78f23096142e929d61cc042f86a5dab5f9c19d7af1c1589fe6aee/image-20260624-181209.png?cb=87ac2bc7dfbe13866f6bb7c5da05be8f) Edit custom field configuration ![image-20260624-181114.png](https://golive.apwide.com/__attachments/a_e7ab23ae04c2e9f54250f7de562eb4b7015bdeb71798ed4e1badee565160138a/image-20260624-181114.png?cb=ec16775481cc18677b15941d55869351) Category custom field configuration *** ** * ** *** ## Select Categories on the Issue Screen Once you've configured a **Category Custom Field** and added it to a screen, you can easily select Categories directly from your work item in Jira. ### Steps 1. Open the **Jira work item**you want to edit. 2. Locate the **Category field**. 3. Search for and select one or more **Categories**. **Tip** To remove a Category, click the **x**icon next to it. ![image-20260624-181436.png](https://golive.apwide.com/__attachments/a_e05048bbdfd79e05387f16f3e7cf913e7e75d2c4162076a18c17d14b176ba30a/image-20260624-181436.png?cb=e35e59376d0e1254efdd556cd7377cea) Category custom field edition *** ** * ** *** ## Automation To update Golive custom fields automatically, refer to our [Jira Automation examples](https://golive.apwide.com/doc/latest/cloud/automation-for-jira.md) and our [Rest API documentation](https://golive.apwide.com/doc/latest/cloud/rest-api.md#Jira-Cloud-REST-API). --- version: "latest" variant: "Golive Cloud" language: "en" --- # Communication Enable real-time updates through Microsoft Teams, Slack, or email notifications based on the changes in the Environments you're monitoring with Jira and Golive. Not only does this keep you promptly informed, but it also allows for swift action when necessary. You can tailor these notifications to suit more complex needs and specific use cases. Discover how to make the most of your Jira and Golive experience by integrating with the most popular collaboration platforms: * [Send MS Teams Notifications](https://golive.apwide.com/doc/latest/cloud/ms-teams.md) * [Send Slack Messages](https://golive.apwide.com/doc/latest/cloud/slack.md) * [Send Custom Emails](https://golive.apwide.com/doc/latest/cloud/custom-emails.md) --- version: "latest" variant: "Golive Cloud" language: "en" --- # Configuration Gap A **Configuration Gap**is a mismatch between what's required for a setup and what's actually available. Examples include: * Testing a newer version (2.0) in an environment set up for an older one (1.1). * Not being able to recreate a problem in the testing environment because it doesn't match the production setup. * Booking a training environment that's unstable or slow. The impact of these gaps can vary depending on the context and the environments involved. In production settings, such gaps are often treated as Incidents. [Next Page](https://golive.apwide.com/llms-full.txt/1)