--- language: "en" --- # Elements Overview ## Elements Overview Display snippets of related issues exactly where you need them [Get Started](https://doc.elements-apps.com/overview/getting-started.md) ### Highlights * #### [Introduction to Elements Overview](https://doc.elements-apps.com/overview/introduction-to-elements-overview.md) Elements Overview is an enhanced issue vizualization app designed for Jira Cloud. * #### [Overviews](https://doc.elements-apps.com/overview/overviews.md) An overview is a customizable way of displaying only relevant linked issues on the current issue. * #### [Changelogs](https://doc.elements-apps.com/overview/changelogs.md) Check out Elements Overview latest features! ### Documentation * #### [Getting started](https://doc.elements-apps.com/overview/getting-started.md) * [Introduction to Elements Overview](https://doc.elements-apps.com/overview/introduction-to-elements-overview.md) * [Installation guide](https://doc.elements-apps.com/overview/installation-guide.md) * [Basic usage](https://doc.elements-apps.com/overview/get-issues-from-the-same-reporter.md) * #### [User guides](https://doc.elements-apps.com/overview/user-guides.md) * [App configuration](https://doc.elements-apps.com/overview/app-configuration.md) * [Compatible field types](https://doc.elements-apps.com/overview/compatible-field-types.md) * #### [Tutorials](https://doc.elements-apps.com/overview/tutorials.md) * [Video tutorials](https://doc.elements-apps.com/overview/video-tutorials.md) * [How-to...?](https://doc.elements-apps.com/overview/how-to.md) * #### [Help and Support](https://doc.elements-apps.com/overview/help-and-support.md) * [FAQs](https://doc.elements-apps.com/overview/faqs.md) * [Migration hub](https://doc.elements-apps.com/overview/migrating-from-server-dc.md) * [Contact our team](https://doc.elements-apps.com/overview/contact-our-team.md) * #### [Additional resources](https://doc.elements-apps.com/overview/additional-resources.md) * [Changelogs](https://doc.elements-apps.com/overview/changelogs.md) * [Security \& Privacy](https://doc.elements-apps.com/overview/security-privacy.md) --- language: "en" --- # 2024/08/22 - Security improvements A security issue was fixed on August 22th 2024. ## Nature of the issue A security vulnerability was recently identified in Elements Overview. The vulnerability affected **version 5.2.0-AC** of Elements Overview. The vulnerability meant that Jira Project Admins could give access to internal comments in Jira Service Management customer portal requests, thus allowing privilege escalation. This vulnerability has been rated as **moderate** , according to the scale published on the [Common Vulnerability Scoring System](https://www.first.org/cvss/) (CVSS), and existed **from June, 26th 2024 to August, 22th 2024**. The vulnerability was brought to our attention by the [Atlassian Marketplace Bug Bounty program](https://developer.atlassian.com/platform/marketplace/marketplace-security-bug-bounty-program/#how-does-the-marketplace-bug-bounty-program-work-). ### Impact Based on our investigations, the vulnerability meant that a Jira Project Administrator could create an overview that displayed comments from related issues. In this case, when the comments in question were marked as "Internal" instead of "Public", they would still be visible in the overview through an error message displaying their content. They could then be visible to customers even though it should not be possible, which created a privilege escalation issue. It should be noted that this logic flaw could only be exploited if Jira Project Admins created these specific overviews including comments in Jira Service Management customer portal. ### Analysis and actions taken Once we became aware of the issue, we reproduced and identified the origin of the problem: a stack trace including the internal comment content was displayed in place of nothing when internal comments were included in Jira Service Management overviews. As a solution, we removed the possibility to display comments in overviews. **This vulnerability is now fixed**. We've updated the Atlassian Marketplace with an updated listing of our app that is free from this vulnerability. No further action is required from any user at this point. ### Conclusion We want you to know that we take this issue very seriously. We are conducting a thorough review of our internal processes to ensure this does not occur again for you and our other customers. If you have any questions, please feel free to raise a support request at [support.elements-apps.com](https://support.elements-apps.com/). --- language: "en" --- # 2024/10/10- P3 Security Issue A security issue was fixed on November 26th 2024. ## Nature of the issue A security vulnerability was recently identified in Elements Overview. The vulnerability meant that any user logged to the Customer Portal could access and therefore leak potentially sensitive issue data through the error message thrown by the `testDynamicJqlQuery` functionKey. This vulnerability has been rated as **moderate** , according to the scale published on the [Common Vulnerability Scoring System](https://www.first.org/cvss/) (CVSS), and existed **from October, 10th 2024 to November, 26th 2024**. The vulnerability was brought to our attention by the [Atlassian Marketplace Bug Bounty program](https://developer.atlassian.com/platform/marketplace/marketplace-security-bug-bounty-program/#how-does-the-marketplace-bug-bounty-program-work-). ### Impact Based on our investigations, the vulnerability meant that any user logged in to the Customer Portal could access and therefore leak potentially sensitive issue data through the error message thrown by the `testDynamicJqlQuery` functionKey. ### Analysis and actions taken Once we became aware of the issue, we reproduced and identified the origin of the problem. The issue occurs because two functions are incorrectly sending requests on behalf of the user (which should be the default behavior). Instead, when the customer portal is loaded, a system setting is accidentally changed, causing all following requests to be sent as the app instead of the user. This affects multiple requests, not just the current one. To fix this, we updated the code to ensure each function sends requests as the appropriate user. From now on, customers who don't have the necessary permissions will see a "forbidden" error message in the response. **This vulnerability is now fixed**. We've updated the Atlassian Marketplace with an updated listing of our app that is free from this vulnerability. No further action is required from any user at this point. ### Conclusion We want you to know that we take this issue very seriously. We are conducting a thorough review of our internal processes to ensure this does not occur again for you and our other customers. If you have any questions, please feel free to raise a support request at [support.elements-apps.com](https://support.elements-apps.com/). --- language: "en" --- # Additional resources This section of our documentation space serves as a comprehensive hub for important updates and informational content on Elements Overview. Here, you will find detailed changelogs, outlining the latest updates and enhancements to our services, along with thorough discussions on security and privacy issues to keep you well-informed about how we protect your data and ensure compliance with regulations. * [Changelogs](https://doc.elements-apps.com/overview/changelogs.md) * [Security \& Privacy](https://doc.elements-apps.com/overview/security-privacy.md) --- language: "en" --- # Advanced options ## NEW Use the **Advanced options** to configure AI-powered custom actions available in the **Overview** panel of your work items. These settings are managed at project level and affect all users who can see the Overview panel. ![image-20260401-082726.png](https://doc.elements-apps.com/__attachments/a_119dfb74a907e686da7109010b26a26cedae5e39f2b4ee3548692713ddcab93c/image-20260401-082726.png?cb=bad14b874c9560122d188dec8fadccc9) In order to use custom actions, Rovo must be activated within your organization and enabled on Jira and/or Jira Service Management ### What are custom actions? Custom actions are only displayed on work item views, i.e. only to licensed Jira users. Jira Service Management customers cannot use custom actions at this time. Custom actions are AI prompts powered by **Atlassian Rovo** . They let your team run repeatable, context-aware tasks directly from the Overview panel of a work item. For example, you can: * Summarize Overview panels that contain many work items * Spot work items that are late or due * Identify common patterns among work items based on fields, custom fields, labels, affected services and get insights The more work items you include in the Overview panel, the more context Rovo has to produce accurate and useful results. [\[MC-13\] Aucun historique des cafés préparés - Jira - 1 April 2026.mp4](https://doc.elements-apps.com/__attachments/a_0350477981704d7076c84158a5fcbec7af3c21c1a7fb2a710bc5536ac49222ef/%255BMC-13%255D%2520Aucun%2520historique%2520des%2520caf%25C3%25A9s%2520pr%25C3%25A9par%25C3%25A9s%2520-%2520Jira%2520-%25201%2520April%25202026.mp4.md) ### Default custom action "Summarize" Overview comes with a built‑in custom action called **"Summarize"** enabled by default. When enabled, users will see a **Summarize** button in the Overview panel, which generates a concise summary based on the work items shown there. ![image-20260401-083007.png](https://doc.elements-apps.com/__attachments/a_4387aa5f999c6f8d6b2d768380c2988de9a9764ce9d5a6de74c0a8fa8b01313d/image-20260401-083007.png?cb=bafd01824180974227b014c9cfa5b2a3) ![image-20260401-083020.png](https://doc.elements-apps.com/__attachments/a_4993cd9c8e47790c0751c63dd4908bc7f8de3acaaa3f8fccaae1c42be4e82bbb/image-20260401-083020.png?cb=bc97f675d8c5ff9ec2e746439ee27977) ### What project admins can do As a Project Admin, you can: * **Rename the custom action** * **Edit the prompt** Adjust how the summary is generated (tone, level of detail, target audience, etc.). * **Test the prompt in context and fine tune it:** * Select a work item * Click "Test prompt". The Rovo sidebar will open with the prompt you entered ![image-20260401-083628.png](https://doc.elements-apps.com/__attachments/a_0379886dc570abb2e3534b8edede86bf475a774602afa571486b328e5ba39096/image-20260401-083628.png?cb=d4fdca86bc809a5917f6aed0e94c5c63) Context is limited to 50 work items * **Disable the action** Turn it off if you don't want end users to see the **Summarize** button in Overview anymore. * **Delete the action** Remove it completely if you don't plan to use it. You can always create your own custom summary action later. ### Create custom actions You can create additional custom actions tailored to your team's workflows (e.g. "Propose next steps", "Draft release note", "Extract risks"). To create a new custom action: 1. Click "Add custom action". ![image-20260401-085035.png](https://doc.elements-apps.com/__attachments/a_6ac0620ed2b9c4f9dab029074dadd148ac5f0e93e4a631637fd29ebdd7ef8417/image-20260401-085035.png?cb=8d8070c150a3f6465f09ed85a227b464) 2. **Configure the action:** * Name the action Give it a clear, user‑friendly title. The title is inline-editable when the action is expanded. * Write the prompt Enter what you want Rovo to do in the **Prompt** text area. You can describe: * The goal (e.g. "Create a bulleted list of key risks") * The format (e.g. "Reply in Markdown with headings") * The audience (e.g. "Explain this for non-technical stakeholders") 3. **Test and refine in context** * Select a work item in Jira. * Back in Advanced options, click **Test prompt** for your action. * The Rovo sidebar opens and shows the result for the selected work item. * Adjust the prompt until the output matches what you expect. Once saved and enabled, the new action will be available in the Overview panel for end users. [Elements Overview - Jira - 1 April 2026.mp4](https://doc.elements-apps.com/__attachments/a_0bd6f33f08424eeff6fb671a5dbc2baea3b5d7fafaa0a0d3e39977d8edffd3bc/Elements%2520Overview%2520-%2520Jira%2520-%25201%2520April%25202026.mp4.md?cb=4adc1d87b135c37c3dc0ba47b0af4acb) ### Disable or delete custom actions You stay in control of which actions your users can access. #### Disable a single action * Use the toggle next to an action to **hide it from end users** without deleting it. * You can re‑enable it later at any time. #### Disable all custom actions * If you turn off the global **Enable all custom actions** switch, **no custom actions** (including "Summarize") are shown in the Overview panel for end users. * Your configuration is preserved; you can turn the switch back on to restore them. #### Delete an action * Click the **trash** icon on a custom action row to permanently delete it. * The action is removed from the Overview panel and from the configuration. --- language: "en" --- # App configuration Elements Overview is configured at a project level, by **project administrators**. The app global administration page can be accessed right after its installation and from the Manage Apps menu. ![image2022-10-27_17-21-13.png](https://doc.elements-apps.com/__attachments/a_6a2ef5d6b7a59e4df34a06f94cb6d8b604c4bc6f0f0231d2d261ec7816296c92/image2022-10-27_17-21-13.png?cb=6f3325f2165a1419c7ff58b8a00c7d95) You'll be prompted to select a project to create an overview, in which you'll be redirected to so you can configure it. The configuration is straightforward and done in 3 different steps. * [Overviews](https://doc.elements-apps.com/overview/overviews.md) * [Overview options](https://doc.elements-apps.com/overview/overview-options.md) --- language: "en" --- # Bulk edit overviews fields ## What is the bulk edition of fields? This feature introduces the capability to edit multiple issue fields simultaneously within an overview. It is designed to enhance efficiency by allowing users **to update multiple related issues at once, directly from the Table view**. ![image-20240605-124036.png](https://doc.elements-apps.com/__attachments/a_bbca2bc9a961039bf57e085a1c96da86a5d04efed6f3e07e3ce778b5f5b57053/image-20240605-124036.png?cb=871efee41858b2b4d6806970480e74a8) A significant pain point for users managing lots of Jira issues is the time-consuming process of updating fields for multiple issues individually. This manual approach can lead to inefficiencies and increased potential for errors, especially when dealing with large projects. The lack of a streamlined bulk editing capability within Jira's native interface exacerbates these challenges, hindering productivity. ## How to bulk edit issues Directly in the overview on the issue, select the issues you want to edit with the **checkbox** at the left, then click on the **Edit**button below a compatible column, and enter the desired value. **Please note** * The bulk edit respects user's permissions. * For project's fields (versions, components), values from every project will be displayed and created in the relevant projects if needed. * If your overview is paginated, the bulk edit will only apply to issues on the page being displayed. --- language: "en" --- # Calculated footers for numeric fields ## What are calculated footers? Footers can be added to any numeric field column displayed in overviews. They allow users to perform calculations on numerical data, directly displayed in the footer section, in order to **aggregate and analyze numerical data more efficiently without the need for external tools or manual calculations**. ![overview calculated footer.png](https://doc.elements-apps.com/__attachments/a_59f09ea67e11951123d7bf1bf4499f365a0d4815bf2b70d35f1c5db6e1ffcff2/overview%20calculated%20footer.png?cb=807b6c3dcfa0b897a3f93a96b7e72d54) Footers can be configured within the [Content](https://doc.elements-apps.com/overview/content.md) step of an overview configuration and are visible in "Table" view (refer to [Display](https://doc.elements-apps.com/overview/display.md) to learn more about the "Table" and "Card" views). ## Available operations For any number field type, you can configure the following operations: * Sum * Mean * Minimum * Maximum * Product * Median Please note that operations are performed on every issues listed in the overview, included those displayed**after the first page of results** when your overview is paginated. ## How to configure footers The configuration of footers is done in the [Content](https://doc.elements-apps.com/overview/content.md) page of the overview set up in 2 steps: 1. After adding a number field, click on configure in the Footer column ![overview calculated footer configuration 1.png](https://doc.elements-apps.com/__attachments/a_d13c488351732ddb0ddf810fa430509615cd82b944aa0d1147b9eb5b3ce113a5/overview%20calculated%20footer%20configuration%201.png?cb=f9641106a61823e7ac1cf1219e8979ed) 2. Select the operation you want to perform on the configured field: ![overview calculated footer configuration 2.png](https://doc.elements-apps.com/__attachments/a_afa77fa14f75fb250f7b85137d5009a7169fca37a4105c1730df37f7c5c4b1f7/overview%20calculated%20footer%20configuration%202.png?cb=a2d7750c10bbafb24a8a7eeb097eda8e) --- language: "en" --- # Changelogs On this page, you will find the **update history** for Elements Overview | **Release date** | **Changes** | |------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | 2026-04-08 | New feature: [Rovo-powered actions](https://doc.elements-apps.com/overview/advanced-options) | | 2026-02-10 | New custom field type supported: Label | | 2025-12-04 | ++Bug fixes:++ * Progress bar and hierarchy display options failed to be enabled when fields are subsequently added * The rendering of Overview panels crashes when the "Parent" field is present | | 2025-11-18 | To boost performance and reliability, the Overview now displays work items in batches of 25, ensuring smoother and more consistent navigation. | | 2025-09-08 | ++Enhancements:++ * Edit and bulk edit "Watchers" and "Security level" fields from overview panels. * Display an error message when the data limit in the overview panel is reached. * Group field pickers into "Assets object fields" and "System and custom fields" for easier browsing during configuration. * Limit the display to a maximum of 15 fields in overview panels to prevent data limits from being reached. ++Bug fix:++ Resolved the issue of duplicate rendering of child work items when the parent work item is edited while expanded. | | 2025-08-21 | ++New features:++ * Progress bar now accounts for work items that are in progress and remain to be done (to do) * Ability to edit/bulk edit the work type from Overview panels * Enable bulk edition of issue fields that share common values ++UI improvements:++ * Progress bar no longer displays when the Overview panel is empty * The look and feel of the issue hierarchy has been improved ++Bug fixes:++ * Overview panel crashes if priority field is displayed but not editable | | 2025-07-22 | [Assets object fields supported in Dynamic JQL](https://doc.elements-apps.com/overview/display-work-items-with-the-same-affected-services.md) | | 2025-07-21 | New field type supported: Assets object Bug fix: you can now sort by priority in Overview panels | | 2025-07-15 | Organizations and Affected services now supported for display and as a dynamic JQL variable | | 2025-07-03 | * More fields rendered in Overviews * bug fix: mouse wheel click opens 2 tabs in Firefox | | 2025-05-26 | * The JSM "Sentiment" field is now supported for display in Overview and as a dynamic JQL variable * "Request Type" field is now supported for display in Overview * The display rendering of various fields was improved | | 2025-04-22 | * New app administration available from Apps menu * Display Resolution field in Overviews * Display issues with the same "Sprint" as the current issue * Improvements to "Edit" buttons in Overviews | | 2024-11-26 | * SLA fields are now supported on the Customer Portal * A [security vulnerability](https://doc.elements-apps.com/overview/2024-10-10-p3-security-issue)was fixed | | 2024-08-22 | * Improvements made to pagination: up to 500 issues can now be displayed in any overview * [Security improvement](https://doc.elements-apps.com/overview/2024-08-22-security-improvements.md) | | 2024-06-06 | * Overviews progress bar * Display issues hierarchy in overviews * Bulk edit issues in overviews * Add read-only fields for JSM portal ([Atlassian CR](https://jira.atlassian.com/browse/JSDCLOUD-4328)) * Data residency * Calculated footers for number fields * New supported field types (Sprint, Project, Data time) * Increase number of issues and pagination for overviews | | 2023-02-20 | * Display linked issues * Displayed related issues depending on parent key, current issue key and project name/key | | 2023-02-01 | * Displayed related issues depending on more field values from current issue | | 2022-12-01 | * Initial release | --- language: "en" --- # Compatible field types This page lists all the type of Jira fields (native or custom fields) that can be used in Elements Overview. **Most compatible fields can be displayed and edited directly in overviews** ( CAN DISPLAY \& EDIT ), whereas some can only be displayed ( CAN DISPLAY ). Please note that you'll be able to edit a custom field in an overview only if you have the right edit permissions on the Jira instance. If you want more field types to be supported by Elements Overview, please reach out through [our Support team](https://support.elements-apps.com/portal/11?createRequest=true&portalId=11&requestTypeId=129). | **Field type** | **Description** | **State** | |----------------------|-----------------------------|---------------------| | Affected services | Jira Service Management | CAN DISPLAY | | Assets object | Jira | CAN DISPLAY | | String | Jira | CAN DISPLAY \& EDIT | | Date | Jira | CAN DISPLAY \& EDIT | | Date time | Jira | CAN DISPLAY \& EDIT | | Number | Jira | CAN DISPLAY \& EDIT | | User | Jira | CAN DISPLAY \& EDIT | | Group | Jira | CAN DISPLAY \& EDIT | | Status | Jira | CAN DISPLAY \& EDIT | | Priority | Jira | CAN DISPLAY \& EDIT | | Votes | Jira | CAN DISPLAY | | Components | Jira | CAN DISPLAY \& EDIT | | Versions | Jira | CAN DISPLAY \& EDIT | | Issue type | Jira | CAN DISPLAY | | Select list | Jira | CAN DISPLAY \& EDIT | | Labels | Jira | CAN DISPLAY \& EDIT | | Custom field: Label | Jira | CAN DISPLAY \& EDIT | | Log work | Jira | CAN DISPLAY | | Issue key | Jira | CAN DISPLAY | | Parent | Jira | CAN DISPLAY \& EDIT | | Parent link | Jira | CAN DISPLAY | | Progress | Jira | CAN DISPLAY | | Σ Progress | Jira | CAN DISPLAY | | Original Estimate | Jira | CAN DISPLAY | | Organizations | Jira Service Management | CAN DISPLAY | | Remaining Estimate | Jira | CAN DISPLAY | | Request language | Jira Service Management | CAN DISPLAY | | Request Participants | Jira Service Management | CAN DISPLAY | | Request Type | Jira Service Management | CAN DISPLAY | | Resolution | Jira | CAN DISPLAY | | Responders | Jira | CAN DISPLAY | | Linked issues | Jira | CAN DISPLAY | | Satisfaction | Jira Service Management | CAN DISPLAY | | Satisfaction date | Jira Service Management | CAN DISPLAY | | Security Level | Jira | CAN DISPLAY | | Sprint | Jira | CAN DISPLAY | | Team | Jira | CAN DISPLAY | | Time spent | Jira | CAN DISPLAY | | Time tracking | Jira | CAN DISPLAY | | Project | Jira | CAN DISPLAY | | SLA | Jira Service Management | CAN DISPLAY | | Watchers | | CAN DISPLAY | | Organization | Customer Service Management | CAN DISPLAY \& EDIT | | Entitlement | Customer Service Management | CAN DISPLAY | --- language: "en" --- # Contact our team We are committed to providing you with comprehensive support on Elements Overview through three convenient contact methods: * [**Our Support Portal**](https://support.elements-apps.com/portal/11?createRequest=true&portalId=11&requestTypeId=129): ideal for troubleshooting, reporting bugs, and addressing technical issues. Access our support portal directly to submit your queries and receive timely assistance from our dedicated support team. * [**A call with the Product Team**](https://talk.elements-apps.com/overview): for change requests and more detailed product discussions, you can book a time slot with our Product team. This allows for a more tailored approach to your specific needs and enhancements. Our team is here to ensure your experience with our services is smooth and efficient. Whether it's a quick fix or a significant change, we're just a click away. --- language: "en" --- # Content The final step in configuring an overview consists in selecting the custom fields you want to display. As a project administrator, and depending on the location you chose, you can customize each overview with the custom fields you want to display. The location selected in the [display](https://doc.elements-apps.com/overview/display.md)configuration has an impact on how data is displayed. This is because we want to ensure the best user experience anywhere an overview is configured. If you select **Issue details** or **Request panel** , the layout will be a "Card", close to the Glance view experience you're familiar with. If you select **Issue panel** , **Issue activity** or **Request details**, the layout will be a "Table". ## Configure content in Card layout Configuring the content of an overview in Card layout is done through the following interface, separated in two sections "**Headers** " and "**Other fields**". ![image2022-10-28_9-57-37.png](https://doc.elements-apps.com/__attachments/a_4a3cb937c25632eb744bd9e17e6dfd0dba3a4193dfca158896f4acb56b1b4268/image2022-10-28_9-57-37.png?cb=50afd55d1660e40a2883810e59d1d3d5) ### Headers Headers are native Jira custom fields, originally displayed in the "Linked issues" section of Jira. You can select which ones you want to display in the header, from none to all of them. Below, the headers have been configured to display the "Issue type", "Key", "Status", and "Summary" of the issue: ![header blur.png](https://doc.elements-apps.com/__attachments/a_bee72d136433db3b8608620a938a0d0341d7366b62720cfe21346fd9970d8282/header%20blur.png?cb=8740b60a8803cde1ebdf5f186c6b3c26) ### Other fields You can add any other Jira custom field in this section, and the header fields that have not been selected in the headers They are displayed just like they would have been in the Jira native glance view. Other fields can be reordered and renamed in the overview, for a better understanding during the overview visualization. ![other fields blur.png](https://doc.elements-apps.com/__attachments/a_e03f0c55f1261f7278b62a7c74095bacd9e308938880c288d904b2dd99bb9f10/other%20fields%20blur.png?cb=ff3f1d18793720601856cb18d5b94002) ## Configure content in Table layout ### Fields configuration In this layout, you just need to select the Jira custom fields you want to display in the table, and reorder them in the way you want it by simply dragging and dropping them. ![image2022-10-28_10-11-38.png](https://doc.elements-apps.com/__attachments/a_55a0bacedfe48454cb49ef42c2e581688a3988d6dbaebaf40247d514b0603604/image2022-10-28_10-11-38.png?cb=402ea983bbdae29e989df6f40409acec) Using the configuration above will result in this overview for your end users: ![image2022-10-28_10-14-16.png](https://doc.elements-apps.com/__attachments/a_55a5c26713edfaa0c6a2a13426e647fc59ef057a8516fe787296cdc1c94cd01f/image2022-10-28_10-14-16.png?cb=5c6cc27d72402fb2f49e6e0267d69367) You can select up to 15 fields to display in Overview panels for performance reasons. ### Other options #### Alias You can use the "**Alias**" column" to rename the column in the final overview, if you want your users to get a better understanding of what is displayed. #### Footers for numeric fields This option is available when adding a numeric field to the overview content, such as "Story points". Learn more about calculated footers in a dedicated page: [Calculated footers for numeric fields](https://doc.elements-apps.com/overview/calculated-footers-for-numeric-fields.md). #### Show progress bar Enable this option to display a progress bar above the overview. Learn more: [Display overviews issues progress](https://doc.elements-apps.com/overview/display-overviews-issues-progress.md). #### Display hierarchy Enable this option to display all issues in the overview in a link-based hierarchy. Learn more: [Display issues hierarchy in overviews](https://doc.elements-apps.com/overview/display-issues-hierarchy-in-overviews.md). ## Preview You don't need to waste time testing your overview in an issue, as it is possible to test it directly from the Content configuration page. To do so, select an issue in the select list. Only issues from the current project are proposed. This preview takes into account the display conditions and focus filters, so your test will show you exactly what your end users will see. ### Table layout preview ![image2022-10-28_10-17-17.png](https://doc.elements-apps.com/__attachments/a_27c159700377d1824a6a71f3d3c1c6a79a125b1d8d4875cced6419c3249f2fb6/image2022-10-28_10-17-17.png?cb=3ae01c9700b66f7190438c028a4df8cd) ### Card layout preview ![image2022-10-28_10-18-4.png](https://doc.elements-apps.com/__attachments/a_aabbe11808fa332714541737acd60052286ff926c4d1ac03f20134cd38bc20c8/image2022-10-28_10-18-4.png?cb=b53cca42f9990ca2e7a2ecfaa044b196) ### Inconsistent configuration When the conditions set up in the[Display](https://doc.elements-apps.com/overview/display.md) step do not match the chosen issue for the preview, this warning message is displayed: ![image2022-10-28_10-28-39.png](https://doc.elements-apps.com/__attachments/a_f6562bfbe361890613942fcd820609c9c2ba8306493a99536a937f77be62fa0d/image2022-10-28_10-28-39.png?cb=894df8f7727f3c63151e5fa64db1e4e0) --- language: "en" --- # Display The first step of an overview configuration consists in selecting where to display your overview. ## Issue Display Conditions As a project administrator, you can control when and where an overview is displayed on an issue. ![image2022-10-27_18-36-13.png](https://doc.elements-apps.com/__attachments/a_7c1c134c35eb0c983e084b6ba79b2f6841c4398b3f3a87ad28b1b96c21184fe9/image2022-10-27_18-36-13.png?cb=a0763d118351906e8b523e7278c428b3) ### Example Condition To display overviews only on issues of type Bug, use the following JQL condition: `issuetype = Bug` ![image2022-10-27_18-37-27.png](https://doc.elements-apps.com/__attachments/a_1632d6267f11b3edaba970db7246733e802fd4388be751b6ec9c1fc0effaf23d/image2022-10-27_18-37-27.png?cb=36cb502cb031da576ec1bca24291833f) For more details on JQL, visit the [Jira JQL Guide](https://www.atlassian.com/software/jira/guides/expand-jira/jql). ## Overview display context You can choose where the overview is displayed within the issue. An overview can have two types of view: **Table** or **Card**, depending on the location. Some features, such as calculated footers or the hierarchy display, are only available in the Table view. The available locations are: **Jira and JSM Agent view:** * **Issue details:** Displayed in the Glance view experience (Table view) * **Issue panel:** Displayed under native Jira sections (Card view) * **Issue activity:** Displayed in a dedicated tab (Table view) **JSM Portal:** * **Request panel:** Displayed on the right part of a request (Card view) * **Request details:** Displayed under native Jira sections (Table view) **Note:** JSM issue locations can only be selected in Jira Service Management projects administration. ![image2022-10-28_9-18-52.png](https://doc.elements-apps.com/__attachments/a_43ed4ff29ce279565a134d97b8b08f9607f0d07cb81c04f56e2f9d450f2fd82a/image2022-10-28_9-18-52.png?cb=8b928bf737226e474ba1bd2be787c803) [Next step: Focus configuration](https://doc.elements-apps.com/overview/focus.md) --- language: "en" --- # Display issues hierarchy in overviews ## What is the hierarchy view? The **Display hierarchy** option is designed to provide a hierarchical representation of related issues within Jira tickets. When enabled, users can visualize the relationship between parent and child issues in a structured table format, enhancing clarity and organization in project management workflows. ![overview issue hierarchy.png](https://doc.elements-apps.com/__attachments/a_4eb917a85c4b8ae697278a4d73d065836e6cb2272f00c0c32aa78aa620ecf509/overview%20issue%20hierarchy.png?cb=568776bcfebc57a9b2c0f58084e1cb9d) Hierarchies can be enabled within the [Content](https://doc.elements-apps.com/overview/content.md) step of an overview configuration and are only available in "Table" view (refer to [Display](https://doc.elements-apps.com/overview/display.md) to learn more about the "Table" and "Card" views). ## Available hierarchy levels This option uses the "Parent link" field and has three levels of hierarchy: * Epic * Stories * Sub-tasks ## How to display issue hierarchies The configuration of hierarchies is done in the [Content](https://doc.elements-apps.com/overview/content.md) page of the overview set up in 2 steps: 1. Navigate to the Content section of the overview. 2. Enable the "Display Hierarchy" toggle. ![overview issue hierarchy configuration.png](https://doc.elements-apps.com/__attachments/a_d8a4fb2a8c7de4152f2471ca56edf397e43211e4d16f0867f9ee68357c00df86/overview%20issue%20hierarchy%20configuration.png?cb=0cbd708e4116483ef12eb9d291cf144f) By default, only descendants will be displayed. To include both ascendants and descendants, enable the "**Rigid Hierarchy**" option. --- language: "en" --- # Display overviews issues progress ## What are overview progress bars? The **Show progress bar**option is designed to enhance visibility and tracking within Jira tickets. It provides a visual representation of the progress of related issues directly within an overview. This allows users to quickly assess the status of related tasks without having to navigate away from the current ticket. ![image-20250821-082212.png](https://doc.elements-apps.com/__attachments/a_30470d0a0b4cfb4beed73952b3731d5bf3d4946a27b8f3cfa03b39d9d059c3bd/image-20250821-082212.png?cb=bd5e616b41d63e302c13ed412b9ad9ca) Progress bars can be enabled within the [Content](https://doc.elements-apps.com/overview/content.md) step of an overview configuration and are available in both "Table" and "Card" views (refer to [Display](https://doc.elements-apps.com/overview/display.md) to learn more about the "Table" and "Card" views). Please note that the progress displayed relates to every issues listed in the overview, included those displayed after the first page of results. ## How to display progress bars To enable this option, you need to navigate through an overview configuration page in the Content section, and activate the **Show progress bar** toggle button. ![display overview progress configuration.png](https://doc.elements-apps.com/__attachments/a_624bf0db5ba4136877fa99d3b17e58939bd2dcaf13be639237580de01ce81b49/display%20overview%20progress%20configuration.png?cb=409baab0fe2c0acf4205ceddb99e2d1a) --- language: "en" --- # Display work items with the same Affected services ## Problem: Service desk agents struggle to identify potential major incidents or outages early when working on customer requests. This leads to longer ticket processing times and inefficient incident investigation, as agents lack visibility into other work items affecting the same services. ## Solution: Display work items with the same affected services within the current work item. This enables agents to quickly spot related incidents or patterns and respond more efficiently. ### Tutorial #### Prerequisites * A service project with the ["Services" feature](https://support.atlassian.com/jira-service-management-cloud/docs/what-is-services/) enabled * Project admin permissions * [Elements Overview](https://go.elements-apps.com/OVC) installed #### Configuration steps ##### 1 - Access Elements Overview in Project Settings * Go to your JSM project. * Click on Project Settings \> Apps \> Elements Overview. * Create a new [overview](https://doc.elements-apps.com/overview/app-configuration/overviews/). ![image-20250724-160805.png](https://doc.elements-apps.com/__attachments/a_4b54a20983e11a09bdb0d6f5ea1082f6d78dd134817eac7083d1487af6f28e4f/image-20250724-160805.png?cb=8376d0ed2a61a42fc6b0077a2df3fc17) 2- **Choose Where to Display the Overview** * In the [Display](https://doc.elements-apps.com/overview/display)section, select where the overview will appear. * For this use case, select "Work item panel" so agents can see it while processing tickets. ![image-20250724-154137.png](https://doc.elements-apps.com/__attachments/a_c79fdbd23eb03a89eeda966849f1d89bfb071380d18d4455afa9d0317c4127ee/image-20250724-154137.png?cb=3fd5275b1d6c89ac521b5236e8ed2525) 💡 **Pro-tip:** Use display conditions to restrict the overview to work items matching specific JQL. ##### 3- **Configure Which Work Items to Display** In order to pull work items with the same Affected services as the current work item, you'll need to choose the "Dynamic JQL" mode. * In the [Focus](https://doc.elements-apps.com/overview/focus) section, choose "Dynamic JQL" mode. * In the "Work items to retrieve" field, enter: "Affected services" IN () Use the IN operand (not =) since "Affected services" is a multi-select field * Click "Insert" and select the "Affected services" field to inject the dynamic variable. ![image-20250724-154111.png](https://doc.elements-apps.com/__attachments/a_4a4c5ae05957fed85dcc78ca77daef6677bd5e84fcc77917541d3b02c35776b3/image-20250724-154111.png?cb=e102373ba5de2f75ac30ce58e63228fc) Result: ![image-20250724-154242.png](https://doc.elements-apps.com/__attachments/a_50fe730d74f26a3cdb125b67d6addc568f99c1f2d3ad5786a7bc587b2a1ad831/image-20250724-154242.png?cb=60f6e9c84229f8336347282dea7c7ea5) * Test your query using the issue picker and "Test query" button. ![image-20250724-154423.png](https://doc.elements-apps.com/__attachments/a_a4e3832e388dbcd8af54e043d4fa6c22f704717d444af9cfb5c08bea5337b360/image-20250724-154423.png?cb=a16ec6a4ce791bc873f5e71c07c9df84) ##### 4- **Select Fields to Display in the Overview Table** * Configure the [table layout](https://doc.elements-apps.com/overview/content#Content-ConfigurecontentinTablelayout). * Choose which fields to show in the overview table. For this use case, we selected the following fields: ![image-20250724-154945.png](https://doc.elements-apps.com/__attachments/a_5077639585a40e1396d374c731b24ddb4cd37562f0d3f5856aa8dea454ada5c8/image-20250724-154945.png?cb=563bd4f14fb216ab19f91228d5a6c7de) * Use the Preview feature to see how the table overview will render in the context of the work item selected. ![image-20250725-073407.png](https://doc.elements-apps.com/__attachments/a_fddb2a189870703d8cc6dfd6315278ebb50f1900364eba253f5d4d1281733217/image-20250725-073407.png?cb=8e48783d63c204cef41c29e1895bdb61) ##### 5- Final result When processing a work item, Service Desk agents will see all work items with the same Affected services, quickly allowing them to identify related incidents and respond more efficiently to potential major issues. ![OVERVIEW AFFECTED SERVICES.png](https://doc.elements-apps.com/__attachments/a_9aee0274ca69e9d2febb17299fd05a7af0bc958e14f57b3ab8cff444bf52463c/OVERVIEW%20AFFECTED%20SERVICES.png?cb=aff10263871e2ace9d7616c50d624eb1) --- language: "en" --- # Enhance customer experience with Sentiment-driven insights in Jira Service Management As organizations scale, the quality of internal support becomes instrumental in employee satisfaction and productivity. Jira Service Management (JSM) now offers customer sentiment analysis---powered by Rovo (formerly Atlassian Intelligence)---that can be strategically applied across the employee lifecycle to foster more empathetic, responsive, and efficient internal support. In this tutorial, we'll show how Elements Overview can leverage the sentiment analysis associated with customer requests to gain **sentiment-driven insights** into a broader **Employee Experience Management (EXM)** framework to empower support agents, HR, IT, and service teams. ## 🧭 Objectives By the end of this guide, you will be able to: * Understand how **sentiment metadata** can elevate internal service delivery. * Apply **three actionable use cases** to support teams within the employee lifecycle. * Build **EXM strategies** using sentiment trends, patterns, and proactive alerts. ## 🛠️ Prerequisites * Jira Service Management Premium or Enterprise Plan * Rovo enabled * Sentiment analysis feature toggled on from the Project Settings * [Elements Overview](https://marketplace.atlassian.com/apps/1229459/elements-overview-display-related-issues-in-custom-views?hosting=cloud&tab=overview) installed ## 🧩 Background ### What is sentiment analysis in JSM? Automatically classifies user tone (Positive, Neutral, Negative) on incoming tickets and comments, helping agents triage, prioritize, and communicate with empathy. ### Why it matters for EXM? Support interactions are touchpoints in the employee journey---their emotional tone can reveal underlying friction points in IT, HR, or operations. By surfacing sentiment trends, we can proactively improve service experience and reduce frustration. ## 💼 Use Case 1: Viewing past issues from the same reporter with negative sentiment **Scenario**: An employee submits a ticket about VPN access. The agent sees that this person has submitted three other tickets recently---two marked Negative. ### ✅ Benefits: * Recognize long-standing frustrations or unresolved issues * Adjust tone to acknowledge prior friction ("Thanks for your patience on this...") * Avoid repetitive solutions ### 🔧 How-To: In Elements Overview: * From the Project Settings, configure the following Overview: ++Focus++: ![image-20250520-130135.png](https://doc.elements-apps.com/__attachments/a_6cc3742ccedb1f1e6856244b5cf04d77cd66417685e33b63a23278ae0f1785ae/image-20250520-130135.png?cb=816b105433a65439c86298b35524dfc8) ++Content++: ![image-20250520-130458.png](https://doc.elements-apps.com/__attachments/a_a462b08ac44758eef9508839a41ac2864b1bd33b74beef0df4f44abb653362fb/image-20250520-130458.png?cb=89053faa001da3b097c148aea00804fc) Result in the customer request: ![image-20250520-131542.png](https://doc.elements-apps.com/__attachments/a_07ccfb1dd5e393fdc889e0ae53984b31912983a178828f77b70b7fec20fcbb54/image-20250520-131542.png?cb=ed38253b9df8dde8eecd0b4be411abd6) ## 💬 Use Case 2: Surfacing similar sentiment issues **Scenario**: A frustrated employee reports "Slack crashes after login." The sentiment is marked Negative. The system shows similar tickets from other employees also marked Negative with similar keywords. ### ✅ Benefits: * Identify major incidents early * Accelerate and simplify root cause analysis * Escalate recurring issues faster to IT/Product ### 🔧 How-To: In Elements Overview: * From the Project Settings, configure the following Overview: ++Focus++: ![image-20250520-133451.png](https://doc.elements-apps.com/__attachments/a_5e6908de5fa9d197f1e1f9fb464e8ac5332d48046a2db37c141370bd084a9ba1/image-20250520-133451.png?cb=a737010437e5ecb8ceef803812c2cd69) ++Content++: ![image-20250520-133808.png](https://doc.elements-apps.com/__attachments/a_3a0d35b85bcb63dd619e8cb4a1635c5cecd70aa97174251d8a87eb84c087dd47/image-20250520-133808.png?cb=7369aad61d76531c1df5162e39caea4e) Result in the customer request: ![Juliette - WIP (4).png](https://doc.elements-apps.com/__attachments/a_1ba018179c1de5d01ef9c60809e4d9a50910cefa7f8232fd4583d15da5ce136a/Juliette%20-%20WIP%20(4).png?cb=9d851e21fb8a15f03cf3889728c3adf8) ## 📂 Use Case 3: Identifying internal services that may require improvements **Scenario**: HR notices that "Remote Work Equipment Requests" have a spike in Negative sentiment over the past 45 days. ### ✅ Benefits: * Identify which internal services are pain points * Inform service design or process changes * Update documentation/self-service flows ### 🔧 How-To: In Elements Overview: * From the Project Settings, configure the following Overview: ++Focus++: ![image-20250526-095430.png](https://doc.elements-apps.com/__attachments/a_bff0f3b5641971648aa1eace0c58578377f144b7a77bee754be0134a2bcdf8e2/image-20250526-095430.png?cb=197bc3bae1607e9b91538a02d3d510af) ++Content++: ![image-20250526-095538.png](https://doc.elements-apps.com/__attachments/a_8bd556d86fb68ae3e11b8922890219c8430d714f21a04f05cc2428282d155d70/image-20250526-095538.png?cb=ba910983df4f2c21a4a7f6a7e59fbfd1) Result in the customer request: ![image-20250526-095335.png](https://doc.elements-apps.com/__attachments/a_52be623779727433ccc6354bb7a642123c430ab1c99caa2c252c2b2b23fff56a/image-20250526-095335.png?cb=189104bc9e5daf0eee75124c4c180566) ## 💡 Tips \& Best Practices * Use **sentiment as an indicator**, not a judgment---always follow up with qualitative review. * Combine sentiment data with CSAT and survey responses for a holistic picture. * Train agents to acknowledge emotional tone without over-promising. --- language: "en" --- # FAQs On this page, you will find answers to common questions that might interest you as well. ## How does pricing work for Elements Overview? Elements Overview is sold as a monthly or annual subscription. Customers are eligible for support and automatic version updates as long as the subscription is active. **If you have 10 users or less licensed for your Jira Cloud instance, you will not be charged at all** to use Elements Overview. If you have more than 10 users, you'll be charged per user amount based on the user tier. You can find details about our pricing [on our Marketplace listing](https://marketplace.atlassian.com/apps/1229459/elements-overview-custom-display-for-related-issues?hosting=cloud&tab=pricing). ## How is annual Cloud pricing calculated? Annual Cloud pricing is calculated on a tiered basis (just like the monthly per-user Cloud pricing). Note that by choosing an annual subscription, you're automatically granted a discount as you are only charged for 10 months of the year, rather than 12 months if you were to subscribe on a monthly basis. ## Can I trial Elements Overview for free before purchasing it? Elements offer a fully functional **free 30 day trial** of Elements Overview to companies who wish to try our product. Once this trial period is over, the cost of the app will automatically be included in your next bill unless manually deactivated via the *Manage Apps* page under the Jira Administration menu. ## What are the data management policies for Elements Overview? For our applications built on the **Atlassian Forge framework**, Elements leverages Atlassian's hosted storage. This means that your data resides within the Atlassian Cloud environment, benefiting from Atlassian's built-in security and compliance standards. ### Data Storage \& Location * **Infrastructure:** All app data is stored in **Forge-hosted storage** provided by Atlassian. * **Location:** Data is typically hosted in the same region as your Atlassian site, ensuring consistent data residency. ### Data Retention \& Deletion In accordance with [Atlassian's data lifecycle policies for Forge apps](https://developer.atlassian.com/platform/forge/storage-reference/hosted-storage-data-lifecycle/), the following retention rules apply: * **App Uninstallation:** If the application is uninstalled, your data is retained for **60 days** following the end of your billing or trial period. * **Data Recovery:** Should you reinstall the app within **21 days** of uninstallation, you can request that the new installation be relinked to your existing data. * **Permanent Deletion:** After the 60-day retention period expires, all stored data is automatically and permanently deleted from Atlassian's infrastructure and cannot be recovered. * **Site Deletion:** If your entire Atlassian site is deleted, all associated app data is permanently removed once the site deletion process is finalized. ### Data Privacy * **Access Control:** Elements employees do not have access to your Forge-hosted data except where strictly necessary for support purposes and with your explicit permission. * **Compliance:** This management follows the same strict privacy principles outlined in our **Data Processing Agreement**. ### Data Export Due to the technical architecture of the Forge platform, Elements does not have access to the underlying persistent storage where your application data is kept. Consequently, **Elements is unable to provide or perform direct data exports** for Forge applications. To obtain an export of your application data, you must **contact Atlassian Support directly**. As the host and controller of the Forge infrastructure, only Atlassian has the necessary access to retrieve and provide data stored within their hosted storage environment. This model ensures that your data remains within Atlassian's secure environment, handled according to their standard data retrieval and security procedures. --- language: "en" --- # Focus The second step of an overview configuration consists in selecting which set of issues you want to see displayed in your overview. ![focus.png](https://doc.elements-apps.com/__attachments/a_74a5881928e6b52146575a321c683688e500248cc201ddfdef540cd5f1daf696/focus.png?cb=bd4dff2a263d529bda9b5a390ec1382e) You have two to three options available: * **Dynamic JQL**: this mode allows you to configure a JQL filter using, if needed, current issue values to retrieve and display relevant issues. * **Linked issues**: this mode allows you to display relevant linked issues in the current issue. * **Additional fields:** Only available for portal overviews on Jira Service Management, it allows to display additional fields from the current issue to your customers, even if those fields should not be visible. ## Dynamic JQL As a project administrator, you can choose which issues you want to display in an overview. To do so, you need to configure a JQL, the same as the ones you could use in native Jira. ![image-20240730-093109.png](https://doc.elements-apps.com/__attachments/a_b9b5e6d3e3f8360b19a535eca91c850327cfba9686ca1f19cb890730234d9650/image-20240730-093109.png?cb=3406689e0a7b779d8f31d8720267b50f) ### Issue to retrieve You are prompted to enter a JQL in this section to filter issues that will be displayed in the table. This value can be left empty. Please note that when using a Dynamic JQL to display issues in the Jira Service Management customer portal, the "**order by**" statement cannot be used. Issues will be displayed in the overview in the order they are returned by default by Jira ("order by issue key DESC"). The JQL can be static or leverage dynamic values from the current issue where the overview is displayed. Using variables in the JQL enhances its power, enabling the display of dynamic content that adds context-specific information, such as support requests raised by the same reporter or incidents related to the same component. Example:`project = OSD AND reporter = ${issue.reporter}` In this example, `{$issue.reporter}` will be dynamically evaluated in each overview where it's configured, and the JQL will be adjusted accordingly. Variables can be injected using the **+ Insert** button located at the right end of the JQL input form. #### Supported field types | **Field type** | **State** | |-------------------------------|---------------| | Assets object | Supported | | Affected services | Supported | | Short text | Supported | | Number | Supported | | Single user | Supported | | Status | Supported | | Select list (single choice) | Supported | | Select list (multiple choice) | Supported | | Select list (cascading) | NOT SUPPORTED | | Labels | Supported | | Versions | Supported | | Sprint | Supported | | Single group picker | NOT SUPPORTED | | Multi groups picker | NOT SUPPORTED | | Multi user | Supported | | Text multi line | NOT SUPPORTED | | Date picker | Supported | | Parent key | Supported | | Current issue key | Supported | | Current project key/name | Supported | | Organizations | Supported | | Request type | Supported | | Reporter | Supported | | Severity | Supported | | Sentiment | Supported | | Impact | Supported | | Organization (CSM) | Supported | If you require a field type that is not currently supported, please [contact our support](https://support.elements-apps.com/) with your request. We continually review feedback to enhance our features and may consider adding new field types based on user needs. ### Project whitelist This option is only visible when displaying overviews in **Jira Service Management**. Overviews will only display issues from the Jira projects selected in the whitelist. If this list is left empty, nothing will be displayed. The list of projects available in this option is limited to the projects that the admin configuring the overview has access to. This means that if several different admins configure the same overview, it may lead to different project whitelists, depending on their respective permissions. This option exists to make sure that only data from authorized projects are displayed to your customers through the JSM customer portal. ### Pagination When using the Table display, issues are paginated by pages of 25, displaying a maximum of 500 issues in total (spread accross 20 pages). When using the Card display, all issues are listed, up to a maximum of 500 issues. ### Test your configuration When configuring a JQL, you don't need to waste time testing it in Jira. You can test your query against an issue directly from Elements Overview. If you have entered a variable in the filter, using the test issue will replace the variable by the value of the selected field. ## Linked issues As a project administrator, you can choose which linked issues you want to display in an overview. You can filter by link type (and direction) and by configuring a JQL. ![image-20240730-093049.png](https://doc.elements-apps.com/__attachments/a_8dcfe25ac48cbb68ec1f5947d7ec5fc6d918328d4d5717cbeccb883edb3bd8bb/image-20240730-093049.png?cb=8ef17629fb3f5f38e5b2edee06a3e792) ### Link types You choose if you want to retrieve only issues with a specific link type (i.e: Blocks, Problem/Incident, ...) and specify a direction (i.e: Causes, Is caused by). This allows you to only focus your working window on relevant issues without being polluted by other linked issues. It can be left empty if no filter on link types is needed. ### Linked Issues Filter In addition to filtering by link type, you can configure a JQL filter to display issues in a specific state or with particular values. This is useful for a more organized display, such as showing only ongoing linked issues or grouping issues by project in different overview tables. If the JQL filter is empty, the table will display the first 50 issues as returned by the Jira search. ### Project whitelist This option is only visible when displaying overviews in **Jira Service Management**. Overviews will only display issues from the Jira projects selected in the whitelist. If this list is left empty, nothing will be displayed. The list of projects available in this option is limited to the projects that the admin configuring the overview has access to. This means that if several different admins configure the same overview, it may lead to different project whitelists, depending on their respective permissions. This option exists to make sure that only data from authorized projects are displayed to your customers through the JSM customer portal. ### Pagination When using a Table display, these issues are paginated by pages of 25. The table displays a maximum of 500 issues (spread across 20 pages). When using the Card display, all issues are listed, up to a maximum of 500 issues. ## Additional fields This option is only available for **Jira Service Management**projects. Selecting this option is meant to solve a [well-known issue](https://jira.atlassian.com/browse/JSDCLOUD-4328) for Jira Service Management portal requests: it allows project admins **to configure read-only issue fields to be shown on the customer's portal**. With this option, fields that are not on the request Creation Screen (such as "Fix versions" or "Due date") can be displayed on the portal. Learn more in a dedicated tutorial: [Show hidden fields in the customer portal](https://doc.elements-apps.com/overview/show-hidden-fields-in-the-customer-portal.md) [Next step: Content configuration](https://doc.elements-apps.com/overview/content.md) --- language: "en" --- # Basic usage ## Context As a Jira administrator, you have just installed Elements Overview on your Jira Cloud instance and you want to make use of it, quickly and efficiently. Why not start with a use case that will help your Support team? Support agents process many tickets every day, and it can get hard for them to keep a history of the problems reported by each user, in order to support them in the most efficient way. With Elements Overview, you can vive them **quick access to tickets raised by a user to better understand the problems they are facing.** Elements Overview can extend information provided in Jira Service Management projects by providing a list of issues reported by the same Reporter. This information is important especially for a Support agent, once they treat a new ticket, to have a better understanding of the user configuration, problems they faced, what was suggested in previous tickets, etc. ... Follow the tutorial to implement the solution. It will result in configuring an overview on the agent side to display issues reported by the current Reporter. ## Tutorial ### Prerequisites * Have at least one Jira Service Management project configured with one Request Type. * Have [Elements Overview](https://go.elements-apps.com/OVC) installed on your instance ### Configuration steps #### 1 - Navigate to the JSM project admin and find Elements Overview You must be a project administrator to configure an overview. Go to your JSM project, click on project settings and find Elements Overview in the apps section. Click on create new [overview](https://doc.elements-apps.com/overview/app-configuration/overviews). ![JSM create an Overview.png](https://doc.elements-apps.com/__attachments/a_7cb4fddd6b7ea6fc8927f2e775ece953ad8e1403b56d7ed900e2d61c123d1477/JSM%20create%20an%20Overview.png?cb=b335ad9f3061985172742475c059b01d) #### 2 - In the display section, select where you want to display your overview The first step is to configure the [display](https://doc.elements-apps.com/overview/app-configuration/overviews/display) of your overview. For JSM projects 2 locations are possible: * Jira issue locations (display the Overview in Jira, on agent side). * JSM issue locations (display the Overview in Portal side). For this use case, as we need to help the support agent by showing issues from same reporter, we chose *Issue panel*. ![JSM Overview Display settings.png](https://doc.elements-apps.com/__attachments/a_5ab9f54fa973a65e334885e06bb980f47b3b36bb6ce01a62074951dab7733382/JSM%20Overview%20Display%20settings.png?cb=3f1c08ee56272993f5b396f388645f5c) #### 3 - In the Focus section, configure which issues the overview will display There are [2 modes](https://doc.elements-apps.com/overview/app-configuration/overviews/focus) available to configure which issues will be listed in the Overview. As the need for this use case is to retrieve issues reported by the current issue Reporter, we'll go with ***Dynamic JQL*** mode as we'll have access to current issue different values that we can use to build a dynamic JQL filter. For example, get issues where the current project and the reporter is the current issue reporter. ![JSM Overview Focus.png](https://doc.elements-apps.com/__attachments/a_ca5230e60122969d81d7baf2e4196c1689a23d3b825645425955ed994c4d4580/JSM%20Overview%20Focus.png?cb=09254dd77d5991857d08be99978ccafe) **Pro-tip:** To exclude the recently submitted issue from the retrieved issues, you can adjust the JQL query as below: project = ${issue.project.key} and reporter=${issue.reporter} and key !=${issue.key} #### 4 - In the Content section, configure any field to be displayed After configuring display and focus, the last step is to configure the [card layout](https://doc.elements-apps.com/overview/app-configuration/overviews/content). Under ***Configure table layout*** *section,* youcan: * Select the Jira custom fields you want to display in the Overview * Reorder the selected fields in the way you want it by simply dragging and dropping them. * Rename some fields in the overview for a better understanding during the overview visualisation (in this example, Assignee was renamed as *Responsible)* Finally, under ***Preview***section, you can select an issue that matches the display conditions set in this Overview, click the "Preview" button to see how the Overview will looks like. ![JSM Overview Content.png](https://doc.elements-apps.com/__attachments/a_622f46864eb6464609b522b305e3647b8a3c5700dca09ff8e282d8759e7d487b/JSM%20Overview%20Content.png?cb=938caa4929ed4adf8034cf0086b85f39) #### 5 - Final result From a Jira issue that matches the Display conditions of the created Overview, add the Overview in the Issue panel by clicking on "Elements Overview" and all issue from same reporter will be displayed will be displayed on the agent side (no Overview will be displayed on Portal side)! ![JSM Overview final result.png](https://doc.elements-apps.com/__attachments/a_e8404edc6a030851937ab9b1a882ddbe72e0b8748ab1826941f3cb2c63180dbb/JSM%20Overview%20final%20result.png?cb=b2cadaac508aeac5bfa9c5f6cf639f15) ![:yellow_star:](https://doc.elements-apps.com/__attachments/a_5e9d07641938b5d282ffd28a0db7f2c41b5fcb64b5545174b73d8aef03282b92/atlassian-yellow_star?cb=831fb7045d4350895482d56d29d4258f) [Try Elements Overview now](https://go.elements-apps.com/OVC). --- language: "en" --- # Getting started **Elements Overview** is an app for Jira Cloud. Its goal is to empower Jira users and customers by **displaying related issues in issue views or request** **portal.** ![elements-overview.png](https://doc.elements-apps.com/__attachments/a_db6da89b5fdaa1c1a4fbde115d6375c1636e58fee2310822abccce07254dd4b3/elements-overview.png?cb=10c794277bb91c9827c2ce2bac74f1bb) In the pages below, you will find a quick look at the main features of our app : * [Introduction to Elements Overview](https://doc.elements-apps.com/overview/introduction-to-elements-overview.md) * [Installation guide](https://doc.elements-apps.com/overview/installation-guide.md) * [Basic usage](https://doc.elements-apps.com/overview/get-issues-from-the-same-reporter.md) --- language: "en" --- # Help and Support Here, you can access a comprehensive FAQ section that provides answers to commonly asked questions, helping you resolve issues quickly and efficiently. If you need more personalized assistance, go to the "*Contact Our Team*" section! * [FAQs](https://doc.elements-apps.com/overview/faqs.md) * [Migration hub](https://doc.elements-apps.com/overview/migrating-from-server-dc.md) * [Contact our team](https://doc.elements-apps.com/overview/contact-our-team.md) --- language: "en" --- # How-to…? Use these short step-by-step guides to **learn everything there is to know** about Elements Overview. How to... * [See related tickets of customer requests in portal](https://doc.elements-apps.com/overview/see-related-tickets-of-customer-requests-in-portal.md) * [See subtasks of the current issue](https://doc.elements-apps.com/overview/see-sub-tasks-of-the-current-issue.md) * [Show hidden fields in the customer portal](https://doc.elements-apps.com/overview/show-hidden-fields-in-the-customer-portal.md) * [Display work items with the same Affected services](https://doc.elements-apps.com/overview/display-work-items-with-the-same-affected-services.md) * [Enhance customer experience with Sentiment-driven insights in Jira Service Management](https://doc.elements-apps.com/overview/enhance-customer-experience-with-sentiment-driven-.md) --- language: "en" --- # Installation guide Elements Overview can be installed from the Atlassian Marketplace or directly from a Jira Cloud instance. ## Installing from the Atlassian marketplace 1 - Go to the Elements Overview page on the Atlassian Marketplace. 2 - Click on the yellow **Try it free** button. 3 - Under "Cloud", click on the **Get it now** button. 4 - On the following screen, select the Jira instance where you want to install Elements Overview and click on **Install app.** 5 - Finally, after being redirected to the target Jira instance, click on **Get it now**. 6 - Don't forget to **Allow**permissions of the application ## Installing from a Jira Cloud instance 1 - Go to the Jira instance where you want to install Elements Overview. 2 - Go to "Apps \> Find new apps" in the top menu. 3 - Search for "Elements Overview". 4 - Click on "Elements Overview". 5 - Click on the **Get app** button. 6 - Click on the **Get it now** button. 7 - Don't forget to **Allow**permissions of the application ## Pricing For more information about this topic, please read our [FAQs](https://doc.elements-apps.com/overview/faqs.md). --- language: "en" --- # Introduction to Elements Overview Elements Overview is an **enhanced issue vizualization app** designed for Jira Cloud. To fulfil its goal of revolutionizing **how you manage and interact with related issues**, it provides intuitive tools to display and edit snippets of crucial information from connected issues directly within the context of your current work. ![elements-overview-3.png](https://doc.elements-apps.com/__attachments/a_e0e655c078bdc2125694add2043ca57fe0c939df6bbf1f874fbf82a175225e28/elements-overview-3.png?cb=09db422cca2cde79155e37d8831aa14d) ## Key features ### Customizable data display Tailor what information to showcase and where within Jira. Whether you prefer to view related issue details in an issue panel or directly in the glance view, Elements Overview allows full customization. For instance, easily display due dates, statuses, or other custom fields from linked Jira issues, providing comprehensive context without navigating away. ### Enhanced user context Empower software teams by controlling the depth of information visible from Jira, ensuring users have the relevant insights needed for informed decision-making and collaboration. ### Improved customer transparency Within Jira Service Management, when customer requests require escalation to other teams, transparency is crucial. Elements Overview enables you to display essential details such as expected fix versions or current statuses directly on the customer portal. ![elements-overview-2.png](https://doc.elements-apps.com/__attachments/a_46f60e0127948432ea0695d7003085dc7735c656ac88c15842b11cc4fb0066f3/elements-overview-2.png?cb=99fe01713445e32cf83b4d2dade59d5e) This transparency enhances customer satisfaction and reduces confusion by keeping all stakeholders informed without compromising privacy or security. ### Efficient issue management Simplify issue handling by editing related issues directly from the current task. This eliminates the need for constant context switching, saving valuable time and improving workflow efficiency. Perform bulk edits seamlessly, streamlining operations and ensuring consistency across linked issues. ## Use cases that might speak to you ### For development teams Agile teams benefit from real-time updates on linked issues, facilitating sprint planning and execution. ![elements-overview-1.png](https://doc.elements-apps.com/__attachments/a_928131d30927f3d24bb73c0fe88cddf4c14e10ac7762638a26f8b19ce4d71b05/elements-overview-1.png?cb=a04005ea0aea40c0864361f089a97b11) ### For Service Management Service desks leverage improved visibility into escalated issues, providing comprehensive support and timely updates to customers without manual intervention required. ### For project managers Gain a holistic view of project progress by aggregating and displaying critical information across interconnected issues. ![:yellow_star:](https://doc.elements-apps.com/__attachments/a_5e9d07641938b5d282ffd28a0db7f2c41b5fcb64b5545174b73d8aef03282b92/atlassian-yellow_star?cb=831fb7045d4350895482d56d29d4258f) **Intrigued?** If this short introduction has stirred your imagination, why not give it a try? [**Try Elements Overview for free**](https://marketplace.atlassian.com/apps/1229459/elements-overview-custom-display-for-related-issues?hosting=cloud&tab=overview&utm_source=elements-apps&utm_medium=documentation&utm_campaign=gettingstarted) --- language: "en" --- # Migration hub Elements Overview is a standalone cloud application originally offered **as the Data Panels feature of Copy \& Sync on premise**. At Elements, we're fully committed to making your path from Data Center to Cloud as seamless as possible. We're working hard to ensure that in the coming months the value you can get from the Cloud application of Elements Copy \& Sync On Premise data panel feature matches and even exceeds the one you currently get with on Data Center. While this is our goal, we know that today there's a gap in functionality between our Data Center feature and our Cloud app. Most of the key functionalities of the Data Center app will be implemented, however, due to functional differences between the Cloud and Server platforms, we are not able to deliver 1:1 feature parity between the environments. Rest assured, the Elements team is working hard to ensure our Elements Copy \& Sync Data Center users find similar functionality in Cloud and enjoy an excellent experience with our Cloud app. ## Migration path Steps to follow to migrate from Jira Data Center to Jira Cloud: * Verify that all the needed features exist on Jira Cloud (see the tables below) * Install Elements Overview on your Jira Cloud instance * Manually create the overviews If you have any doubt or question **contact our support team** . We'll assist you in your migration. ## Features comparison with Data Panels OP | **Feature group** | **Feature** | **Implementation status** | **Comment** | |---------------------|-----------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------| | Data Panel Location | Display in issue Yes/No | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | | | Location in issue | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Display in boards | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Display in JSM | ![warning](https://doc.elements-apps.com/__attachments/a_138f5d8c08d7932eceb570970c5f03adcb224b5b08bf4662a9588720919c73e0/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Partially available | | | Display conditions | JQL display filter | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | Native Jira Panels | Hide panels | ![warning](https://doc.elements-apps.com/__attachments/a_138f5d8c08d7932eceb570970c5f03adcb224b5b08bf4662a9588720919c73e0/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) Not possible | | | Issues to display | Linked issues filter | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Link type | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | Table | Show headers | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | | | Reorder columns | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Custom headers | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Custom footers | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | | | Link to issue | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | Issues linking | Link issues | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | | Operation buttons | Set Copy\&Sync operation (recipe) | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | | Issue operation | Edit remote issue | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Delete remote issue | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | | | Transition issue | ![check mark](https://doc.elements-apps.com/__attachments/a_7e4af77759ff9baa9fec0949269956226393a5a151d46d359c676882f3ac5553/atlassian-check_mark?cb=a10212e1c1021c5194f7535b6843f955) Available | | | | Delete link | ![cross mark](https://doc.elements-apps.com/__attachments/a_367baaf1f138236a346c2b3ebac47b2245b1967eb12916c444426fc2a9cadb64/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) Unavailable | | ## More resources to help you plan your migration Atlassian has published a dedicated [Migration Resource Center](https://www.atlassian.com/migration/cloud) with step-by-step guides, free tools, and dedicated support to assist you on your journey to Cloud. Have specific questions about our app? Please [reach out to our support team](https://support.elements-apps.com/page/cloud-support?createRequest=true&portalId=11&requestTypeId=129) - they're here to help and advise. --- language: "en" --- # Overview options In the pages below, you will find more information about the extended options provided by Elements Overview. * [Calculated footers for numeric fields](https://doc.elements-apps.com/overview/calculated-footers-for-numeric-fields.md) * [Display issues hierarchy in overviews](https://doc.elements-apps.com/overview/display-issues-hierarchy-in-overviews.md) * [Display overviews issues progress](https://doc.elements-apps.com/overview/display-overviews-issues-progress.md) * [Bulk edit overviews fields](https://doc.elements-apps.com/overview/bulk-edit-overviews-fields.md) --- language: "en" --- # Overviews An overview is a **customizable**way of displaying only **relevant**linked issues on the current issue. In addition, it's possible to edit any displayed custom fields, following the right current user's permission You can configure one location by overview from the following list but you can configure multiple overviews for one project. ## Jira Software and Jira Service Management Agent locations Click here to expand ### Issue Glance view ![image2022-10-27_17-56-25.png](https://doc.elements-apps.com/__attachments/a_dd51d6d8cc8446382d52cad541ab3f08b7357f5d4129bcee321ccb542be4a542/image2022-10-27_17-56-25.png?cb=72d99c40c1235c1130f79f2cb276f78f) #### Issue Panel view ![image2022-10-27_17-52-56.png](https://doc.elements-apps.com/__attachments/a_274826d6fb93b4412a1601256d0eaa6b750d1a46c9be576ac088a101b500f984/image2022-10-27_17-52-56.png?cb=3d2667340031ef0f368a79e1b0b38c55) #### Issue Activity view ![image2022-10-27_18-1-40.png](https://doc.elements-apps.com/__attachments/a_c60854ede87fee5c032ca6e4d89382381391da799cc5bdb47bb2d3f0c24b553e/image2022-10-27_18-1-40.png?cb=e2154ae6b9e519a4a2794bbbd62cf076) ### Jira Service Management locations Click here to expand #### Request details ![image2022-10-27_18-13-39.png](https://doc.elements-apps.com/__attachments/a_3b54d4254d8d7701607fdb119639d56b177fa80532b7b99967e945276fcfe890/image2022-10-27_18-13-39.png?cb=af293927e7360ca6466a8a047e300f7e) #### Request panels ![image2022-10-27_18-18-39.png](https://doc.elements-apps.com/__attachments/a_72af3705b60a40a6e1730be44f37d712d89dc994563d9ca5ed63df70aaa4991f/image2022-10-27_18-18-39.png?cb=3162d8c78643cd524f6e7928426fb760) ### How to configure an overview In the following pages, you will find the full explanation of the 3-part overview configuration. * [Display](https://doc.elements-apps.com/overview/display.md) * [Focus](https://doc.elements-apps.com/overview/focus.md) * [Content](https://doc.elements-apps.com/overview/content.md) * [Advanced options](https://doc.elements-apps.com/overview/advanced-options.md) --- language: "en" --- # Security * [2024/08/22 - Security improvements](https://doc.elements-apps.com/overview/2024-08-22-security-improvements.md) * [2024/10/10- P3 Security Issue](https://doc.elements-apps.com/overview/2024-10-10-p3-security-issue.md) --- language: "en" --- # Security & Privacy The security of our apps and the data privacy of our customers are of utmost importance to us at Elements. We are constantly collaborating with Atlassian and investing significant efforts to have Elements Overview meet the highest security standards in the Atlassian ecosystem. Additionally, we are compatible with **Data Residency** with any realm you select. You can find any useful information regarding data storage, security, compliance, and privacy on our [Marketplace listing](https://marketplace.atlassian.com/apps/1229459/elements-overview-custom-display-for-related-issues?hosting=cloud&tab=privacy-and-security). We are enrolled in the [Atlassian Marketplace Cloud Security Program](https://www.atlassian.com/trust/marketplace) and Elements Pulse is [Cloud Fortified](https://www.atlassian.com/blog/add-ons/introducing-cloud-fortified), which means we participate in Atlassian's bug bounty, ensure performance at scale by automated infrastructure deployment and load testing, and respond within 1 day (24 hours) to critical customer support issues, 5 days a week. Cloud Fortified is the highest level of security recognized by Atlassian for Marketplace Partners. For details about Atlassian security programs: * [Marketplace Security Bug Bounty Program](https://developer.atlassian.com/platform/marketplace/marketplace-security-bug-bounty-program/) * [Vulnerability Disclosure Program](https://developer.atlassian.com/platform/marketplace/vdp/) In addition to responding to individual security questionnaires and surveys from our customers, we also provide the following compliance and security information to all our customers: * [Our Trust Center](https://trust.elements-apps.com/) If you have any questions about our security commitments, please contact us by [opening a support request](https://support.elements-apps.com/). --- language: "en" --- # See related tickets of customer requests in portal ## Problem: Lack of visibility on related or escalated tickets for customers on JSM portal Many organizations manage their IT service operations through Jira Service Management. Customers can raise incidents, ask for new features or request access to a new service. Without access to linked issues, customers may face several challenges that can impact their ability to track escalated issues or change requests. When customers are not able to view linked issues in the customer portal, they may struggle to get a complete picture of the status and progress of their requests. This lack of visibility can lead to frustration and confusion, as customers may not understand the relationships between different tasks and the impact they have on their request. ## Result: Provide an overview of related issues directly on the portal Elements Overview empowers Jira Service Management customers by giving them valuable information about what is blocking their tickets or what is related to their request. Follow the tutorial to implement the solution. It will result in configuring an overview on the customer's portal displaying out of reach issues such as escalated problems or related change requests. ## Tutorial ### Prerequisites * Have at least one Jira Service Management project configured with portal access * Users that raise requests must be at least customers of the JSM project * Have [Elements Overview](https://go.elements-apps.com/OVC) installed on your instance ### Configuration steps #### 1 - Navigate to the JSM project admin and find Elements Overview You must be a project administrator to configure an overview. Go to your JSM project, click on project settings and find Elements Overview in the apps section. Click on create new [overview](https://doc.elements-apps.com/overview/app-configuration/overviews). ![image2023-6-1_11-4-11.png](https://doc.elements-apps.com/__attachments/a_67aa9298a09df3f1f534bf47b010d6ccc1c5b19d7f1a542ad1eff1b08a56968d/image2023-6-1_11-4-11.png?cb=7edb4f41c1738f3afda60f14391fd02d) #### 2 - In the display section, select where you want to display your overview The first step is to configure the [display](https://doc.elements-apps.com/overview/app-configuration/overviews/display) of your overview. For JSM projects 2 additional options are added under "JSM issue locations": * Request panel (the right part of a request) * Request details (under portal activity section) For this use case, we chose Request panel. **Pro-tip:** You can use additional display conditions if you want to restrict the display of an overview to issues matching the JQL. ![image2023-6-1_11-5-53.png](https://doc.elements-apps.com/__attachments/a_afe79c7125ee86f2bb91d2b5b34605f740565eff84a6ac42a7059b46506f03de/image2023-6-1_11-5-53.png?cb=91724832f978f25009338d3a37e9406a) #### 3 - In the Focus section, configure which issues the overview will display You'll be prompted to choose between [2 modes](https://doc.elements-apps.com/overview/app-configuration/overviews/focus): * **Dynamic JQL:** this mode allows you to configure a JQL filter using, if needed, current issue values to retrieve and display relevant issues * **Linked issues:** Issues linked to the current issue are proposed, they can be filtered by type or JQL For example, select Linked issues and select all issues that block the request ticket and are not in the status category "Done". ![image2023-6-1_11-7-57.png](https://doc.elements-apps.com/__attachments/a_853ec5b0df7d6e0ef7254fd6316a9dd645a023de3587309367096d2255c0c883/image2023-6-1_11-7-57.png?cb=689f25fbaf8a8e705443a3484f80ec8b) #### 4 - In the Content section, configure any field to be displayed After configuring display and focus, the last step is to configure the [card layout](https://doc.elements-apps.com/overview/app-configuration/overviews/content): * Headers: A subset of native Jira fields, that can be showed or hidden * Other fields: Any other compatible fields, that will be displayed one after the other Just click on the headers you want to show or hide (in this example, only Assignee is hidden) and add any field you want. You can reorder them according to their priority. ![image2023-6-1_11-8-31.png](https://doc.elements-apps.com/__attachments/a_25d59fab276710d7229d3e728a46a546dcec7ecbee722fdc8292f752a9907a53/image2023-6-1_11-8-31.png?cb=ea5f4ff575d62d2136816f8fd4286241) #### 5 - Final result ![image2023-6-1_11-10-18.png](https://doc.elements-apps.com/__attachments/a_fc8ded4f6218ef730a7f78992619d80f2d4e2be57b5f0c101e55e249f9acf01a/image2023-6-1_11-10-18.png?cb=ac3bf8592b40d125ea325f6df8f8c0d6) [Try it now](https://go.elements-apps.com/OVC) --- language: "en" --- # See subtasks of the current issue ## **Problem: Having multiple issues linked to the ticket but the need is to monitor its subtasks** Onboarding process implies on several steps that will be translated in multiple tasks and even sub tasks in the HR project; however, we might need to monitor certain ones like the Sub tasks and have them displayed in a dedicated panel with possibility to update many fields directly from that panel. ## **Result: Provide an Overview of current issue subtasks** Elements Overview empowers Jira projects user experience by giving them valuable information about what is blocking their tickets or what is related to their request. Follow the tutorial to implement the solution. It will result in configuring an overview on the agent side to display current issue Sub tasks. ## **Tutorial** ### Prerequisites * Have at least one Jira Software project configured with Sub task issue type. * Have [Elements Overview](https://go.elements-apps.com/OVC) installed on your instance ### Configuration steps #### 1 - Navigate to the Jira Software project admin and find Elements Overview You must be a project administrator to configure an overview. Go to your JSM project, click on project settings and find Elements Overview in the apps section. Click on create new [overview](https://doc.elements-apps.com/overview/app-configuration/overviews). ![2024-01-23 14_07_53-Elements Overview - Elements Apps Support.png](https://doc.elements-apps.com/__attachments/a_4f96f75896ce06712c249343604d48c57a5e5e2b6468db0e7aa8f0061cce9f9c/2024-01-23%2014_07_53-Elements%20Overview%20-%20Elements%20Apps%20Support.png?cb=1915488c639a914d9abd8ecb531b3613) #### 2 - In the display section, select where you want to display your overview The first step is to configure the [display](https://doc.elements-apps.com/overview/app-configuration/overviews/display) of your overview. * Issue display conditions: You can use additional display conditions if you want to restrict the display of an overview to issues matching the JQL. For this use case, we'll restrict this Overview for certain issue type (it's a Standard issue type, not a Sub task) * Overview display context: Specify the Overview location in the Jira issue. For this use case, we'll chose *Issue panel.* ![Elements Overview display.png](https://doc.elements-apps.com/__attachments/a_7166d37d4c8fe3af5aa6c96dc59cf56732c3df5d475884d32fb46163bf651834/Elements%20Overview%20display.png?cb=3d83f5c678a00396fba263759bbae7e4) #### 3 - In the Focus section, configure which issues the overview will display There are [2 modes](https://doc.elements-apps.com/overview/app-configuration/overviews/focus) available to configure which issues will be listed in the Overview. As the need for this use case is to retrieve the Sub tasks of the current issue, we'll go with ***Dynamic JQL*** mode as we'll have access to current issue different values that we can use to build a dynamic JQL filter. For example, get issues where the issue type is Sub task (not necessary the Sub-Task issue type available in Jira but any other issue type created as Sub-Task like *Procurement, Internal task in the below example)*and their parent is the current issue key. ![Elements Overview Focus.png](https://doc.elements-apps.com/__attachments/a_7c1c5de82de1a3acd95d4d03b8d0ba1713f350bd33e96d31c1b502b29fadf31b/Elements%20Overview%20Focus.png?cb=957c6a9dfb09f341ba11aaf7152fd2aa) #### 4 - In the Content section, configure any field to be displayed and test the Overview After configuring display and focus, the last step is to configure the [card layout](https://doc.elements-apps.com/overview/app-configuration/overviews/content). Under ***Configure table layout*** *section,* youcan: * Select the Jira custom fields you want to display in the Overview * Reorder the selected fields in the way you want it by simply dragging and dropping them. * Rename some fields in the overview for a better understanding during the overview visualisation (in this example, Assignee was renamed as *Responsible)* Finally, under ***Preview***section, you can select an issue that matches the display conditions set in this Overview, click the "Preview" button to see how the Overview will looks like. ![Elements Overview Content.png](https://doc.elements-apps.com/__attachments/a_39310864952df8688388a874c446335fb18109fcb3c6c531b7e33e21bd79b66a/Elements%20Overview%20Content.png?cb=b7c1c8922f9172221c45a3166ffd1114) #### 5 - Final result From a Jira issue that matches the Display conditions of the created Overview, add the Overview in the Issue panel by clicking on "Elements Overview" and all Sub tasks related to the current issue will be displayed! Not only that, you can update those Sub Tasks (transition issue, set Due Date, ...) directly from within the Overview without the need to browse them one by one. ![Elements Overview Issue Panel.png](https://doc.elements-apps.com/__attachments/a_6804cc8830725d99851b71b6e347046e2773e8318386746ab6bdaf86aa30f06c/Elements%20Overview%20Issue%20Panel.png?cb=687285b2ebb55828cd0d6d7cfcd75918) [Try Elements Overview now](https://go.elements-apps.com/OVC) --- language: "en" --- # Show hidden fields in the customer portal ## Context ### The Need Enable customers to access additional information on the JSM portal that is not available during request creation. ### The Solution Use Elements Overview to display fields like **Due Date** and **Fix Versions** to customers on the JSM portal. ### Related Use Case In a typical service management scenario, customers often need to track the progress of their requests, including when a bug will be fixed and in which software version. However, certain fields, such as **Due Date** and **Fix Versions**, are only visible to agents because they are not part of the request creation screen. By using Elements Overview, these fields can be displayed to customers, enhancing transparency and communication. This feature is particularly beneficial for project managers and support teams who need to keep stakeholders informed about timelines and software updates, while removing the need for back-and-forth exchanges between agent and customer. ## Tutorial This tutorial will guide you through the process of displaying the **Due Date** and **Fix Versions** fields to customers on the JSM portal, even if these fields are not part of the request creation screen. ### Prerequisites Ensure the following conditions are met before proceeding: * At least one Jira Service Management project is configured with portal access. * Users raising requests must be customers of the JSM project. * **Elements Overview** is installed on your instance. ### Configuration Steps #### 1. Access Elements Overview As a project administrator, navigate to your JSM project settings and locate **Elements Overview** in the Apps section. #### 2. Create a New Overview Click on the **Create New Overview** button and give a name to your overview. ![image-20241025-085245.png](https://doc.elements-apps.com/__attachments/a_e5159d5d8e4194fba21f5ef630a0cb44fcc1f0ae326a4c8ea21cb8ba1dec5bf1/image-20241025-085245.png?cb=702a280a99cb251acbcfa219b5902286) #### 3. Configure Display Location Configure the Display of your overview. For this Jira Service Management use case, select one of the two available JSM issue locations. In this example, choose the **Request Panel** to display the overview in the right column of the request. ![image-20241025-085351.png](https://doc.elements-apps.com/__attachments/a_c7b2f3fbe26252d8b8e2fb463ab44acb6db5ee62fa93f9295832b9b38ea7cf90/image-20241025-085351.png?cb=3cebf7c6626703f3cf15b759a59cd23d) #### 4. Set Up the Focus Section Set up the Focus section to configure which issues the overview will display. Select the **Additional Issue Fields** option to display fields from the current request. ![image-20241025-085454.png](https://doc.elements-apps.com/__attachments/a_20d1b98fc661eb4a4589621a12610a13412980b1913dc0afcec3af442a1787ed/image-20241025-085454.png?cb=05c1fc98eaf2b904415b12ba65a34a72) #### 5. Configure Content Section In the Content section, configure the fields you want to display. Use the **Add Another Field** select list to add the **Due Date** and **Fix Versions** fields. ![image-20241025-085543.png](https://doc.elements-apps.com/__attachments/a_5482f4c704b28069507d71d8a7623edaf0f3f6cb59ff48b2c0b5d9ea15b458e4/image-20241025-085543.png?cb=7ce7af1af9f0ee9ecbe5b71d7d1e8382) #### 6. Save the Overview Once configured, click on the **Save** button. The overview will be ready to use. ### Results In this tutorial, you configured Elements Overview to display the **Due Date** and **Fix Versions** fields to customers on the JSM portal. This setup allows customers to view important information as soon as agents update these fields. ![image-20241025-090338.png](https://doc.elements-apps.com/__attachments/a_af96e649c3c88ec76fec7a1af07aef7c6447276c906ade0bfa97a21f16a7b670/image-20241025-090338.png?cb=82f0daeac819f0039bd3814b0778b332) This enhancement improves the customer experience by providing transparency and timely updates, which are crucial in service management scenarios where communication and information sharing are key. For any questions or feedback, please visit our [support portal](https://support.elements-apps.com/). **Try Elements Overview for free on the** [**Atlassian Marketplace**](#)**.** --- language: "en" --- # Tutorials Explore our step-by-step guides on various 'how-to' topics. This space is designed to help you navigate Elements Overview with ease, offering detailed instructions on everything from basic setups to advanced functionalities. * [Video tutorials](https://doc.elements-apps.com/overview/video-tutorials.md) * [How-to...?](https://doc.elements-apps.com/overview/how-to.md) --- language: "en" --- # User guides You'll find here detailed instructions for Jira administrators on how to configure and manage the app. [App configuration](https://doc.elements-apps.com/overview/app-configuration.md) * [Compatible field types](https://doc.elements-apps.com/overview/compatible-field-types.md) --- language: "en" --- # Video tutorials This page lists video guides or interactive demos for our main use cases. * [See related tickets of request on customer portal](https://youtu.be/_1Xlrcf9E-8?si=g_yRm0flOwkvxxTG) * [See related incidents in the global problem](https://youtu.be/2zrXpshP-6I?si=w8h9abdGdEc_8pAh) * [Onboarding new employees with Jira](https://youtu.be/wYHeZWHv5Mw?si=anSAxURHrHJFIGWJ) --- language: "en" --- # Elements Connect ## Elements Connect Bring your external data inside Jira on Data Center. [Get Started](https://doc.elements-apps.com/elements-connect/getting-started-guide.md) ### Highlights * #### [Datasources configuration](https://doc.elements-apps.com/elements-connect/datasources-configuration.md) Elements Connect datasources definitions can be configured from Connect administration page, in the "Datasource" section. * #### [Field configuration](https://doc.elements-apps.com/elements-connect/field-configuration.md) Elements Connect fields definitions can be configured from Connect administration page, in the "Fields" section. * #### [Migrating to Jira Cloud](https://doc.elements-apps.com/elements-connect/migrating-to-jira-cloud.md) Welcome to the Elements Connect migration hub! Discover how to migrate to Jira Cloud. ### Documentation * #### [Getting Started Guide](https://doc.elements-apps.com/elements-connect/getting-started-guide.md) * [Discover Elements Connect administration](https://doc.elements-apps.com/elements-connect/discover-elements-connect-administration.md) * [Create Elements Connect custom field](https://doc.elements-apps.com/elements-connect/create-elements-connect-custom-field.md) * [Configure Elements Connect custom field](https://doc.elements-apps.com/elements-connect/configure-elements-connect-custom-field.md) * [Display Elements Connect field in Jira issues](https://doc.elements-apps.com/elements-connect/display-elements-connect-field-in-jira-issues.md) * [Go further with Elements Connect](https://doc.elements-apps.com/elements-connect/go-further-with-elements-connect.md) * #### [Administration Guide](https://doc.elements-apps.com/elements-connect/administration-guide.md) * [Configuration](https://doc.elements-apps.com/elements-connect/configuration.md) * [Integrations](https://doc.elements-apps.com/elements-connect/integrations.md) * [Upgrade/Downgrade Guide](https://doc.elements-apps.com/elements-connect/upgrade-downgrade-guide.md) * [Backup \& Restore](https://doc.elements-apps.com/elements-connect/backup-restore.md) * [Improve performances](https://doc.elements-apps.com/elements-connect/improve-performances.md) * [2 more pages](https://doc.elements-apps.com/elements-connect/administration-guide.md) * #### [User Guide](https://doc.elements-apps.com/elements-connect/user-guide.md) * [Edit an Elements Connect field](https://doc.elements-apps.com/elements-connect/edit-an-elements-connect-field.md) * [Use an Elements Connect field in search](https://doc.elements-apps.com/elements-connect/use-an-elements-connect-field-in-search.md) * [Display Elements Connect field in Dashboard](https://doc.elements-apps.com/elements-connect/display-elements-connect-field-in-dashboard.md) * #### [API Guide](https://doc.elements-apps.com/elements-connect/api-guide.md) * [Java API](https://doc.elements-apps.com/elements-connect/java-api.md) * [Elements Connect REST API](https://doc.elements-apps.com/elements-connect/elements-connect-rest-api.md) * [Jira REST API](https://doc.elements-apps.com/elements-connect/jira-rest-api.md) * [Storage format](https://doc.elements-apps.com/elements-connect/storage-format.md) * #### [Troubleshooting](https://doc.elements-apps.com/elements-connect/troubleshooting.md) * [Autocomplete - Datasource results do not show up in an autocomplete field when using $userInput](https://doc.elements-apps.com/elements-connect/autocomplete-datasource-results-do-not-show-up-in-.md) * [Cache - Eh107CacheManager is closed](https://doc.elements-apps.com/elements-connect/cache-eh107cachemanager-is-closed.md) * [Dashboard - Elements Connect fields values not displayed in Dashboard Charts](https://doc.elements-apps.com/elements-connect/dashboard-elements-connect-fields-values-not-displ.md) * [Dashboard - HTML tags are not evaluated when an Elements Connect is displayed in a statistical gadget](https://doc.elements-apps.com/elements-connect/dashboard-html-tags-are-not-evaluated-when-an-elem.md) * [Database datasource - "Dangerous use of multiple connections" on local database](https://doc.elements-apps.com/elements-connect/database-datasource-dangerous-use-of-multiple-conn.md) * [28 more pages](https://doc.elements-apps.com/elements-connect/troubleshooting.md) * #### [Tutorials \& Examples](https://doc.elements-apps.com/elements-connect/tutorials-examples.md) * [Demo use cases: examples of Elements Connect fields set-up](https://doc.elements-apps.com/elements-connect/demo-use-cases-examples-of-elements-connect-fields.md) * [Tutorials: learn how to configure Elements Connect](https://doc.elements-apps.com/elements-connect/tutorials-learn-how-to-configure-elements-connect.md) * #### [Customer stories and Use Cases](https://doc.elements-apps.com/elements-connect/customer-stories-and-use-cases.md) * [How to populate Jira fields with data from any external source](https://doc.elements-apps.com/elements-connect/how-to-populate-jira-fields-with-data-from-any-ext.md) * [External data in Jira fields: low code connector vs homemade script](https://doc.elements-apps.com/elements-connect/external-data-in-jira-fields-low-code-connector-vs.md) * [Making the ticket creation experience more conversational in Slack](https://doc.elements-apps.com/elements-connect/making-the-ticket-creation-experience-more-convers.md) * [How Velocity helps you do more with Elements Connect](https://doc.elements-apps.com/elements-connect/how-velocity-helps-you-do-more-with-elements-conne.md) * [Look back at the Atlassian Summit 2019: Jira Service Desk and apps](https://doc.elements-apps.com/elements-connect/look-back-at-the-atlassian-summit-2019-jira-servic.md) * [7 more pages](https://doc.elements-apps.com/elements-connect/customer-stories-and-use-cases.md) * #### [FAQ](https://doc.elements-apps.com/elements-connect/faq.md) * [Are the Elements Connect fields compatible with Jira's import/export?](https://doc.elements-apps.com/elements-connect/are-the-elements-connect-fields-compatible-with-ji.md) * [Can Elements Connect fields be manipulated from a ScriptRunner Behaviours script?](https://doc.elements-apps.com/elements-connect/can-elements-connect-fields-be-manipulated-from-a-.md) * [Can I get data from SOAP webservice?](https://doc.elements-apps.com/elements-connect/can-i-get-data-from-soap-webservice.md) * [CSV Import - How to set Elements Connect field when creating issues from a CSV file](https://doc.elements-apps.com/elements-connect/csv-import-how-to-set-elements-connect-field-when-.md) * [How to activate the \~ and !\~ search on Live text fields](https://doc.elements-apps.com/elements-connect/how-to-activate-the-and-search-on-live-text-fields.md) * [17 more pages](https://doc.elements-apps.com/elements-connect/faq.md) * #### [Release notes](https://doc.elements-apps.com/elements-connect/release-notes.md) * [8.0.8 Release note](https://doc.elements-apps.com/elements-connect/8-0-8-release-note.md) * [8.0.7 Release note](https://doc.elements-apps.com/elements-connect/8-0-7-release-note.md) * [8.0.5 Release note](https://doc.elements-apps.com/elements-connect/8-0-5-release-note.md) * [8.0.4 Release note](https://doc.elements-apps.com/elements-connect/8-0-4-release-note.md) * [8.0.6 Release note](https://doc.elements-apps.com/elements-connect/8-0-6-release-note.md) * [145 more pages](https://doc.elements-apps.com/elements-connect/release-notes.md) --- language: "en" --- # 1st workaround ## Working Principle When a value is selected in a Connect field, the key defined in the field configuration is stored in Jira: ![image-2024-1-9_10-3-0.png](https://doc.elements-apps.com/__attachments/a_16b33195545fbddf84af5201573ffb5886d9b09ae3c75b1c8423349385b0b7ca/image-2024-1-9_10-3-0.png?cb=3c09e85423f033b002e947669293759b) It's this data that is migrated by Configuration Manager. The purpose is to update the Connect field key with a value common to both Jira instances: * For a Connect field storing Issue IDs, the field key should be changed to Issue keys. * For a Connect field storing Option IDs (such as a Select List), the field key should be changed to Option names. For example, let's suppose that the source instance contains an issue whose id is "10000" and key is "TEST-1", while the target instance contains an issue whose id is "10001" and the key is "TEST-1". The Issue key is common to both instances and can be used for matching. By updating the Connect field key from Issue ID to Issue key in the source instance, the Connect field values can be migrated correctly by Configuration Manager. Special case: JQL fields In the case of a field connected to the "Jira issues (JQL)" datasource, the Issue ID is stored automatically and it's not possible to change the field key. You need to switch the datasource to "Jira database (SQL)" and then convert the JQL query into an SQL query. ## Steps to follow ### Case 1 - when the field key is an Issue ID Click to expand... #### Context Let's say the Connect field that stores Issue IDs is using the following query: SELECT id, summary FROM jiraissue As follows: ![image-2024-1-9_10-36-12.png](https://doc.elements-apps.com/__attachments/a_33f90ff161230415b3984d970719b909f8f9c32bb68e2ebf948562b7df79e94a/image-2024-1-9_10-36-12.png?cb=2f180deddadea65dd0fffc343920923f) #### A. Edit the Connect field with a temporary configuration First, you need to update the Connect field configuration and change its key from Issue ID to Issue key. To do so, you need to use **$currentCustomfieldValue** to retrieve the old keys, as this variable contains the key currently stored in Jira. Please update your Connect field query as follows*(and keep your initial query somewhere*): #if($currentCustomfieldValue.size() > 0) SELECT CONCAT(p.pkey,'-',j.issuenum), j.summary FROM jiraissue j JOIN project p ON j.project = p.id WHERE j.id IN ($currentCustomfieldValue.stringList()) #else $query.abort() #end This field configuration is temporary until the script below is executed. Its purpose is to retrieve the Issue key corresponding to the returned Issue ID. ![info](https://doc.elements-apps.com/__attachments/a_e9e1822e6dd75bc80b5df71d25a9c27f5a59fd29a63801ab77e514c4834263a1/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) *If the field is connected to the "Jira issues (JQL)" datasource, switch the datasource to "Jira database (SQL)"* #### B. Run a script to update the Connect field keys You then need to run a script to update the Connect field key in all affected issues, based on the temporary Connect field query configured above. Thus, the Issue ID will be changed to the Issue key in all affected issues: Click to expand... log.warn("EC SCRIPT - Script Starts") log.warn("EC SCRIPT --------------------------------------------------") import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.web.bean.PagerFilter import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.event.type.EventDispatchOption def pluginAccessor = ComponentAccessor.getPluginAccessor() def customFieldManager = ComponentAccessor.getCustomFieldManager() def issueManager = ComponentAccessor.getIssueManager() def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser) def searchService = ComponentAccessor.getComponent(SearchService) def user = ComponentAccessor.getJiraAuthenticationContext().getUser() def query = jqlQueryParser.parseQuery("A_VALID_JQL_QUERY") def connectFieldsToBeUpdated = ["customfield_XXXXX","customfield_YYYYY"] log.warn("EC SCRIPT --------------------------------------------------") def results = searchService.search(user, query, PagerFilter.getUnlimitedFilter()) results.getResults().each { myIssue -> log.warn("EC SCRIPT - Updating issue "+myIssue.key) def issueToUpdate = issueManager.getIssueObject(myIssue.key) connectFieldsToBeUpdated.each{connectFieldId -> def connectField = customFieldManager.getCustomFieldObject(connectFieldId) log.warn("EC SCRIPT - connect field: "+connectFieldId) def connectFieldValue = myIssue.getCustomFieldValue(connectField) if(connectFieldValue){ log.warn("EC SCRIPT - => "+connectFieldId+" contains the following value:"+connectFieldValue) connectFieldValue = extracValueFromJson(connectFieldValue) log.warn("EC SCRIPT - => extracted value:"+connectFieldValue) def issueKeys = getIssueKeys(connectFieldValue, issueManager) if(issueKeys){ log.warn("EC SCRIPT - => "+connectFieldId+" has been updated with these issue-keys:"+issueKeys) issueToUpdate.setCustomFieldValue(connectField, '{"keys":['+issueKeys+']}') } else { log.warn("EC SCRIPT - => "+connectFieldId+" has not been updated") } } else { log.warn("EC SCRIPT - => "+connectFieldId+" is empty") } } issueManager.updateIssue(user, issueToUpdate, EventDispatchOption.DO_NOT_DISPATCH, false) log.warn("EC SCRIPT --------------------------------------------------") } log.warn("EC SCRIPT - Script End") def extracValueFromJson(jsonValue){ log.warn("EC SCRIPT - ==> extracValueFromJson - Start") def match = (jsonValue =~ /\[.*?\]/)[0] // extract value thanks to a regex def valueString = match.substring(0, match.length() - 1).substring(1) // remove square brackets valueString = valueString.replace('"','') // remove double quotes log.warn("EC SCRIPT - ==> extracValueFromJson - End") return valueString.tokenize(',') } def getIssueKeys(connectFieldValue, issueManager){ log.warn("EC SCRIPT - ==> getIssueKeys - Start") String issueKeys = "" connectFieldValue.each{ value -> if(value.toString().contains('-') && value.toString().tokenize('-')[1].isNumber()){ log.warn("EC SCRIPT - ===> "+value+" is an issue-key => we don't do anything") } else if(value.toString().isNumber()){ log.warn("EC SCRIPT - ===> "+value+' is an issue-id => we convert the issue-id to issue-key') MutableIssue selectedIssue = issueManager.getIssueObject(value.toLong()) if(selectedIssue){ if(issueKeys.length() <= 0){ issueKeys = '"'+selectedIssue.getKey()+'"' } else { issueKeys += ',"'+selectedIssue.getKey()+'"' } } else { log.warn("EC SCRIPT - ===> The issue '"+value+"' has not been found => we don't do anything") } } else { log.warn("EC SCRIPT - ===> '"+value+"' is not an issue-id or an issue key => we don't do anything") } } log.warn("EC SCRIPT - ==> getIssueKeys - End") return issueKeys } Please replace: * A_VALID_JQL_QUERY with a JQL query returning all the issues to be updated * customfield_XXXXX and customfield_YYYYY with the Connect fields ID You can update multiple Connect fields at the same time, but be aware that this script may cause slowdowns depending on the number of Connect fields being updated and the number of issues returned by the JQL query. This script may take a long time to run based on the scope of affected issues. We thus recommend you to schedule this maintenance operation during non-business hours in order to avoid performance issues #### C. Edit the Connect field with a permanent configuration Once the key has been updated in all affected issues, you can replace your temporary query with a permanent one. Different cases are possibles: ##### Case 01 - SQL field: Click to expand... * Assuming your initial Connect field query (storing Issue IDs) was the following: SELECT id, summary FROM jiraissue ![image-2024-1-9_10-36-12.png](https://doc.elements-apps.com/__attachments/a_33f90ff161230415b3984d970719b909f8f9c32bb68e2ebf948562b7df79e94a/image-2024-1-9_10-36-12.png?cb=2f180deddadea65dd0fffc343920923f) * The new Connect field query (storing Issue keys) should be: SELECT CONCAT(p.pkey,'-',ji.issuenum), ji.summary FROM jiraissue ji INNER JOIN project p ON p.id = ji.project ![image-2024-1-9_10-38-39.png](https://doc.elements-apps.com/__attachments/a_f69050677126e400337b0d8627facae7f1478c4d1cae61ef6d422166efe0cf70/image-2024-1-9_10-38-39.png?cb=645433ecd0268404d97d38583bd475f2) ##### Case 02 - JQL field: Click to expand... * Assuming your field was connected to the "Jira issues (JQL)" and the query was: PROJECT = PM AND ISSUETYPE = Task ![image-2024-1-9_10-52-54.png](https://doc.elements-apps.com/__attachments/a_29bef53a29ae922b8a30678c1105c027570631ec1512a54d2d313970d2de9ccc/image-2024-1-9_10-52-54.png?cb=4acdf7499daae9a65cd030ebd4dbb60d) * The new datasource should be "Jira database (SQL)" and the query should be: SELECT CONCAT(p.pkey,'-',ji.issuenum), ji.summary FROM jiraissue ji INNER JOIN project p ON p.id = ji.project INNER JOIN issuetype it ON it.id = ji.issuetype WHERE p.pkey = 'PM' AND it.pname = 'Task' ![image-2024-1-9_10-56-5.png](https://doc.elements-apps.com/__attachments/a_f13dd86ce1a81179f757738e1cd903f98883f18a6aec3ed5faa7026a5bba5d74/image-2024-1-9_10-56-5.png?cb=103c4e76c20d113be36ca863af94191c) #### D. Migrate with CMJ Your Elements Connect configuration is then ready to be migrated with Configuration Manager. ### Case 2 - when the field key is an Option ID Click to expand... #### Context Let's assume that the Connect field stores option IDs from a custom Select List (whose ID is "10300") and uses the following query: SELECT DISTINCT cfo.id, cfo.customvalue FROM customfieldvalue cfv INNER JOIN customfieldoption cfo ON cfv.stringvalue = cfo.id WHERE cfv.customfield = 10300 As follows: ![image-2024-1-12_15-27-44.png](https://doc.elements-apps.com/__attachments/a_432b1a60f50b2b7f9200bc2e6bb1758b365b732c42434d1db5c3fffd11bde1c2/image-2024-1-12_15-27-44.png?cb=a0fd693f0847841b8bd914b6ae5c78a2) #### A. Edit the Connect field with a temporary configuration First, you need to update the Connect field configuration and change its key from Option ID to Option Name. To do so, you need to use **$currentCustomfieldValue** to retrieve the old keys, as this variable contains the Option ID currently stored in Jira. Please update your Connect field query as follows: #if($currentCustomfieldValue.size() > 0) SELECT DISTINCT cfo.customvalue FROM customfieldvalue cfv INNER JOIN customfieldoption cfo ON cfv.stringvalue = cfo.id WHERE cfv.customfield = 10300 AND cfo.id IN ($currentCustomfieldValue.stringList()) #else $query.abort() #end ![info](https://doc.elements-apps.com/__attachments/a_e9e1822e6dd75bc80b5df71d25a9c27f5a59fd29a63801ab77e514c4834263a1/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) *Please replace 10300 according to your own custom field ID.* This field configuration is temporary until the script below is executed. Its purpose is to retrieve the Option Name corresponding to the returned Option ID. #### B. Run a script to update the Connect field keys You then need to run a script to update the Connect field key in all affected issues, based on the temporary Connect field query configured above. Thus, the Option ID will be changed to the Option Name key in all affected issues: Click to expand... log.warn("EC SCRIPT - Script Starts") log.warn("EC SCRIPT --------------------------------------------------") import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.web.bean.PagerFilter import com.atlassian.jira.event.type.EventDispatchOption def pluginAccessor = ComponentAccessor.getPluginAccessor() def customFieldManager = ComponentAccessor.getCustomFieldManager() def issueManager = ComponentAccessor.getIssueManager() def optionsManager = ComponentAccessor.getOptionsManager() def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser) def searchService = ComponentAccessor.getComponent(SearchService) def user = ComponentAccessor.getJiraAuthenticationContext().getUser() def query = jqlQueryParser.parseQuery("A_VALID_JQL_QUERY") def connectFieldsToBeUpdated = ["customfield_XXXXX","customfield_YYYYY"] def customfieldFieldId = "customfield_10300" def customfield = customFieldManager.getCustomFieldObject(customfieldFieldId) log.warn("EC SCRIPT --------------------------------------------------") def results = searchService.search(user, query, PagerFilter.getUnlimitedFilter()) results.getResults().each { myIssue -> log.warn("EC SCRIPT - Updating issue "+myIssue.key) def issueToUpdate = issueManager.getIssueObject(myIssue.key) connectFieldsToBeUpdated.each{connectFieldId -> def connectField = customFieldManager.getCustomFieldObject(connectFieldId) log.warn("EC SCRIPT - connect field: "+connectFieldId) def connectFieldValue = myIssue.getCustomFieldValue(connectField) if(connectFieldValue){ log.warn("EC SCRIPT - => "+connectFieldId+" contains the following value:"+connectFieldValue) connectFieldValue = extracValueFromJson(connectFieldValue) log.warn("EC SCRIPT - => extracted value:"+connectFieldValue) def fieldConfig = customfield.getRelevantConfig(myIssue) def optionNames = getOptionNames(connectFieldValue, fieldConfig, optionsManager) if(optionNames){ log.warn("EC SCRIPT - => "+connectFieldId+" has been updated with these Option Names:"+optionNames) issueToUpdate.setCustomFieldValue(connectField, '{"keys":['+optionNames+']}') } else { log.warn("EC SCRIPT - => "+connectFieldId+" has not been updated") } } else { log.warn("EC SCRIPT - => "+connectFieldId+" is empty") } } issueManager.updateIssue(user, issueToUpdate, EventDispatchOption.DO_NOT_DISPATCH, false) log.warn("EC SCRIPT --------------------------------------------------") } log.warn("EC SCRIPT - Script End") def extracValueFromJson(jsonValue){ log.warn("EC SCRIPT - ==> extracValueFromJson - Start") def match = (jsonValue =~ /\[.*?\]/)[0] // extract value thanks to a regex def valueString = match.substring(0, match.length() - 1).substring(1) // remove square brackets valueString = valueString.replace('"','') // remove double quotes log.warn("EC SCRIPT - ==> extracValueFromJson - End") return valueString.tokenize(',') } def getOptionNames(connectFieldValue, fieldConfig, optionsManager){ log.warn("EC SCRIPT - ==> getOptionNames - Start") String optionNames = "" connectFieldValue.each{ value -> def name = optionsManager.findByOptionId((Long) value.toLong()) if(optionNames.length() <= 0){ optionNames = '"'+name+'"' } else { optionNames += ',"'+name+'"' } } log.warn("EC SCRIPT - ==> getOptionNames - End") return optionNames } Please replace: * A_VALID_JQL_QUERY with a JQL query returning all the issues to be updated * customfield_XXXXX and customfield_YYYYY with the Connect fields ID * customfield_10300 with the custom Select List ID You can update multiple Connect fields at the same time, but be aware that this script may cause slowdowns depending on the number of Connect fields being updated and the number of issues returned by the JQL query. This script may take a long time to run based on the scope of affected issues. We thus recommend you to schedule this maintenance operation during non-business hours in order to avoid performance issues #### C. Edit the Connect field with a permanent configuration Once the key has been updated in all affected issues, you can replace your temporary query with a permanent one: SELECT DISTINCT cfo.customvalue FROM customfieldvalue cfv INNER JOIN customfieldoption cfo ON cfv.stringvalue = cfo.id WHERE cfv.customfield = 10300 ![info](https://doc.elements-apps.com/__attachments/a_e9e1822e6dd75bc80b5df71d25a9c27f5a59fd29a63801ab77e514c4834263a1/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) *Please replace 10300 according to your own custom field ID.* #### D. Migrate with CMJ Your Elements Connect configuration is then ready to be migrated with Configuration Manager. --- language: "en" --- # 2nd workaround ## Working principle The purpose is to retrieve a piece of data which is common to across both Jira instances, migrate this data to the target instance and update the Connect fields accordingly: * For Issue IDs, the corresponding Issue keys are retrieved * For Option IDs (such as a Select List), the corresponding Option names are retrieved Once this common piece of data is migrated, the Connect fields are updated accordingly. For example, a ticket has id "10000" and key "TEST-1" in the source instance. Once migrated, this ticket has id "10001" and key "TEST-1" in the target instance. The "TEST-1" key is common to both instances and can be used for matching. Based on this key, you can update the Connect field in the target instance by following the procedure below. ## Steps to follow ### From the source Jira instance #### A. Create a custom Text field First, you need to create a custom **Text Field (single line)**: ![image-2024-1-4_14-24-51.png](https://doc.elements-apps.com/__attachments/a_68c09bbfa47ac1756d0f40f906a0bb7fbb0836cf472126091a38c4dd5c5f35ed/image-2024-1-4_14-24-51.png?cb=91908641d63f5cdcdff71e33030e1184) Add this custom field to the projects where the Connect field is used. ![info](https://doc.elements-apps.com/__attachments/a_e9e1822e6dd75bc80b5df71d25a9c27f5a59fd29a63801ab77e514c4834263a1/atlassian-info?cb=feab5cd71111204d6b52545f3027dd0c) *Create one custom Text field for each Connect field.* *Each Connect field affected by the problem must have its own custom field.* #### B. Run a script to copy the Connect field value to the custom Text field Then, you need to run a script (via the Console tab of [Scriptrunner for Jira](https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=datacenter&tab=versions)): 1. If the Connect field stores Issue IDs, this is the script to execute to populate the custom Text field with the corresponding Issue keys: Click to expand... log.warn('EC SCRIPT - Start') import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.web.bean.PagerFilter import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.issue.util.DefaultIssueChangeHolder import com.atlassian.jira.issue.MutableIssue def pluginAccessor = ComponentAccessor.getPluginAccessor(); def plugin = pluginAccessor.getPlugin("com.valiantys.jira.plugins.SQLFeed"); def serviceValueClass = plugin.getClassLoader().loadClass("com.valiantys.nfeed.api.IFieldValueService"); def fieldValueService = ComponentAccessor.getOSGiComponentInstanceOfType(serviceValueClass); def customFieldManager = ComponentAccessor.getCustomFieldManager(); def issueManager = ComponentAccessor.getIssueManager() def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser) def searchService = ComponentAccessor.getComponent(SearchService) def user = ComponentAccessor.getJiraAuthenticationContext().getUser() def query = jqlQueryParser.parseQuery("A_VALID_JQL_QUERY") def connectFieldId = "customfield_XXXXX" def customFieldId = "customfield_YYYYY" def customField = customFieldManager.getCustomFieldObject(customFieldId); def results = searchService.search(user, query, PagerFilter.getUnlimitedFilter()) log.warn("EC SCRIPT - Total issues: ${results.total}") log.warn('EC SCRIPT ----------------------------------------------------------------') results.getResults().each { myIssue -> def connectFieldValue = fieldValueService.getFieldValues(myIssue.key, connectFieldId) if(connectFieldValue){ log.warn("EC SCRIPT - "+connectFieldId+" is not empty in "+myIssue.key) String customFieldValue = "" log.warn("EC SCRIPT - Connect field values:"+connectFieldValue) connectFieldValue.each { value -> MutableIssue selectedIssue = issueManager.getIssueObject(value.toLong()) if(customFieldValue.length() <= 0){ customFieldValue = selectedIssue.getKey() } else { customFieldValue += ','+selectedIssue.getKey() } } customField.updateValue(null, myIssue, new ModifiedValue(myIssue.getCustomFieldValue(customField), customFieldValue), new DefaultIssueChangeHolder()) log.warn("EC SCRIPT - issue "+myIssue.key+" has been updated with:'"+customFieldValue+"'") } else { log.warn("EC SCRIPT - "+connectFieldId+" is empty in "+myIssue.key) } log.warn('EC SCRIPT ----------------------------------------------------------------') } log.warn('EC SCRIPT - End') Please replace: * A_VALID_JQL_QUERY with a JQL query returning all the issues to be updated * customfield_XXXXX with the Connect field ID * customfield_YYYYY with the Custom Text field ID 2. If the Connect field stores Option IDs, this is the script to execute to populate the custom Text field with the corresponding Option names: Click to expand... log.warn('EC SCRIPT - Start') import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.web.bean.PagerFilter import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.issue.util.DefaultIssueChangeHolder def pluginAccessor = ComponentAccessor.getPluginAccessor(); def plugin = pluginAccessor.getPlugin("com.valiantys.jira.plugins.SQLFeed"); def serviceValueClass = plugin.getClassLoader().loadClass("com.valiantys.nfeed.api.IFieldValueService"); def fieldValueService = ComponentAccessor.getOSGiComponentInstanceOfType(serviceValueClass); def customFieldManager = ComponentAccessor.getCustomFieldManager(); def issueManager = ComponentAccessor.getIssueManager() def optionsManager = ComponentAccessor.getOptionsManager() def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser) def searchService = ComponentAccessor.getComponent(SearchService) def user = ComponentAccessor.getJiraAuthenticationContext().getUser() def query = jqlQueryParser.parseQuery("A_VALID_JQL_QUERY") def connectFieldId = "customfield_XXXXX" def customFieldId = "customfield_YYYYY" def customField = customFieldManager.getCustomFieldObject(customFieldId); def results = searchService.search(user, query, PagerFilter.getUnlimitedFilter()) log.warn("EC SCRIPT - Total issues: ${results.total}") log.warn('EC SCRIPT ----------------------------------------------------------------') results.getResults().each { myIssue -> def connectFieldValue = fieldValueService.getFieldValues(myIssue.key, connectFieldId) if(connectFieldValue){ log.warn("EC SCRIPT - "+connectFieldId+" is not empty in "+myIssue.key) String customFieldValue = "" log.warn("EC SCRIPT - Connect field values:"+connectFieldValue) connectFieldValue.each { value -> def optionItem = optionsManager.getAllOptions().find{ (String) it.optionId.toString() == value } if(customFieldValue.length() <= 0){ customFieldValue = optionItem } else { customFieldValue += ','+optionItem } } customField.updateValue(null, myIssue, new ModifiedValue(myIssue.getCustomFieldValue(customField), customFieldValue), new DefaultIssueChangeHolder()) log.warn("EC SCRIPT - issue "+myIssue.key+" has been updated with:'"+customFieldValue+"'") } else { log.warn("EC SCRIPT - "+connectFieldId+" is empty in "+myIssue.key) } log.warn('EC SCRIPT ----------------------------------------------------------------') } log.warn('EC SCRIPT - End') Please replace: * A_VALID_JQL_QUERY with a JQL query returning all the issues to be updated * customfield_XXXXX with the Connect field ID * customfield_YYYYY with the Custom Text field ID This script may take a long time to run based on the scope of affected issues. We thus recommend you to schedule this maintenance operation during non-business hours in order to avoid performance issues #### C. Migrate with CMJ Once the custom Text field has been populated with Issue keys, perform the migration using Configuration Manager and make sure sure that the custom Text field is embedded/included in the migration. #### D. Delete the custom Text field Once the migration has been carried out, delete the custom Text field. ### From the target Jira instance #### A. Run a script to copy the custom Text field value to the Connect field Once the migration has been carried out, you need to run the following script in the target instance (via the Console tab of [Scriptrunner for Jira](https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?hosting=datacenter&tab=versions)): 1. If the Connect field stores Issue IDs: Click to expand... log.warn('EC SCRIPT - Start') import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.web.bean.PagerFilter import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.event.type.EventDispatchOption def pluginAccessor = ComponentAccessor.getPluginAccessor(); def customFieldManager = ComponentAccessor.getCustomFieldManager(); def issueManager = ComponentAccessor.getIssueManager() def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser) def searchService = ComponentAccessor.getComponent(SearchService) def user = ComponentAccessor.getJiraAuthenticationContext().getUser() def query = jqlQueryParser.parseQuery("A_VALID_JQL_QUERY") def connectFieldId = "customfield_XXXXX" def customFieldId = "customfield_YYYYY" def connectField = customFieldManager.getCustomFieldObject(connectFieldId); def customField = customFieldManager.getCustomFieldObject(customFieldId); def results = searchService.search(user, query, PagerFilter.getUnlimitedFilter()) log.warn("EC SCRIPT - Total issues: ${results.total}") log.warn('EC SCRIPT ----------------------------------------------------------------') results.getResults().each { myIssue -> if(myIssue.getCustomFieldValue(customField)){ def customFieldValues = myIssue.getCustomFieldValue(customField).toString().split(',') log.warn("EC SCRIPT - "+customFieldId+" is not empty in "+myIssue.key) log.warn("EC SCRIPT - Custom field values:'"+myIssue.getCustomFieldValue(customField)+"'") def connectFieldValues = [] customFieldValues.each { value -> MutableIssue selectedIssue = issueManager.getIssueObject(value) if(selectedIssue){ connectFieldValues.add((String) selectedIssue.id.toString()) } } if(connectFieldValues){ log.warn("EC SCRIPT - Connect field values:'"+connectFieldValues+"'") def issueToUpdate = issueManager.getIssueObject(myIssue.key) issueToUpdate.setCustomFieldValue(connectField, '{"keys":'+connectFieldValues+'}'); issueManager.updateIssue(user, issueToUpdate, EventDispatchOption.DO_NOT_DISPATCH, false); log.warn("EC SCRIPT - "+connectFieldId+" has been updated in "+myIssue.key) } } else { log.warn("EC SCRIPT - "+customFieldId+" is emtpy in "+myIssue.key) } log.warn('EC SCRIPT ----------------------------------------------------------------') } log.warn('EC SCRIPT - End') Please replace: * A_VALID_JQL_QUERY with a JQL query returning all the issues to be updated * customfield_XXXXX with the Connect field ID * customfield_YYYYY with the Custom Text field ID 2. If the Connect field stores Option IDs: Click to expand... log.warn('EC SCRIPT - Start') import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.bc.issue.search.SearchService import com.atlassian.jira.jql.parser.JqlQueryParser import com.atlassian.jira.web.bean.PagerFilter import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.event.type.EventDispatchOption def pluginAccessor = ComponentAccessor.getPluginAccessor(); def customFieldManager = ComponentAccessor.getCustomFieldManager(); def issueManager = ComponentAccessor.getIssueManager() def optionsManager = ComponentAccessor.getOptionsManager() def jqlQueryParser = ComponentAccessor.getComponent(JqlQueryParser) def searchService = ComponentAccessor.getComponent(SearchService) def user = ComponentAccessor.getJiraAuthenticationContext().getUser() def query = jqlQueryParser.parseQuery("A_VALID_JQL_QUERY") def connectFieldId = "customfield_XXXXX" def customFieldId = "customfield_YYYYY" // the field used to migrate Connect field values def selectListId = "customfield_ZZZZZ" // the field whose Options IDs are stored by the Connect field def connectField = customFieldManager.getCustomFieldObject(connectFieldId); def customField = customFieldManager.getCustomFieldObject(customFieldId); def selectListField = customFieldManager.getCustomFieldObject(selectListId); def results = searchService.search(user, query, PagerFilter.getUnlimitedFilter()) log.warn("EC SCRIPT - Total issues: ${results.total}") log.warn('EC SCRIPT ----------------------------------------------------------------') results.getResults().each { myIssue -> if(myIssue.getCustomFieldValue(customField)){ def customFieldValues = myIssue.getCustomFieldValue(customField).toString().split(',') log.warn("EC SCRIPT - "+customFieldId+" is not empty in "+myIssue.key) log.warn("EC SCRIPT - Custom field values:'"+myIssue.getCustomFieldValue(customField)+"'") def connectFieldValues = [] customFieldValues.each { value -> def fieldConfig = selectListField.getRelevantConfig(myIssue) def optionItem = optionsManager.getOptions(fieldConfig)?.find { it.toString() == value } if(optionItem){ connectFieldValues.add((String) optionItem.optionId.toString()) } } if(connectFieldValues){ log.warn("EC SCRIPT - Connect field values:'"+connectFieldValues+"'") def issueToUpdate = issueManager.getIssueObject(myIssue.key) issueToUpdate.setCustomFieldValue(connectField, '{"keys":'+connectFieldValues+'}'); issueManager.updateIssue(user, issueToUpdate, EventDispatchOption.DO_NOT_DISPATCH, false); log.warn("EC SCRIPT - "+connectFieldId+" has been updated in "+myIssue.key) } } else { log.warn("EC SCRIPT - "+customFieldId+" is empty in "+myIssue.key) } log.warn('EC SCRIPT ----------------------------------------------------------------') } log.warn('EC SCRIPT - End') Please replace: * A_VALID_JQL_QUERY with a JQL query returning all the issues to be updated * customfield_XXXXX with the Connect field ID * customfield_YYYYY with the Custom Text field ID *(the field used to migrate Connect field values)* * customfield_ZZZZZ with the Custom field ID used by the Connect field *(the field whose Options IDs are stored by the Connect field)*. This script may take a long time to run based on the scope of affected issues. We thus recommend you to schedule this maintenance operation during non-business hours in order to avoid performance issues #### B. Delete the custom Text field Once the Connect fields have been updated, delete the corresponding custom Text field. --- language: "en" --- # 3 real-life use cases on how to get external data into Jira Jira is a powerful tool: it is great for planning, tracking, and managing projects. But sometimes it doesn't allow you to do exactly what you or your clients want. Has this ever happened to you? You are at a kick-off meeting with a new client to gather his needs. At some point, he mentions his sales team is using Salesforce CRM to manage all their accounts: "Oh wouldn't it be great if we could get information from Salesforce accounts into Jira? We just paid a lot to get Salesforce, and we really need to capitalize on the investment. If we are paying for lots of services that don't work together, that's no good. We can do it, right?" This is one of the multitude of requests a client can make for retrieving and gathering external data to input into Jira Software or Jira Service Management. Fortunately the answer you can give him is "Yes, of course we can! And I know exactly which tool you need to do that!" [Elements Connect (formerly nFeed)](https://elements-apps.com/products/connect-for-jira/) brings your external data inside [Jira custom fields](https://elements-apps.com/blog/jira-custom-fields/). It works with an extensive range of external data sources. To present the variety of use cases implementable with Elements Connect, we created a [demo portal](http://connect-demos.elements-apps.com/). We have selected for you 3 real-life use cases you may face some day (or have already faced) as a Jira consultant or Jira admin, from suggesting similar issues to retrieving details from a CRM or LDAP. ## Retrieve data about clients from Salesforce CRM **The situation** A company is using side by side Salesforce for managing their customer accounts and a [Jira Service Management](https://www.atlassian.com/software/jira/service-desk) portal for customer support. **The goal** To improve customer support, it is useful to provide agents with additional information about customers raising requests from the Jira Service Management portal. The goal is to provide details about the client directly in Jira Service Management, such as name, job title, phone, his or her Salesforce account and related opportunities, and to make this information only visible by the agents. This way they will have more context and can better answer requests. **How Connect can help** With Elements Connect, you can add different custom fields to your Jira Service Management request form and only display them on the agent side. These fields are connected to Salesforce using the Salesforce connector, and Elements Connect fetches the requested data remotely from Salesforce to populate these fields. You get exactly the data you are looking for depending on the selected client. In this case, the fields are populated with the client details (name, job title, phone and email address), the associated Salesforce account and the related opportunities. ![Integrating Salesforce data in Jira with Elements Connect](https://elements-apps.com/wp-content/uploads/2019/08/Elements-Connect-Jira-Service-Desk-Salesforce_CRM-1.png) ## Get employees details from LDAP into Jira **The situation** A consulting company is gathering all employees details (phone, email, manager name, organization, etc.) within LDAP. For this company, Jira is the main tool for project management. It is used by HR teams for onboarding processes, marketing teams for managing campaigns, and consulting teams for resources allocation \& planning. For these teams, a great benefit would be to access employees information into Jira. **The goal** Get employee information from LDAP and display it in Jira so Jira users have access to relevant employees information in context. **How Connect can help** In this example, Elements Connect can get specific information about the current user (his name, job position, phone number \& email address) by executing LDAP queries on the company's LDAP. All this data is nicely displayed in a user card using some HTML, providing the task's assignee all the information he or she needs about the employee. ![Elements Connect Jira LDAP integration](https://elements-apps.com/wp-content/uploads/2019/08/Elements-Connect-Jira-LDAP-Training-example.png) ## Present similar issues to avoid duplicate issue creation in Jira Service Management **The situation** A software company is using a Jira Service Management for managing issue \& bug requests on their products. Using Jira Service Management for retrieving and managing customers requests is a common thing for customer-focused software companies. However if a bug is detected and reported by a customer, other customers are probably facing the same issue and are likely to raise it too. That leads to duplicated tickets, which are difficult to manage by the agents. **The goal** To avoid the creation of duplicate issues in Jira Service Management, by informing the customer of existing similar issues upon issue creation. **How Connect can help** An additional field "Similar issues" can be added to the Jira Service Management request form with Elements Connect. This read-only field is connected to the local Jira, and lists existing issues with a similar summary. When the customer begins to type his or her request in the Summary field, a dynamic JQL query is executed based on what is typed in the Summary field to display issues that have a similar summary in the Connect "Similar issues" field. This way, the customer is directly informed about the existing similar issues, can take a look at them if needed and watch the one corresponding to his or her problem until resolution. ![https://elements-apps.com/wp-content/uploads/2019/08/Elements-Connect-jira-service-desk-similar-issues.gif](https://elements-apps.com/wp-content/uploads/2019/08/Elements-Connect-jira-service-desk-similar-issues.gif) ## Make Jira work with any external data source It's common for consultants to work with clients who have multiple different tools. The risk with this diversity of solutions is to lose time looking for information in various sources and even data duplication. With Jira and [Elements Connect](https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=datacenter&tab=overview), you can make these tools work together, gather all information into Jira and make your clients' lives easier. Interested in implementing one of these use cases? You can download the configuration of each example from our[Elements Connect demo portal](http://connect-demos.elements-apps.com/) and try them on your own Jira instances. You can also find a lot of other examples with various data sources and learn how to connect to knowledge bases, product catalogs, translation tools, and more. To access to it, you just need to create an account. Have a look and get inspired! [Visit the Elements Connect demo portal](http://connect-demos.elements-apps.com/) And next time you meet a client who wants to connect Jira to Salesforce or any other data source, you'll know what to do! --- language: "en" --- # 6.0.1 Release note We've put UX and ease of configuration the heart of this release. This version comes with a completely redesigned admin interface featuring a field configuration tester, a new snapshot field category, and more. ## Important notice - Breaking changes This version might brings breaking changes, we recommend you to carefully read this release note and **test the upgrade on a staging environment first**. ### v5 and v6 compatibility #### Field values storage format **Change** In this version, we have changed the way Connect stored field values in Jira. For performance and consistency reasons, from XML we have switched the file format to JSON. **Consequence** It means that field values stored with Connect v6 cannot be read by Connect v5. As a consequence, **if Connect is downgraded from v6 to v5 all the fields set or updated while v6 was installed will appear empty with v5**. We highly recommend you to run advanced test on a staging environment before upgrade to v6. [Read more about the field values storage format](https://doc.elements-apps.com/elements-connect/storage-format.md) #### Elements Connect configuration **Change** The storage location and structure of Elements Connect configuration has changed too. Previously stored a single XML file stored in Jira properties the configuration is now stored in multiple AO tables in Jira database. **Consequence** For this reason, if you upgrade to v6, make some changes in Connect configuration and then downgrade to v5, the changes made in v6 won't be visible after the downgrade. This can lead to inconsistency in the data stored in your Connect fields. ### Compatibility with 3rd party apps Other Jira apps are compatible with Elements Connect fields, like Eazy BI, Exporter or Midori's apps. Unfortunately, some of them directly use the value stored in Jira DB. Because of the change brought by this version, the compatibility could be broken. We have already warned the vendors whose apps are compatible with Connect (at least the one we are aware of). On our side we released a new version of our own app - Copy and Sync - compatible with Elements Connect v5 and v6. If you are a developer and if your app is compatible with Elements Connect fields, please have a look at the changes made to the storage format. This warning also applies to Jira admins using Elements Connect field in Script Runner scripts. The recommended way to work with Elements Connect fields is to [use the Java API](https://doc.elements-apps.com/elements-connect/java-api.md). ## New features ### Configuration Tester We've built a brand new field configuration tester which provides insights on your field configuration. It shows query results, a preview of how your data will be displayed in issues and metrics about query execution time. [Read more about the Configuration tester](https://doc.elements-apps.com/elements-connect/configuration-tester.md). ### Snapshot field We've added a new category of custom fields: snapshot fields. Instead of fetching data every time a screen is refreshed, snapshot fields get the record value from the data source only once. [Read more about the Snapshot field](https://doc.elements-apps.com/elements-connect/the-different-field-types.md) ### Field editors #### Autocomplete HTML tags can now be used in the autocomplete editor. You can use them to add some visual impact to the fields options. #### Read only A common way to display results in a read only multi values field is to use a table. Until today, you had to write yourself the HTML code to generate a table. With this new version, you won't have to do it anymore as Elements Connect now offers a predefined "Table" table for those fields. #### Query result picker For clarity, "Query result picker" field has been renamed to "Table" #### New editors: Checklist \& Radio button Compared to drop downs, radio buttons and checkboxes: * have lower cognitive load because they make all options permanently visible so that users can easily compare them * are quicker to edit (1 click to select an option against at least two for drop downs - more if the user has to scroll to view all options) However, drop downs are a better choice if the # of options is \>= 6\~8 For this reason, we have added two fields editors: * Radio button * Checkbox [Read more about the different fields editors](https://doc.elements-apps.com/elements-connect/field-editor-configuration.md). ### Velocity \& query editor The Velocity language is at the heart of Elements Connect. We use it to add dynamism to queries, using conditional instructions (like if / else or for loops) and by including references to other issue fields. When using dependencies, it's not trivial to find the right syntax and custom field ID we'd like to add a dependency to #### Autocomplete and syntax validator That's why we have added an autocomplete function to the query editor. Just type '$' in a query editor, and you'll see the full list of velocity variables and functions available in the current context. And because Velocity sometimes offers a weird syntax, we've added a syntax validator that live checks your query and will warn you if there is an error in your script. #### Better field support When using dependencies to options fields in your queries (fields like nartive checkboxes or select lists), you know directly have access to the option name in addition to the option id. Using the getOptionName() and getOptionsNames(). This will highly simplify the migration of a configuration between Jira instances. We now also support the Sprint field provided by Jira Software [Read more about Velocity](https://doc.elements-apps.com/elements-connect/velocity.md) ### Java API While we try to provide all the required features in Elements Connect, some use cases simply cannot be implemented without scripting. Many users rely on scripting apps, like Scriptrunner, to leverage their usage of Elements Connect. For that matters, we offer a public Java API that can be used in scripts. Now you can trigger the computation of an Elements Connect fields from any script, using the new [computeFieldsValue()](https://elementsapps.github.io/elements-connect-javadoc/0.2.0/com/valiantys/nfeed/api/IFieldValueService.html#computeFieldsValue-java.lang.String-java.util.List-) method. [Read more about the Java API.](https://doc.elements-apps.com/elements-connect/java-api.md) ## Bug fixes We have also fixed numerous bugs: | priority | key | summary | functional components | |----------|-----|---------|-----------------------| | Unable to locate Jira server for this macro. It may be due to Application Link configuration. |||| --- language: "en" --- # 6.0.10 Release note ## Bug fixes If you're upgrading from v5, [read this release note carefully](https://doc.elements-apps.com/display/CO/.6.0.1+Release+note+v6.0)!! * [CO-3549](https://support.elements-apps.com/browse/CO-3549) - Connect field disappears from the basic search options when refreshing the page * [CO-3626](https://support.elements-apps.com/browse/CO-3626) - Description of Elements Connect fields doesn't support HTML and JS * [CO-3630](https://support.elements-apps.com/browse/CO-3630) - Connect fields do not work on JSD if a global default value is set (IE11) * [CO-3631](https://support.elements-apps.com/browse/CO-3631) - User field selected value do not appear in basic search --- language: "en" --- # 6.0.11 Release note ## Jira 8.4 compatibility If you're upgrading from v5, [read this release note carefully](https://doc.elements-apps.com/display/CO/.6.0.1+Release+note+v6.0)!! This version brings the compatibility with Jira 8.4 --- language: "en" --- # 6.0.2 Release note ## Support of gzip encoding and bug fixes **If you upgrade from v5, please** [**read this release note carefully**](https://doc.elements-apps.com/elements-connect/latest/jira-administrators/release-notes/6-0-1-release-note)**!!** This version, brings the support of the gzip encoding for URL datasources. If you're requesting large files with Elements Connect, [you should activate this option](https://doc.elements-apps.com/elements-connect/latest/jira-administrators/improve-performances#id-.Improveperformancesv6.0-EnablegzipcompressionforURLdatasources) in your datasource configuration to speed up your fields. We have also fixed small bugs related to the new 6.0 version: * [CO-3492](https://support.elements-apps.com/browse/CO-3492) - Connect should handle the gzip encoding * [CO-3547](https://support.elements-apps.com/browse/CO-3547) - Order of JSON columns and Read only table template not saved in the correct order * [CO-3563](https://support.elements-apps.com/browse/CO-3563) - "Cannot read property 'maxSuggestions' of undefined" error when editing or testing configuration created from json export * [CO-3564](https://support.elements-apps.com/browse/CO-3564) - NullPointerException when generating configuration backup * [CO-3565](https://support.elements-apps.com/browse/CO-3565) - HTML returned by the data source shall never be evaluated (edit, search \& display views) * [CO-3567](https://support.elements-apps.com/browse/CO-3567) - Connect Legacy Text fields not compatible with Jira Misc Workflow and other apps (com.valiantys.jira.plugins.sql.customfield.DeprecatedFieldSingularObject) * [CO-3569](https://support.elements-apps.com/browse/CO-3569) - It shall be possible to export a field configuration even if the CF is deleted * [CO-3570](https://support.elements-apps.com/browse/CO-3570) - It shall be possible to open and delete a field configuration when field is missing * [CO-3571](https://support.elements-apps.com/browse/CO-3571) - Add debug information in logs when searching on connect fields generates an error --- language: "en" --- # 6.0.3 Release note ## Fix compatibility issues \& other bug fixes **If you upgrade from v5, please**[**read this release note carefully**](https://doc.elements-apps.com/elements-connect/latest/jira-administrators/release-notes/6-0-1-release-note)**!!** In Elements Connect 6.0 we introduced some changes in the fields value storage format which had an impact on the compatibility of Elements Connect with third-party apps. We did our best to make sure Elements Connect remained compatible with the most popular third-party apps, however, we didn't take into account some commonly used apps. In this version, we're fixing some compatibility issues that weren't addressed by the 6.0 version. Rest assured that we know how integration with other apps is important for customers and that fixing compatibility bugs is our #1 priority. Bug fixes: * [CO-3572](https://support.elements-apps.com/browse/CO-3572) - Broken compatibility with JEMH * [CO-3579](https://support.elements-apps.com/browse/CO-3579) - Can't set Connect field values when importing issues from CSV * [CO-3577](https://support.elements-apps.com/browse/CO-3577) - Elements Connect does not display correctly special characters (like Cyrillic alphabet or chars with accents) * [CO-3576](https://support.elements-apps.com/browse/CO-3576) - Dependencies between fields appear broken whilst they should not --- language: "en" --- # 6.0.4 Release note ## Jira Misc Workflow Extensions compatibility **If you upgrade from v5, please**[**read this release note carefully**](https://doc.elements-apps.com/elements-connect/latest/jira-administrators/release-notes/6-0-1-release-note)**!!** This version brings back the compatibility with Jira Misc Workflow Extensions app (JMWE) post functions, see [CO-3583](https://support.elements-apps.com/browse/CO-3583) - Can't copy Elements Connect fields with JMWE. It also fixes some bugs which are listed here : * [CO-3265](https://support.elements-apps.com/browse/CO-3265) - Dependencies are not resolved when bulk-moving issues between projects * [CO-3580](https://support.elements-apps.com/browse/CO-3580) - JSON Path in Columns with velocity or empty lines not evaluated * [CO-3587](https://support.elements-apps.com/browse/CO-3587) - Unknown error when trying to save field configuration when license is not valid --- language: "en" --- # 6.0.5 Release note ## Bug fixes **If you upgrade from v5, please**[**read this release note carefully**](https://doc.elements-apps.com/elements-connect/latest/jira-administrators/release-notes/6-0-1-release-note)**!!** This version fixes some bugs which are listed here : * [CO-3208](https://support.elements-apps.com/browse/CO-3208) - Autocomplete multi value Elements Connect field cannot be used on Safari iOS and Android * [CO-3524](https://support.elements-apps.com/browse/CO-3524) - Problem with ScriptRunner and CPU Usage * [CO-3590](https://support.elements-apps.com/browse/CO-3590) - Parent fields not appearing when (bulk) moving issues between projects * [CO-3595](https://support.elements-apps.com/browse/CO-3595) - Cannot edit Elements Connect fields value after upgrade to 6.0.4 * [CO-3496](https://support.elements-apps.com/browse/CO-3496) - Selection in the first column of a cascading select list deselects option in the second column * [CO-3593](https://support.elements-apps.com/browse/CO-3593) - Impossible to use default value for an Elements Connect field in JSD --- language: "en" --- # 6.0.6 Release note ## Bug fixes Details **If you upgrade from v5, please** [read this release note carefully](https://doc.elements-apps.com/elements-connect/6-0-1-release-note.md)**!!** This version fixes some bugs which are listed here : * [CO-3510](https://support.elements-apps.com/browse/CO-3510)- Can't edit nFeed field contextualized on an issue type from the "Convert subtask to issue" when target task has a different workflow: Forbidden 403 * [CO-3594](https://support.elements-apps.com/browse/CO-3594) - Impossible to use default value for an Elements Connect field with multi selection in JSD * [CO-3596](https://support.elements-apps.com/browse/CO-3596) - Elements Connect fields ignore the "Required" or "Mandatory" option * [CO-3600](https://support.elements-apps.com/browse/CO-3600) - Make it clear that an issue shall be selected in the configuration tester when there is a dependency to $issue --- language: "en" --- # 6.0.7 Release note ## Bug fixes If you upgrade from v5, please [read this release note carefully](https://doc.elements-apps.com/display/CO/.6.0.1+Release+note+v6.0)!! This version fixes this bugs: * [CO-3604](https://support.elements-apps.com/browse/CO-3604) - Legacy fields don't behave like Deprecated fields with schemes * [CO-3584](https://support.elements-apps.com/browse/CO-3584) - Cannot copy Connect Live Text key value into another Live Text Connect field on Post Function --- language: "en" --- # 6.0.8 Release note ## Bug fixes If you upgrade from v5, please [read this release note carefully](https://doc.elements-apps.com/display/CO/.6.0.1+Release+note+v6.0)!! This version fixes bugs: * [CO-3609](https://support.elements-apps.com/browse/CO-3609) - Edit issue: Connect fields depending on user field not refreshed when their parent field is edited * [CO-3612](https://support.elements-apps.com/browse/CO-3612) - Error when editing a field which has a dependency to a "Multi value select" Jira field * [CO-3605](https://support.elements-apps.com/browse/CO-3605) - "Set a field value" post function selects all values available for a single value field instead of the first one * [CO-3606](https://support.elements-apps.com/browse/CO-3606) - Popup doesn't display properly when in-line editing dependent Element Connect fields [Next Page](https://doc.elements-apps.com/llms-full.txt/1)