diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/_category_.json b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/_category_.json new file mode 100644 index 0000000000..0523872d9e --- /dev/null +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/_category_.json @@ -0,0 +1,11 @@ +{ + "label": "Jira Forge", + "position": 10, + "collapsed": true, + "collapsible": true, + "link": { + "type": "doc", + "id": "jira_forge_integration" + } +} + diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md new file mode 100644 index 0000000000..16504ebd99 --- /dev/null +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq.md @@ -0,0 +1,26 @@ +--- +title: "Jira Forge FAQs and Basic Troubleshooting" +description: "Jira Forge FAQs and Basic Troubleshooting" +sidebar_position: 4 +--- + +# Jira Forge FAQs and Basic Troubleshooting + +This section will discuss frequently asked questions and basic troubleshooting for Platform Governance's Jira Forge app. + +1. I already have Strongpoint Connect app installed in my instance. Is it okay to install the Forge app as well? + - **Yes**, it is perfectly okay to install the Forge app even though you currently have the Connect app. They should not cause any conflicts during installation and during using either one of them or both of them at the same time. + +2. What will happen to the data in Netwrix Settings page in Connect app once I have installed the Forge app? + - Data in the Netwrix Settings page in Connect app does not get migrated to the Netwrix NetSuite Settings page in the Forge app. Since these are 2 different implementation/apps, you will have to manually migrate the Connect app data to Forge app. + +3. Is it normal that I see two (2), Netwrix NetSuite tabs in my issues panel if my instance has both Connect and Forge apps? + - **Yes**, it is normal. Two (2) separate apps have separate file descriptors that show separate tabs in the issue panel. + +4. Why did all my data in Netwrix NetSuite Settings page in Forge app disappear when I updated to a new version? + - This is Atlassian's way of securing your data, every install or update is a fresh start. However, there are 2 ways to retrieve your data: (1) You will have to raise a ticket to Atlassian support to restore the data in your instance when the Jira Forge app was installed or updated. (2) You can manually input them back yourself. + +5. Is there impact to existing connect tickets if forge is being used? + - **No**. Since the change request information is being pulled from the NetSuite account that Jira Forge is currently connected to, there should be no impact when switching to the Forge app. + +**Back to:** [Jira Forge Walkthrough Example](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md new file mode 100644 index 0000000000..275b7ec159 --- /dev/null +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_integration.md @@ -0,0 +1,50 @@ +--- +title: "Jira Forge" +description: "Jira Forge" +sidebar_position: 1 +--- + +# Jira Forge + +Platform Governance for NetSuite's Change Management capabilities are integrated with Jira, one of the most popular issue ticketing and development project management systems. Customers are able to look for and include NetSuite Customizations, assess impacts for requested changes, and push Jira change tickets into a Change Request. This enables easy management of changes, seamless tracking of compliant changes and automating the reconciliation of change logs during an audit. + +## Integration Overview + +- Features and Benefits +- Technical Considerations +- Set Up the Integration + +### Features and Benefits + +With Platform Governance for NetSuite's integration of NetSuite and Jira (Cloud), you can use the Jira tool while we automatically add and track the associated changes in your NetSuite account. The integration eliminates the need for double entry in the two systems. + +Jira Integration uses the latest Atlassian Forge implementation which provides enhanced security, ensuring data does not leave the ecosystem and adheres to strict security standards (SOC2, ISO/IEC 27001). + +The Jira Forge integration automatically syncs Jira tickets with a NetSuite change request: + +- Creates a corresponding Change Request when a Jira ticket is generated. +- Updates NetSuite with the corresponding customizations. +- Sets the Change Request status according to its corresponding Jira ticket status. + +Change Managers and System Administrators quickly realize the integration benefits: + +- Uses Jira to organize and track the development process. +- Maintains data integrity within Jira and NetSuite. +- Streamlines processes for updating daily activities and tasks. +- Reduces turnaround time for change deployments. +- Eliminates waiting for others to transition a change request status. +- Enables creating a change request to a target NetSuite account. + +### Technical Considerations + +Review these considerations prior to deploying the Jira integration: + +1. Platform Governance for NetSuite integration is implemented as a Forge app. It can be enabled or disabled based on configuration and runs independently of other scripts, ensuring it does not interfere with existing processes. +2. All functions are self-executing, complying with Atlassian Jira Forge's best practices. +3. No DOM manipulation or global scripts are deployed. +4. No external libraries are needed. It is plain JavaScript. +5. No direct or custom database access is required. Data resides either in the Atlassian instance or the connected NetSuite account. +6. NetSuite connections use the REST Atlassian Jira Forge's interface, executing on the client side to prevent server load. + + +**Next Step:** [Jira Forge Set Up](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md new file mode 100644 index 0000000000..79815682fc --- /dev/null +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up.md @@ -0,0 +1,219 @@ +--- +title: "Jira Forge Set Up" +description: "Jira Forge Set Up" +sidebar_position: 2 +--- + +# Jira Forge Set Up + +The steps below show detailed instructions and prerequisites on how to set up Platform Governance Jira Integration. + +## Prerequisites + +- Install the latest Netwrix Platform Governance(Strongpoint) bundle +- Install the latest Netwrix Platform Governance Jira bundle +- Install the latest version of the Netwrix Platform Governance Jira Forge app +- Set up NetSuite Token-based Authentication Credentials +- Set up Jira Credentials +- Set up Jira Status Mapping +- Set up Jira Project Keys +- Set up Jira TBA Credentials + +### Install the latest Netwrix Platform Governance(Strongpoint) bundle + +Netwrix Platform Governance(Strongpoint) bundle is a key prerequisite for Jira Forge to work. It is required that your NetSuite account is installed with the latest version or at least **7.7.5** or above. + +For installation details you may refer to the installation guide found in [Installing Platform Governance for NetSuite](/docs/platgovnetsuite/installation/installing_strongpoint). + +#### NOTE: +If the latest version of the bundle is already installed, you may skip this part. + +### Install the latest Netwrix Platform Governance Jira bundle + +This step will require a user to have NetSuite account access and an Administrator role for that account. This bundle must be version **2.0** or higher to work properly. The Netwrix Platform Governance Jira bundle is a non-managed bundle, please check the [Community](https://community.netwrix.com/c/products/platform-governance-netsuite/181) regularly for the latest updates and announcements. + +#### NOTE: +If the latest version of the bundle is already installed, you may skip this part. + +1. Log in to the NetSuite account and navigate to Search & Install Bundles page. + - In the Dashboard main menu: **Customization > SuiteBundler > Search & Install Bundles** +2. In the KEYWORDS field, search for **311231**. This is the bundle ID for Netwrix Platform Governance Jira bundle + + +![Jira Forge Bundle Search](/images/platgovnetsuite/integrations/jira_forge_jira_bundle_search.webp) + +3. Click on Netwrix Platform Governance Jira bundle in the search results. +4. Click Install when the Bundle Details opens. +5. Click Install Bundle on the Preview Bundle Install page. + +### Install the latest version of the Netwrix Platform Governance Jira Forge app + +This process requires access to the Atlassian Marketplace and Administrator permissions on the Jira instance where the app will be installed. + +1. Go to the [Atlassian Marketplace](https://marketplace.atlassian.com/). +2. In the search bar, type in either of the keywords: **Netwrix Platform Governance** or **Strongpoint**(this is the product's previous name). +3. You should see a number of products displayed, select **Netwrix NS Platform Governance (formerly Strongpoint)-Forge**. + + +![Jira Forge Marketplace Search](/images/platgovnetsuite/integrations/jira_forge_marketplace_search_results.webp) + +4. After selecting, you should be redirected to the product's overview page. + + +![Jira Forge Marketplace Overview](/images/platgovnetsuite/integrations/jira_forge_marketplace_overview.webp) + +5. Click the **Get it now** button found at the upper-right part of the page. +6. You will now be redirected to the installation process. Select the Jira instance where you want to install Netwrix Platform Governance Forge + + +![Jira Forge Marketplace Select Site](/images/platgovnetsuite/integrations/jira_forge_marketplace_select_site.webp) + +7. Click **Review** +8. You are now in the last step where you can review the app's Permissions and Data management. All of these have been strictly reviewed by the Atlassian team and adhere to their security policies. When ready, click **Get it now** button. + + +![Jira Forge Marketplace Review](/images/platgovnetsuite/integrations/jira_forge_marketplace_review_install.webp) + +### Set up NetSuite Token-based Authentication Credentials + +This step will require a user to have NetSuite account access and an Administrator role to that account. + +Token Based Authentication is set up through NetSuite. Here is the basic process: + +1. NetSuite Administrator creates an Integration Record for the Platform Governance for NetSuite application. This only needs to be performed once per account. Open **Setup > Integration > Integration Management > Manage Integrations > New**. For more information, refer to the NetSuite help article Create Integration Records for Applications to Use TBA. To view a list of integration records in this account, open **Setup > Integration > Integration Management > Manage Integrations**. + + #### NOTE: + Please take note and keep these values to yourself. + +2. Each user creates their token in NetSuite. Refer to the NetSuite help Manage TBA Tokens in the NetSuite UI for details. Once you have created your tokens, add them to Jira. +3. Create an Access Token by navigating to main menu, **Setup > Users/Roles > Access Tokens > New**. +4. Fill the fields with the following values: + - Application Name: The Integration Record that was created in Step 1. + - User: Select yourself (Employee Record). + - Role: STRONGPOINT DEVELOPER ROLE + - Token Name: ***Token name of your choice*** + - Skip checking Inactive checkbox +5. Click 'Save'. + + #### NOTE: + You can also create a Token Based Authentication for your NetSuite Administrator role. Follow the steps below: + 1. Login as an **Administrator** role in NetSuite. + 2. In your NetSuite account dashboard, navigate to the bottom left part of the page. Under **Settings**, you should see **Manage Access Tokens** and be able to click the link. + + + ![Jira Forge NetSuite Admin TBA](/images/platgovnetsuite/integrations/jira_forge_netsuite_tba_admin.webp) + + 3. You should be redirected to **My Access Tokens** page. Click the **New My Access Token** button, this allows you to create a TBA record for your Administrator role. + 4. Select an Application Name(Integration record) for this token. + 5. Click **Save**. + + **IMPORTANT:** Please take note and keep these values to yourself. + +### Set up Jira Credentials + +This step will require a user to have Jira instance access and a user to have NetSuite account access. + +1. Create a Jira token via this URL: https://id.atlassian.com/manage-profile/security/api-tokens + - Take note of the token value as this will be associated with your email address that is used to login to the Atlassian/Jira ecosystem. Refer to the Atlassian documentation to obtain a Token. +2. In this step, you should have the following credentials on hand + - Jira user email address + - Jira token generated above. +3. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. There should only be **ONE(1)** record displayed. Click 'Edit' and it should open the Configuration and Stats page. +4. Click 'Jira Integration' tab. You should be able to see a number of fields. Turn your attention to Jira User and Jira Token fields. +5. Populate these fields with the following values: + - Jira User - Jira user email address in step 2. + - Jira token - Jira token generated in step 1. +Click 'Save'. + +### Set up Jira Status Mapping + +To take advantage of the automatic synchronization feature, we recommend reviewing your Jira statuses to be mapped to the Change Management statuses. When a ticket status is updated to a mapped status, Platform Governance for NetSuite handles the synchronization between Jira and NetSuite. + +The mapping allows multiple Jira statuses to map to each Change Request status. The mapping is part of the Configure NetSuite and Jira procedure. + +Refer to the Atlassian documentation for instructions on +[Defining status field values](https://confluence.atlassian.com/adminjiraserver070/defining-status-field-values-749382903.html?_ga=2.262596428.1900070949.1572132057-2138500458.1540834491). + +1. In NetSuite, go to Netwrix Configuration and Stats by navigating in the main menu, **Netwrix > Netwrix Support > Installation Settings**. There should only be **ONE(1)** record displayed. Click 'Edit' and it should open the Configuration and Stats page. + +Enter the mappings between your Jira statuses and the Change Request statuses. For best practice, define your Jira statuses prior to this step. You can enter multiple Jira statuses for each Change Request status, separated by commas. For example, Ready for Deployment,Done. Assign your relevant mapping for each of the Change Request statuses: + +**Jira Statuses for In Progress Status** + +**Jira Statuses for Pending Approval Status** + +**Jira Statuses for Approved Status** + +**Jira Statuses for Complete Status** + +**Jira Statuses for Rejected Status** + +**Jira Statuses for Canceled Status** + +2. Check Automatic Synchronization to enable Platform Governance for NetSuite to handle the synchronization between Jira and NetSuite when a Ticket status is updated to a mapped status, without having to click Push. If you are using an account where you do not want to create a Change Request, leave this unchecked so you can do your research or testing without generating Change Requests. + +3. Check Allow NS to Jira Push to enable pushing NetSuite change requests into Jira. Otherwise, you can leave it as unchecked if you do not need to enable this feature. + +Click 'Save' + +### Set up Jira Project Keys + +This step will require a user to have Jira instance access where Netwrix Platform Governance for NetSuite Jira Forge app is installed. You are now closer to using the integration app. + +1. In your browser, open your Jira application. +2. In the left part of the page, there is a sidebar that lists shortcuts and apps that are installed in this Jira instance. Under 'Your Apps', there should be an app that is titled 'Netwrix NetSuite Settings'. Click it and it should display the Netwrix NetSuite Settings page. + + +![Jira Forge Netwrix NetSuite Settings Menu](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp) + +3. The page has 2 tabs, Netwrix NetSuite TBA Credentials and Netwrix NetSuite Project Keys. Let's focus on 'Netwrix NetSuite Project Keys' tab. Click the tab. + + +![Jira Forge Netwrix NetSuite Settings Project Keys](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_project_keys_menu.webp) + +4. 'New Project Key' button should be displayed. Click the button and a modal should pop-out for you to add a Project Key in the field. + - By defining a Project Key, the Platform Governance app can only be displayed and used within the project. + + +![Jira Forge Netwrix NetSuite Settings Project Keys Modal](/images/platgovnetsuite/integrations/jira_forge_project_key_modal.webp) + +5. Click 'Create' and the newly added/created project key should be listed in the page. + +### Set up Jira TBA Credentials + +This step will require a user to have Jira instance access where Netwrix Platform Governance for NetSuite Jira Forge app is installed. You are now closer to using the integration app. + +1. In your browser, open your Jira application. +2. In the left part of the page, there is a sidebar that lists shortcuts and apps that are installed in this Jira instance. Under 'Your Apps', there should be an app that is titled 'Netwrix NetSuite Settings'. Click it and it should display the Netwrix NetSuite Settings page. + + +![Jira Forge Netwrix NetSuite Settings Menu](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp) + +3. The page has 2 tabs, Netwrix NetSuite TBA Credentials and Netwrix NetSuite Project Keys. Let's focus on 'Netwrix NetSuite TBA Credentials' tab. Click the tab. + + +![Jira Forge Netwrix NetSuite Settings Menu TBA](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba.webp) + +4. 'New Token Based Authentication' button should be displayed. Click the button and a modal should pop-out for you to add a new TBA record to be used to connect to a NetSuite account. + + +![Jira Forge Netwrix NetSuite Settings Menu TBA Modal](/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba_modal.webp) + + - Populate the fields. + - A 'Test Connection' button (yellow) can be found inside the modal, this button is used to test or check if the credentials and account you have are valid. + + +![Jira Forge Netwrix NetSuite Settings TBA Test Connection](/images/platgovnetsuite/integrations/jira_forge_tba_test_connection_successful.webp) + +5. Click 'Create' and the newly added/created TBA record should be listed in the page. + +Additionally, 'Update' and 'Delete' buttons are found on the right part of your record. These buttons allow you to update or delete the record, respectively. + + +![Jira Forge Netwrix NetSuite Settings TBA List](/images/platgovnetsuite/integrations/jira_forge_tba_list.webp) + +If you have followed the step by step guide in this page, you are good to go and are ready to use the integration app. + +The next page, Jira Forge Walkthrough will show you how the app works! + +**Next Step:** [Jira Forge Walkthrough Example](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough) diff --git a/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md new file mode 100644 index 0000000000..a521ab1e06 --- /dev/null +++ b/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_walkthrough.md @@ -0,0 +1,330 @@ +--- +title: "Jira Forge Walkthrough" +description: "Jira Forge Walkthrough" +sidebar_position: 3 +--- + +# Jira Forge Walkthrough + +If you have reached this part it means that you have completed ALL prerequisites found in the Jira Forge Setup page. If NOT, please go through the setup steps for a smooth walkthrough of the integration's features. + +This walkthrough is one example based on our test account. You must install and configure the Jira integration, including setting up the Jira Statuses prior to using this walkthrough. + +### The walkthrough demonstrates these steps: + +- Create a Jira Ticket +- Logging In and Connecting to a NetSuite Account +- Add or Remove Customizations +- Importing Customizations +- Perform Risk Assessment +- View Entity Relation Diagram +- Ready for Development +- Deploy Changes and Complete the Ticket +- Other notable features + +### Create a Jira Ticket +1. Login to your Jira account. +2. Open a Project. +3. Click Create (+). +4. Fill the necessary fields and Click 'Create' + +### Logging In and Connecting to a NetSuite Account +Before proceeding to this step, make sure you already have created a TBA record. If not please see [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. + +1. In your issue ticket, you should see the 'Netwrix NetSuite Forge' tab in the issues tab. Click the tab. + Two possible displays: + + 1. If you have NOT executed [Set up Jira Project Keys](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-project-keys) in the Setup Page, you will see this message displayed "Only projects defined in the Netwrix Settings page can use this integration". Please check if you have done that part. + + + ![Jira Forge Issue No Project Key](/images/platgovnetsuite/integrations/jira_forge_issue_no_project_key.webp) + + 2. If you have, you should see the connect page where you can connect or log in to a NetSuite defined in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. + + + ![Jira Forge Issue Connect Form](/images/platgovnetsuite/integrations/jira_forge_issue_connect_form.webp) + +2. If you are seeing the connect fields, you are in the right track. Please select a NetSuite account to connect to. +3. Upon selecting an account, the app loads. It is establishing the initial connection process. Once it is successful, the "Connect" button below should be enabled. Otherwise, please double check the TBA credentials that you have entered in [Set up Jira TBA Credentials](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_set_up#set-up-jira-tba-credentials) in Setup page. + + +![Jira Forge Issue Connect Form Successful](/images/platgovnetsuite/integrations/jira_forge_issue_connect_form_successful.webp) + +4. Click "Connect" button. +5. You should see the ITGC Form for our Jira app. Change Request data is loaded, it also shows which account where you are currently connected. + + +![Jira Forge Issue Connect Form Successful ITGC](/images/platgovnetsuite/integrations/jira_forge_connect_itgc_form.webp) + +### Add or Remove Customizations + +Now that you are ready to attach customizations to your Jira ticket. This section shows you how to add and/or remove customizations in the Forge app. + +To start adding or removing customizations, follow the steps below: + +1. In the form, there should be a button named "Lookup Customization". This allows the user to add existing customization to the Jira ticket. Click the button. A modal should appear. This allows the user to filter and select a customization to attach to the change request. + + +Available filters: +- Name +- Script ID +- Type +- Bundle ID +- Modified By +- From +- To + + +![Jira Forge Lookup Customization Modal](/images/platgovnetsuite/integrations/jira_forge_lookup_customization_modal.webp) + +2. Choose a filter to narrow down the selection of customizations. In this case, we will use the Name filter. Click the "Lookup" button. + + +![Jira Forge Lookup Customization Modal Name Filter](/images/platgovnetsuite/integrations/jira_forge_lookup_name_filter.webp) + +3. Select a customization to attach by ticking the checkbox beside the name. Once ticked, click the "Add Customizations" button at the bottom part of the modal. + - Below shows a flag with a message that the action is in progress. + + + ![Jira Forge Add Customization Flag In Progress](/images/platgovnetsuite/integrations/jira_forge_add_customization_in_progress.webp) + + - Below shows a flag with a message that the action is successful. + + + ![Jira Forge Add Customization Flag In Progress](/images/platgovnetsuite/integrations/jira_forge_successful_add_customization.webp) + +4. You can also add customization that is yet to be created. This is what the "Proposed Customization" button is for. To add one, click the "Proposed Customization" button. A modal should appear with the following fields: + - Type + - ScriptID/Name + + + ![Jira Forge Proposed Customization Modal](/images/platgovnetsuite/integrations/jira_forge_proposed_customization_modal.webp) + +5. Select the Type for your proposed customization. In this case, we will select "Body Field" type. Notice that the Script ID/Name field is prepopulated with the prefix of the script ID, this allows the user ease of use and not mistakenly input the wrong script ID prefix for the type. Type the script ID of your choice. + + + ![Jira Forge Proposed Customization Input](/images/platgovnetsuite/integrations/jira_forge_add_proposed_wth_input.webp) +6. Click the "Add Proposed Customization" button to add/attach it to the Jira ticket change request. + - Below shows a flag with a message that the action is in progress. + + + ![Jira Forge Proposed Customization Flag In Progress](/images/platgovnetsuite/integrations/jira_forge_add_proposed_in_progress.webp) + + - Below shows a flag with a message that the action is successful. + + + ![Jira Forge Proposed Customization Flag Successful](/images/platgovnetsuite/integrations/jira_forge_add_proposed_successful.webp) + +Below shows the existing and proposed customizations that were added in steps 1 through 6. + + +![Jira Forge Existing and Proposed Customizations](/images/platgovnetsuite/integrations/jira_forge_existing_and_proposed_customizations_added.webp) + +7. Just as you can add existing and/or proposed customizations, you can also remove them from the Jira ticket change request. Simply click the "trash" icon located at the right side of the customization's name and will trigger the remove process. + + +![Jira Forge Remove Customizations Icon](/images/platgovnetsuite/integrations/jira_forge_remove_trash_icon.webp) + + - Below shows a flag with a message that the action is in progress. + + + ![Jira Forge Remove Customizations Flag In Progress](/images/platgovnetsuite/integrations/jira_forge_remove_customization_in_progress.webp) + + - Below shows a flag with a message that the action is successful. + + + ![Jira Forge Remove Customizations Flag Success](/images/platgovnetsuite/integrations/jira_forge_remove_customization_successful.webp) + +If you have reached this section, you were able to execute the following: +- Use the Lookup customization filter +- Add existing and proposed customizations +- Delete/remove a customization + +### Importing Customizations + +This feature is similar to the add customization process, the key difference is that the user can add customizations in bulk. Import customization only allows the user to upload files in XML and a SDF project in ZIP formats. + +You may contact your company's NetSuite Administrator for a sample of this files. + +To use import feature follow the steps below: + +1. Click the "Import Customization" button in the form. A modal will appear with the option to upload a file. As discussed above, only a SDF project in ZIP and XML file formats are accepted. + + +![Jira Forge Import Customization](/images/platgovnetsuite/integrations/jira_forge_import_customization_modal.webp) + +2. Select a file to import. +- Importing XML file format + + +![Jira Forge Import Customization](/images/platgovnetsuite/integrations/jira_forge_import_xml_file.webp) + +- Importing SDF ZIP file format + + +![Jira Forge Import Customization](/images/platgovnetsuite/integrations/jira_forge_import_sdf_zip.webp) + +3. Click the "Import Customizations" button. You will see a flag message at the lower left side of your screen indicating that the importing process is In Progress. + +4. Once the importing is successful, all valid objects will populate the Customization and Proposed Customization tables accordingly. You will also see a flag message indicating the importing process is successful. + +If you have reached this section, you were able to execute the following: +- Use the Import Customization feature and add customizations in bulk. + +### Perform Risk Assessment + +This feature will show you Platform Governance's Impact Analysis tool. This tool reviews your customizations for dependencies or risks. + +To use Impact Analysis follow the steps below: + +1. Click the "Impact Analysis" button located at the bottom left section of the form. + + +![Jira Forge Impact Analysis Button](/images/platgovnetsuite/integrations/jira_forge_impact_analysis_button.webp) +2. A modal will appear to start the risk assessment process. + + +![Jira Forge Impact Analysis Calculating](/images/platgovnetsuite/integrations/jira_forge_calculating_impact_analysis.webp) + +3. The modal populates with objects that are impacted. They are categorized as **Can Be Safely Deleted or Modified**, **Cannot Be Safely Deleted or Modified** and **Inactive Customizations (Already Deleted)**. Objects under the **Cannot Be Safely Deleted or Modified** will also show the Impacted Customizations. + + +![Jira Forge Impact Analysis Data](/images/platgovnetsuite/integrations/jira_forge_impact_analysis.webp) + +If you have reached this section, you were able to execute the following: +- Perform an impact analysis on the customization that are add/attached to the Jira ticket change request. + +### View Entity Relation Diagram + +The Entity Relationship Diagram (ERD) tool graphically displays your Customizations and all dependencies. + +To use ERD follow the steps below: + +1. Click the "View ERD" button located at the bottom left section of the form just beside the "Impact Analysis" button. + + +![Jira Forge View ERD Button](/images/platgovnetsuite/integrations/jira_forge_view_erd_button.webp) + +2. A modal will appear to start pulling ERD data. + + +![Jira Forge Pulling ERD Data](/images/platgovnetsuite/integrations/jira_forge_pulling_erd_data.webp) + +3. The modal populates with the customization and its corresponding hyperlink to the ERD. + + +![Jira Forge ERD Data](/images/platgovnetsuite/integrations/jira_forge_list_erd_data.webp) + +4. Click "View ERD" link to view the customization's ERD. It will open to a new tab within the same browser. + + +![Jira Forge ERD Data NetSuite](/images/platgovnetsuite/integrations/jira_forge_sample_erd.webp) + +If you have reached this section, you were able to execute the following: +- View the entity relation diagram of the customization that is add/attached to the Jira ticket change request. + +### Ready for Development + +Once you have resolved any risk or conflicts, your changes are ready for development: + +1. Change the Jira status of your ticket to match the status set up for Jira Statuses for Pending Approval Status. For example, Selected for Development. + +2. Click Push if you are not using Automatic Synchronization to push status changes. A confirmation your Change Request was Created/Updated is displayed. + +- Below shows the "Push" button. + + +![Jira Forge Push Button](/images/platgovnetsuite/integrations/jira_forge_push_button.webp) + +- Below shows a flag with a message that the action is in progress. + + +![Jira Forge Push In Prgoress](/images/platgovnetsuite/integrations/jira_forge_push_in_progress.webp) + +- Below shows a flag with a message that the action is successful. + + +![Jira Forge Push Successful](/images/platgovnetsuite/integrations/jira_forge_push_successful.webp) + +3. The Change Request Status field on the form will show the change request status in NetSuite. The status is now Pending Approval. It is also link to open the Change Request in NetSuite. + + +![Jira Forge Change Request Pending Approval](/images/platgovnetsuite/integrations/jira_forge_change_request_pending_approval_status.webp) + +If you have reached this section, you were able to execute the following: +- Push a change request from a Jira ticket. +- See the change request status from Jira. + +### Deploy Changes and Complete the Ticket + +When development is done, and the Change Request is approved according to your policy, the Jira ticket is ready to be updated. + +1. The Change Request Status field on the form will show the change request status in NetSuite. The status is now Approved, this means the change request is now approved in NetSuite. + + +![Jira Forge Change Request Approved](/images/platgovnetsuite/integrations/jira_forge_approved_cr_status.webp) + +2. Change the Jira status of your ticket to match the status set up for Jira Statuses for Approved Status. In our example set up, we have two possible statuses: Ready for Deployment and Done. Setting up two statuses enables you to split up the deployment and the ticket closure if you want to monitor the deployment task separately. Both statuses are valid for Deployment, but only Done closes the Jira ticket and updates the Change Request to Completed. + +3. Click Push if you are not using Automatic Synchronization to push status changes. A confirmation your Change Request was Created/Updated is displayed. +- Below shows a flag with a message that the action is in progress. + + +![Jira Forge Change Request Approved Flag In Progress](/images/platgovnetsuite/integrations/jira_forge_push_in_progress.webp) + +- Below shows a flag with a message that the action is successful. + + +![Jira Forge Change Request Approved Flag Sucessful](/images/platgovnetsuite/integrations/jira_forge_push_successful.webp) + +4. If you used Ready for Deployment, update your Jira status to Done once your deployment and verification activities are complete. + +If you have reached this section, you were able to execute the following: +- Push a change request from a Jira ticket. +- See the Approved change request status from Jira. + +#### If you open the Change Request in NetSuite: + +- All Customizations added from Jira are displayed. +- Affected Bundle ID is added (if used). +- Change Overview is set to the Jira ticket description. +- Change Request is Approved and ready to be deployed. + + +![Jira Forge Change Request NetSuite 1](/images/platgovnetsuite/integrations/jira_forge_itgc_cr_1.webp) +- Originated System, External Change Request Number and External Link to the Jira ticket are populated on the Related Change Records tab. + + +![Jira Forge Change Request NetSuite 2](/images/platgovnetsuite/integrations/jira_forge_itgc_cr_2.webp) +- If the Jira status is Done, the Change Request shows as Completed. + +### Other notable features + +These are the other features whose actions are not that commonly used but are of equal importance in the integration app. + +1. **Add Bundle ID** - The **+** button beside the Affected Bundle ID field. User will be able to add NetSuite bundle IDs to the change request. You can add one bundle ID at a time for this action. It is only an add functionality, removing a bundle ID in the change request would require the user to contact a NetSuite Administrator or user for this action. + + +![Jira Forge Add Bundle Button](/images/platgovnetsuite/integrations/jira_forge_add_bundle_button.webp) + + + +![Jira Forge Add Bundle Modal](/images/platgovnetsuite/integrations/jira_forge_add_bundle_modal.webp) + +2. **Push External** - This feature allows the user to "push" the Jira ticket change request and its objects to an external NetSuite account. Pushing to an external NetSuite account save the user's time in creating a change request with the same objects in another NetSuite account. Push external can be executed by clicking the "Push External" button, a modal will appear prompting the user to select a NetSuite account that he/she wishes to push the Jira ticket change request. NetSuite accounts in the modal selection are the same accounts defined by the user in Netwrix NetSuite TBA Credentials page. + + +![Jira Forge Push External Button](/images/platgovnetsuite/integrations/jira_forge_push_external_button.webp) + + + +![Jira Forge Push External Modal](/images/platgovnetsuite/integrations/jira_forge_push_external_modal.webp) + +3. **Settings** - The Settings is a drop-down button, allows the user to switch NetSuite accounts to connect to. When "Settings" button is clicked, a "Change Account" option is shown. When the user clicks "Change Account", the session is disconnected and the connection to a NetSuite account stopped. The connection form is then shown to allow the user to connect to another NetSuite account. + + +![Jira Forge Settings Button](/images/platgovnetsuite/integrations/jira_forge_settings_change_account.webp) + +You have successfully finished the step by step Jira Forge Walkthrough! + +**Next Step:** [Jira Forge FAQs](/docs/platgovnetsuite/ticketingintegrations/jiraforgeintegration/jira_forge_faq) diff --git a/static/images/platgovnetsuite/integrations/jira_forge_add_bundle_button.webp b/static/images/platgovnetsuite/integrations/jira_forge_add_bundle_button.webp new file mode 100644 index 0000000000..9bd48aebd1 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_add_bundle_button.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_add_bundle_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_add_bundle_modal.webp new file mode 100644 index 0000000000..f29e4c5e3b Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_add_bundle_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_add_customization_in_progress.webp b/static/images/platgovnetsuite/integrations/jira_forge_add_customization_in_progress.webp new file mode 100644 index 0000000000..fedcd62448 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_add_customization_in_progress.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_in_progress.webp b/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_in_progress.webp new file mode 100644 index 0000000000..9a79faa7cb Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_in_progress.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_successful.webp b/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_successful.webp new file mode 100644 index 0000000000..12fd397a4c Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_successful.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_wth_input.webp b/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_wth_input.webp new file mode 100644 index 0000000000..e9925e3622 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_add_proposed_wth_input.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_approved_cr_status.webp b/static/images/platgovnetsuite/integrations/jira_forge_approved_cr_status.webp new file mode 100644 index 0000000000..e24e1bbeed Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_approved_cr_status.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_calculating_impact_analysis.webp b/static/images/platgovnetsuite/integrations/jira_forge_calculating_impact_analysis.webp new file mode 100644 index 0000000000..42b08574da Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_calculating_impact_analysis.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_change_request_pending_approval_status.webp b/static/images/platgovnetsuite/integrations/jira_forge_change_request_pending_approval_status.webp new file mode 100644 index 0000000000..85ff66c9b5 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_change_request_pending_approval_status.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_connect_itgc_form.webp b/static/images/platgovnetsuite/integrations/jira_forge_connect_itgc_form.webp new file mode 100644 index 0000000000..2017801a25 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_connect_itgc_form.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_existing_and_proposed_customizations_added.webp b/static/images/platgovnetsuite/integrations/jira_forge_existing_and_proposed_customizations_added.webp new file mode 100644 index 0000000000..f322681ae5 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_existing_and_proposed_customizations_added.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_impact_analysis.webp b/static/images/platgovnetsuite/integrations/jira_forge_impact_analysis.webp new file mode 100644 index 0000000000..64d37e4d44 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_impact_analysis.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_impact_analysis_button.webp b/static/images/platgovnetsuite/integrations/jira_forge_impact_analysis_button.webp new file mode 100644 index 0000000000..53abc578b7 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_impact_analysis_button.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_import_customization_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_import_customization_modal.webp new file mode 100644 index 0000000000..1daa6de70b Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_import_customization_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_import_sdf_zip.webp b/static/images/platgovnetsuite/integrations/jira_forge_import_sdf_zip.webp new file mode 100644 index 0000000000..ac80ba3e37 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_import_sdf_zip.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_import_xml_file.webp b/static/images/platgovnetsuite/integrations/jira_forge_import_xml_file.webp new file mode 100644 index 0000000000..753bd700f5 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_import_xml_file.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_issue_connect_form.webp b/static/images/platgovnetsuite/integrations/jira_forge_issue_connect_form.webp new file mode 100644 index 0000000000..d7567db77c Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_issue_connect_form.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_issue_connect_form_successful.webp b/static/images/platgovnetsuite/integrations/jira_forge_issue_connect_form_successful.webp new file mode 100644 index 0000000000..9610944fad Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_issue_connect_form_successful.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_issue_no_project_key.webp b/static/images/platgovnetsuite/integrations/jira_forge_issue_no_project_key.webp new file mode 100644 index 0000000000..2d4c7686f7 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_issue_no_project_key.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_itgc_cr_1.webp b/static/images/platgovnetsuite/integrations/jira_forge_itgc_cr_1.webp new file mode 100644 index 0000000000..984cf370b2 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_itgc_cr_1.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_itgc_cr_2.webp b/static/images/platgovnetsuite/integrations/jira_forge_itgc_cr_2.webp new file mode 100644 index 0000000000..fe92c5eae7 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_itgc_cr_2.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_jira_bundle_search.webp b/static/images/platgovnetsuite/integrations/jira_forge_jira_bundle_search.webp new file mode 100644 index 0000000000..fbf0893938 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_jira_bundle_search.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_list_erd_data.webp b/static/images/platgovnetsuite/integrations/jira_forge_list_erd_data.webp new file mode 100644 index 0000000000..1a96d1643d Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_list_erd_data.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_lookup_customization_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_lookup_customization_modal.webp new file mode 100644 index 0000000000..84bd8ff765 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_lookup_customization_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_lookup_name_filter.webp b/static/images/platgovnetsuite/integrations/jira_forge_lookup_name_filter.webp new file mode 100644 index 0000000000..35f6d8aa90 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_lookup_name_filter.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_marketplace_overview.webp b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_overview.webp new file mode 100644 index 0000000000..742a680179 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_overview.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_marketplace_review_install.webp b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_review_install.webp new file mode 100644 index 0000000000..540a00baaa Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_review_install.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_marketplace_search_results.webp b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_search_results.webp new file mode 100644 index 0000000000..9938fbc3c4 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_search_results.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_marketplace_select_site.webp b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_select_site.webp new file mode 100644 index 0000000000..14c4ee99e9 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_marketplace_select_site.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_netsuite_tba_admin.webp b/static/images/platgovnetsuite/integrations/jira_forge_netsuite_tba_admin.webp new file mode 100644 index 0000000000..a836e80152 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_netsuite_tba_admin.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_project_keys_menu.webp b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_project_keys_menu.webp new file mode 100644 index 0000000000..065bc61998 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_project_keys_menu.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp new file mode 100644 index 0000000000..b82f848261 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_menu.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba.webp b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba.webp new file mode 100644 index 0000000000..3caee1170b Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba_modal.webp new file mode 100644 index 0000000000..e510d5802e Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_netwrix_netsuite_settings_tba_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_project_key_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_project_key_modal.webp new file mode 100644 index 0000000000..96315f8974 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_project_key_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_proposed_customization_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_proposed_customization_modal.webp new file mode 100644 index 0000000000..2e030c8122 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_proposed_customization_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_pulling_erd_data.webp b/static/images/platgovnetsuite/integrations/jira_forge_pulling_erd_data.webp new file mode 100644 index 0000000000..01bd2b072e Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_pulling_erd_data.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_push_button.webp b/static/images/platgovnetsuite/integrations/jira_forge_push_button.webp new file mode 100644 index 0000000000..506a9e63b9 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_push_button.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_push_external_button.webp b/static/images/platgovnetsuite/integrations/jira_forge_push_external_button.webp new file mode 100644 index 0000000000..2e4acd0f06 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_push_external_button.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_push_external_modal.webp b/static/images/platgovnetsuite/integrations/jira_forge_push_external_modal.webp new file mode 100644 index 0000000000..3dc146b237 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_push_external_modal.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_push_in_progress.webp b/static/images/platgovnetsuite/integrations/jira_forge_push_in_progress.webp new file mode 100644 index 0000000000..6ab1704886 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_push_in_progress.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_push_successful.webp b/static/images/platgovnetsuite/integrations/jira_forge_push_successful.webp new file mode 100644 index 0000000000..d2f65be7b4 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_push_successful.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_remove_customization_in_progress.webp b/static/images/platgovnetsuite/integrations/jira_forge_remove_customization_in_progress.webp new file mode 100644 index 0000000000..92092618f1 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_remove_customization_in_progress.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_remove_customization_successful.webp b/static/images/platgovnetsuite/integrations/jira_forge_remove_customization_successful.webp new file mode 100644 index 0000000000..eacac09989 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_remove_customization_successful.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_remove_trash_icon.webp b/static/images/platgovnetsuite/integrations/jira_forge_remove_trash_icon.webp new file mode 100644 index 0000000000..3c94d15b12 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_remove_trash_icon.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_sample_erd.webp b/static/images/platgovnetsuite/integrations/jira_forge_sample_erd.webp new file mode 100644 index 0000000000..4e06d91325 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_sample_erd.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_settings_change_account.webp b/static/images/platgovnetsuite/integrations/jira_forge_settings_change_account.webp new file mode 100644 index 0000000000..b07ed788da Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_settings_change_account.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_successful_add_customization.webp b/static/images/platgovnetsuite/integrations/jira_forge_successful_add_customization.webp new file mode 100644 index 0000000000..0c61cc2a3c Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_successful_add_customization.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_tba_list.webp b/static/images/platgovnetsuite/integrations/jira_forge_tba_list.webp new file mode 100644 index 0000000000..fbd35f3915 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_tba_list.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_tba_test_connection_successful.webp b/static/images/platgovnetsuite/integrations/jira_forge_tba_test_connection_successful.webp new file mode 100644 index 0000000000..435842101a Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_tba_test_connection_successful.webp differ diff --git a/static/images/platgovnetsuite/integrations/jira_forge_view_erd_button.webp b/static/images/platgovnetsuite/integrations/jira_forge_view_erd_button.webp new file mode 100644 index 0000000000..53abc578b7 Binary files /dev/null and b/static/images/platgovnetsuite/integrations/jira_forge_view_erd_button.webp differ