--- version: "Latest" language: "en" --- # Tooltips ## Tooltips Easily add tooltips over any Confluence content User Guide Download Report an Issue ### Documentation * #### [User Guide](https://atlassianapps.sngular.com/tooltips/Latest/user-guide.md) * #### [Migrating to Data Center](https://atlassianapps.sngular.com/tooltips/Latest/migrating-to-data-center.md) * #### [Tooltip Usage Assessment](https://atlassianapps.sngular.com/tooltips/Latest/tooltip-usage-assessment.md) --- version: "Latest" language: "en" --- # Migrating to Data Center ## Differences Between Server and Data Center Versions Tooltips is a fully compliant Confluence Data Center app. In order to provide ongoing support and annual DC compliance certification, we charge a small fee for the app. Otherwise, functionality is identical to the Server version of the app. ## How to Migrate to Data Center If you have the Server version installed, Confluence's "Manage Apps" screen may incorrectly notify you that there is no DC compatible version of Tooltips. You can switch to the DC version simply by doing the following: 1. Go to the Manage Apps screen 2. Uninstall Tooltips (you will not lose any data) 3. Go to the "Find New Apps" screen and search for "Tooltips" 4. If you are running Confluence Data Center, you will be able to install and license the DC version of the app --- version: "Latest" language: "en" --- # Tooltip Usage Assessment Because tooltips are not stored as macros, it is not possible to track them from the Macro Usage screen or using CQL. The following SQL query should work on any database engine and will return a list of pages likely containing tooltips: SQL select c.contentid, c.contenttype, s.spacename, s.spacekey, c.title from BODYCONTENT bc join content c on bc.contentid = c.contentid join spaces s ON c.spaceid = s.spaceid where body like '%tooltip=%' and c.prevver is null and c.content_status = 'current' order by s.spacekey, c.title; --- version: "Latest" language: "en" --- # User Guide /\*\\*/ What Does This Plugin Do? Adding a Tooltip Creating a Tooltip With a Web Link Tips ## What Does This Plugin Do? The Tooltips plugin allows authors to add content as tooltips within a page that pop up when a user hovers the mouse cursor over the page element containing the tooltips. ![tooltip-example.png](https://atlassianapps.sngular.com/__attachments/a_5e3d1c58bb8d4179d66e2d1e60861f5a655a32a0974dfad9a7290df0111c0c10/tooltip-example.png?cb=f4b6ed414c10577c7880bff5fc33c5ea) This is a great way to enhance your documentation without adding clutter to your pages. This plugin allows this functionality entirely through the link dialog so that no macros are necessary. ## Adding a Tooltip You can add a tooltip over any wiki content that supports links. To add a new tooltip: 1. In the page editor, highlight the desired text, images, or elements 2. Click the ![insert-link.png](https://bitbucket.org/repo/MRkn7A/images/2717310206-insert-link.png) button in the toolbar to open the link editor 3. Select the "Tooltip" tab on the left 4. Enter the text you'd like to appear in the tooltip in the "Tooltip Text" field and click Save ![screenshot2-small.png](https://atlassianapps.sngular.com/__attachments/a_60f4f4942c1a8701a9eb6bde33497575b499da210ba0672e0bdad3bbd8f6e1b5/screenshot2-small.png?cb=c5e0db79a5489d4b8b5fc3923db0e8dc) ## Creating a Tooltip With a Web Link If you'd like to create a tooltip that also links to another URL: 1. In the page editor, highlight the desired text, images, or elements 2. Click the ![insert-link.png](https://bitbucket.org/repo/MRkn7A/images/2717310206-insert-link.png) button in the toolbar to open the link editor 3. Select the "Web link" tab on the left 4. Enter the link address 5. Select the "Tooltip" tab on the left 6. Enter the text you'd like to appear in the tooltip in the "Tooltip Text" field and click Save ## Tips * Use tooltips in table headers to keep tables more compact * Add them to status lozenges to add details * Confluence provides useful emoticons you can use to provide tooltips * Shortcuts for useful emoticons: | Emoticon | Shortcut | |---------------|----------| | (information) | (i) | | (question) | (?) | | (warning) | (!) | --- version: "Latest" variant: "Cloud" language: "en" --- # Shared Estimations for Jira ## Shared Estimations for Jira This app helps teams collaboratively estimate Jira issues in a sync/async manner. This documentation will guide you through Shared Estimations for Jira. Plan, e... ### Pinned articles * #### [๐Ÿ“Understanding Estimation Methods](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/understanding-estimation-methods.md) A Note on Result Anonymity Beyond selecting how your team estimates (the method), there's also a choice in how the results are displayed once voting concludes.... ### Documentation * #### [๐Ÿš€Getting started](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/getting-started.md) #### [โš™๏ธ Using Shared Estimations](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/using-shared-estimations.md) #### [๐Ÿ“Understanding Estimation Methods](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/understanding-estimation-methods.md) * #### [๐Ÿ›  Configuration (for Jira Admins)](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/general-configuration.md) * #### [Migrations (for Jira Admins)](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/migrations-for-jira-admins.md) * #### [๐Ÿ—’ Release Notes](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/release-notes.md) * #### [๐Ÿ’ก Troubleshooting](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/faq.md) * #### [โ˜๏ธ Cloud Migration Guide](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/cloud-migration-guide.md) --- version: "Latest" variant: "Cloud" language: "en" --- # โ˜๏ธ Cloud Migration Guide **Important:** ++To migrate Shared Estimations data with JCMA,++ your Jira Data Center instance must be running Shared Estimations version **4.4.0** or later. Upgrade before starting the migration. This page explains how to migrate the Shared Estimations app from Jira Data Center to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), and what data will be migrated as part of the process. ## Overview Shared Estimations integrates with the Jira Cloud Migration Assistant (JCMA) to provide a guided and reliable migration path from Data Center to Cloud. When you migrate projects with JCMA, the app-related configuration and estimation data associated with those projects can be migrated automatically to your Jira Cloud site. The migration is project-based: when you select projects for migration in JCMA, the Shared Estimations configuration and data that belong to those projects are included in the migration scope, subject to the limitations described in this guide. ## What Is Migrated ### Global Configuration Shared Estimations provides a global configuration that allows Jira administrators to control where the app is available. As part of a JCMA-driven migration, Global Shared Estimations configuration is migrated to the target Jira Cloud site. ### Issues Estimation Data Estimation data managed by Shared Estimations is migrated automatically when the associated project is migrated with JCMA, provided that: * The project is included in a JCMA migration plan. * Shared Estimations is installed and connected in both the Data Center and Cloud environments. For issues that are in scope of the migration and not archived, Shared Estimations estimation data will be migrated and linked to the corresponding issues in Jira Cloud. ## What Is Not Migrated Archived issue data is not migrated. Estimation data stored by Shared Estimations for archived issues in Jira Data Center will not be available in Jira Cloud after migration. This means: * If an issue is archived in Jira Data Center, its associated Shared Estimations data will not be migrated to Cloud. ## Support and Troubleshooting For help planning or validating your migration, contact our support team with details about your current board setup and desired Cloud configuration. [Open a support ticket](https://jirasupport.atlassian.net/servicedesk/customer/portal/1/group/18/create/105). --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ’ก Troubleshooting ## FAQ (Frequently Asked Questions) ### **Q: Why are my estimations not being saved to the Jira "Story Points" field?** A: If the app is not saving estimation values to the Jira "Story Points" field, please confirm the following settings in your Jira instance: * **Exact Field Name:** The Jira instance must have a field named exactly **"Story Points"** or at least have a field configured with that exact name in **United States English**. * **Issue Context:** The "Story Points" field needs to be configured to appear within the context of the Jira issue being viewed. If it is not set to a global context or within a "Project -\> Issue" context, the app will not be able to find and interact with it. * **Numeric Field Type:** The "Story Points" field must be of a **numeric** field type. --- version: "Latest" variant: "Cloud" language: "en" --- # Fibonacci **Estimation Process** * When this method is selected, users will vote using the Fibonacci sequence: **1, 2, 3, 5, 8, 13, 21, 34, 55, 89, โˆž, ?** as options. * During voting, these options will be presented in the voting pad. * The results will show the distribution of votes across these values. **General Purpose** We recognize that estimating complex tasks involves inherent uncertainty, especially as complexity increases. The Fibonacci method leverages our natural ability to compare the relative size of tasks. Its sequence, with increasingly larger gaps between numbers, mirrors the growing uncertainty we face when trying to estimate larger and more intricate items. By using this method, teams can more effectively differentiate between tasks based on their relative effort. This encourages valuable discussions among team members, leading to a shared understanding of the work involved and ultimately contributing to improved planning. **Non-numeric Values** * **โˆž (Infinity):** Represents a task too large to estimate accurately now, likely needing to be broken down. * **? (Question Mark):** Indicates a lack of information or understanding required for estimation. **Correlation with Story Points** * Most Fibonacci values (1, 2, 3, 5, 8, 13, 21, 34, 55, 89) are directly used as story point values. * **? (Question Mark):** This value **does not have a related value** to be automatically set in the Jira "Story Points" field. It usually requires further discussion and potentially re-estimation. * **โˆž (Infinity):** This value corresponds to **999** in the Jira "Story Points" field, indicating a very large or undefined amount of effort. --- version: "Latest" variant: "Cloud" language: "en" --- # Fist to Five **Estimation Process** * When this method is selected, the user initiating the estimation (the owner) will be prompted to enter a **proposed numeric value**(1-99). * This proposed value will be displayed on the voting screen above the voting pad. * Voters will use the "Fist to Five" method to indicate their agreement: **Fist, 1, 2, 3, 4, 5**. * **Fist (or 1):** Represents low confidence, disagreement, or major concerns. * **5 Fingers:** Represents high confidence, full agreement, or readiness to proceed. * The results will show the distribution of agreement levels. **General Purpose** This method is used to quickly gauge the team's consensus or level of agreement with a proposed estimate. It's not directly estimating size but rather the confidence in a pre-defined value. **Fist to Five** is often used as a quick method to gauge team consensus or confidence regarding a plan, decision, or a proposed estimate. It helps quickly surface alignment or identify points of disagreement that need further discussion. **Correlation with Story Points** When using the **Fist to Five** method, the proposed value entered by the estimation owner will be stored directly in the Jira "Story Points" field after the estimation process is submitted. The team's votes reflect their level of agreement with this proposed value. --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ›  Configuration (for Jira Admins) **Accessing Project Configuration** Jira administrators can configure *Shared Estimations* for their Jira instance by following these steps: 1. Click the **cogwheel icon โš™๏ธ** (Settings) located at the top right corner of your Jira instance. 2. Select **Manage apps**. 3. In the left sidebar menu, identify and click on the *Shared Estimations* section. **Selecting Jira Projects for Shared Estimations** ![Shared Estimations - Available for all projects by default](https://atlassianapps.sngular.com/__attachments/a_266c25d8b9c453d61f7847f19c5e32d51b69d5fc9d2cfa75ae1bf302150ce142/Screenshot%202025-09-02%20at%2011.08.42.png?cb=b4a820f16620591d6b97a5b486a55b41) Available for all projects by default ![Screenshot 2025-09-02 at 11.07.30.png](https://atlassianapps.sngular.com/__attachments/a_92f3e9154430506e58e45eaf83d70e17bfea239dc612cae5fbea3c08ea47908b/Screenshot%202025-09-02%20at%2011.07.30.png?cb=ef774f6fbea7e4fcc26f1eb66458de45) Enable the Shared Estimation for specific projects The configuration screen features a multi-select dropdown that allows you to choose the specific Jira projects where you want *Shared Estimations* to be active. * **Selecting Projects:** Click on the dropdown to see a list of your Jira projects. Select the projects where you want to enable Shared Estimations. * **Applying to All Projects:** If the multi-select dropdown is left empty, *Shared Estimations* will be available and will run on all Jira projects within your Jira instance. --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿš€Getting started **Accessing Shared Estimations** You can access and use *Shared Estimations* directly within the Jira issue search, a Jira issue view, or from the Jira board sidebar, providing flexibility based on your workflow. ![Shared Estimations - Look for the dedicated Shared Estimations section on the Jira issue right panel.](https://atlassianapps.sngular.com/__attachments/a_8dd551dc9c346ce59630ec5e7f3b74783b54aefb03dc76a729875da244df4039/Screenshot%202025-09-02%20at%2011.01.46.png?cb=8505f723dcbf162a202f588c6171be50) Look for the dedicated *Shared Estimations*section on the Jira issue right panel. **Basic Estimation Workflow** 1. Navigate to the Jira issue you want to estimate. 2. Locate the *Shared Estimations* section within the Jira issue view (or access it from the board sidebar). 3. Follow the on-screen prompts to start or join an estimation session. 4. Participate in the voting process. 5. View the results and the finalized estimation. --- version: "Latest" variant: "Cloud" language: "en" --- # Linear **Estimation Process** * When this method is selected, users will vote using the numbers from **1 to 10** as options. * During voting, these numbers will be presented in the voting pad. * The results will show the distribution of votes across these values. **General Purpose** The linear method provides a simple and straightforward way to estimate effort or complexity on a consistent, numerical method. It's often used when tasks are relatively well-understood and the differences in size are perceived as evenly distributed. **Correlation with Story Points** Linear method directly correlates the voted value with story points (e.g., a vote of 5 equals 5 story points). --- version: "Latest" variant: "Cloud" language: "en" --- # Migrations (for Jira Admins) The **Migrations** dashboard allows Jira administrators to track and monitor data migrations from your previous Jira instance (Jira Data Center) to your current Jira Cloud environment. This page provides visibility into all migration activities, their current status, and any issues that may have occurred during the migration process. ## ๐Ÿš€ Accessing the Migrations Page Jira administrators can access the tracking history by following these steps: 1. Click the cogwheel icon โš™๏ธ (**Settings**) located at the top right corner of your Jira instance. 2. Select **Marketplace apps**. 3. In the left sidebar menu, look for the **Shared Estimations** section and click on **Migrations**. ## **๐Ÿ“Š Understanding the Migrations Table** ![Captura de ecraฬƒ 2026-05-29, aฬ€s 18.35.58.png](https://atlassianapps.sngular.com/__attachments/a_96dd6abb20f5ddab71059f5988f398cb84193d47f2273f1c33636c95f7808b07/Captura%20de%20ecra%CC%83%202026-05-29,%20a%CC%80s%2018.35.58.png?cb=0b6347565ee90acc431788acd445d7d8) * **Name:** The name of the originating instance or server where the data is coming from (e.g., *Legacy Jira Server - Production*). * **Projects:** A list of the specific Jira projects whose estimation data was included in this transfer. * **Created At:** The exact date and timestamp showing when the migration process was initiated. * **Status:** Reflects the current state of the migration. It will display one of the following badges: * ๐Ÿ†• **Started:** The migration request has been received and initialized. * ๐Ÿ”„ **In Progress:** Data is actively being transferred and processed. * โœ… **Completed:** The data has been successfully imported into Shared Estimations. * โŒ **Configuration failed / Estimation failed / Failed:** An error occurred, and the migration was aborted. The badge text automatically updates to show which part of the process caused the failure. Hovering over any of these failed badges reveals a tooltip with the detailed error message. To help you easily search and analyze your migration history, **the table fully supports data sorting** . You can click on the column header to toggle the sorting order of the displayed records. For example, clicking on the **Created At** column header allows you to switch the view to display the most recent migrations first. Clicking it again will reverse the order to show the oldest migrations at the top of the table. ### ๐Ÿ”ง How the Detailed Error Message Works ![Captura de ecraฬƒ 2026-05-29, aฬ€s 18.26.57.png](https://atlassianapps.sngular.com/__attachments/a_28c09c09c129d1fc2d7c1636a8f04d698bc7b3b9ee3e51714d8a16b5b21e0a3d/Captura%20de%20ecra%CC%83%202026-05-29,%20a%CC%80s%2018.26.57.png?cb=12cb3ae2a4d410e7d681635f01ac4797) To keep the dashboard clean, detailed technical logs are kept hidden until needed. If a migration stops and displays a failure badge, simply **hover your cursor over the badge** to read the diagnostic tooltip. The tooltip displays the exact context of the failure based on its category: 1. **Configuration failed:** Displays details about missing, empty, or incompatible configuration files from the source instance. (e.g., *"An error occurred while migrating the configuration..."*). 2. **Estimation failed:** Displays details regarding corrupted or unsupported vote history, story points, or estimation scales. (e.g., *"An error occurred while migrating the estimations..."*). 3. **Generic failed:** Indicates unexpected system errors, file processing issues, or timeouts during the transfer. *๐Ÿ’ก* ***Tip:*** *Every failure tooltip includes a unique* ***Reference ID*** *(e.g.,* `real-migration-1234`*). If you need to open a support ticket, please include this Reference ID so our team can immediately locate the exact technical details in the system logs.* --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ—ณ๏ธ Participating in Estimation Sessions Once an estimation session is started, the user who initiated it becomes the **estimation owner** , and all other participants are **voters.** The **estimation owner** has additional controls to manage the process. **The Voting Screen** ![Shared Estimations - User voting screen](https://atlassianapps.sngular.com/__attachments/a_21a4b6d9d4c4782ee8bd5cdab5498a3b25e953c377365642a8701cda43cfe787/Screenshot%202025-09-02%20at%2010.39.15.png?cb=31b96b62ea485cf330ea73436ddce815) User voting screen ![Shared Estimations - Estimation owner voting screen](https://atlassianapps.sngular.com/__attachments/a_d8d58d23dc929fd02eb6fe33556cf0af2d7e74ac30440a568ee7d13aaab23e7a/Screenshot%202025-09-02%20at%2010.36.49.png?cb=0c0511b60098f0f59cf9b0ccb0f8e426) Estimation owner voting screen * **Estimation** **Owner Identification** The top of the screen displays a bar identifying the user who started the estimation as the **estimation owner**and the estimation status (on the info icon tooltip). * **Voters List** Below the estimation owner identification, avatars of the voters who have voted during the session are shown. Hovering over an avatar displays the voter's name in a tooltip. If no one has voted yet, the message **"No one estimated yet"** is displayed. ![Shared Estimations - Voters list](https://atlassianapps.sngular.com/__attachments/a_a4c2100f554ed348fbfb8827412863f7d4be3a7255fc1baacd09be367dac0957/Screenshot%202025-09-02%20at%2010.05.25.png?cb=2de26bd59605c780424502d6be4cde5a) Voters list * **Selected Method Identification** The selected estimation method is displayed on the screen. * **Additional Information for Dynamic Methods** * **Fist to Five:** Located above the voting pad on the right, you'll see the **proposed value** entered by the owner. * **Wisdom of the Crowd:** The four **numeric values** entered by the estimation owner are presented as the voting options in the voting pad. * **Voting Pad** Below the method information, a voting pad with all the options from the selected method is presented. * **Estimation Owner Controls** As the estimation owner, you will see two additional buttons below the voting pad: * **Stop:** Click this button to terminate the voting and move on to the results screen. * **Delete:** Click this button to discard the current estimation session and return to the previous step (method selection). **Voter Interaction** As a voter, click on an option in the voting pad to submit your estimate. Your selected option will be highlighted. You can change your vote at any time by clicking on a different option. **Key Aspects** * **Bias-Free Estimations** Your individual estimates remain private and are not visible to other participants until the owner stops the voting. This helps to minimize bias in the estimation process. * **Live Interaction** During a synchronous estimation session, votes and actions are updated instantly for all participants, ensuring a real-time collaborative experience. --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ”„ Re-estimating an Issue Clicking the **Re-estimate** button will take you to the scale selection screen (as described in [Scenario 1: No Existing Estimation - Selecting a Method](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/starting-the-estimation-process.md#Scenario-1:-No-Existing-Estimation---Selecting-a-Scale)), where you can choose the estimation method and set the estimation's anonymity level before starting the new session. You will also see an additional **Cancel** button: ![Shared Estimations - Re-estimate screen](https://atlassianapps.sngular.com/__attachments/a_6cb7d05eda923b34a18478f3df4caa54cc524f85255c091bc0b49fff6da7ea55/Screenshot%202025-09-02%20at%2007.01.22.png?cb=670c410c2555a42836494839062d993c) Re-estimate screen Clicking **Cancel** will take you back to the screen showing the current estimation without starting a new session. --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ—’ Release Notes This page provides a comprehensive overview of the release history for Shared Estimations for Jira. Browse the entries below to learn about new features, bug fixes, and important announcements. --- version: "Latest" variant: "Cloud" language: "en" --- # โ–ถ๏ธ Starting the Estimation Process The initial screen you see when accessing*Shared Estimations* for a Jira issue depends on whether the designated Jira "Story Points" field already contains a value. ## **Scenario 1: No Existing Estimation - Selecting a Method** If the Jira "Story Points" field is empty and this is the first time you are estimating this issue, you'll see this screen. ![Shared Estimations - Selecting the estimation method](https://atlassianapps.sngular.com/__attachments/a_982efdd4e4bd6bffa5fc076c09d6ef298fc6ab207ae1ae68d19f3b937524320d/Screenshot%202025-09-02%20at%2006.48.07.png?cb=da6c84a18143be4c7ddcb9aa6b810a22) Selecting the estimation method This screen presents several options to configure before starting the estimation: ### **Estimation Method** Choose an estimation method from the dropdown menu. 1. Some options are **Dynamic Methods**, where participants propose their own numerical value instead of selecting from a predefined list. These require additional input when starting the estimation: * **Fist to Five:** If selected, the estimation owner will be prompted to enter a proposed value (1-99) to initiate the discussion. * ![Shared Estimations - Fist to five method](https://atlassianapps.sngular.com/__attachments/a_7b992ea665c7bd7010ed14818b624a9053bb3882d6b9fadd1cd20992b98d2dfd/Screenshot%202025-09-02%20at%2006.53.05.png?cb=f625d15317907a07f0c1bfe0a7967690) Fist to five method * **Wisdom of the Crowd:** If selected, the estimation owner will be prompted to enter four unique numeric values (1-99) as initial proposals. ![Screenshot 2025-09-02 at 06.55.18.png](/__attachments/a_a647f99623e6892773878d68ba504fc576e27e26889a4b4f8e3a6c8e72b71a94/Screenshot%202025-09-02%20at%2006.55.18.png?cb=a831b693a8de392cbf8fa1bf21a89095) Wisdom of the crowd method **Estimation Anonymity Toggle** * A toggle allows the estimation owner to choose whether the *results* of the estimation will be anonymous or non-anonymous. * **Default:** Estimations are **anonymous** by default. * **Anonymous Mode:** * Participants' votes are *always* hidden during the voting phase to prevent bias. * When the estimation concludes and results are displayed, you will see the distribution of votes and the list of participants, but individual votes *will not* be linked to specific participants. * **Non-Anonymous Mode:** * During the voting phase, participants' votes are *always* hidden to prevent bias (the same as in the anonymous mode). * When the estimation concludes and results are displayed, the specific vote cast by each participant *will be shown* next to their name. 2. **Start Estimation** Once you have selected a method, provided any required input (for Dynamic Methods), **and set the desired anonymity level** , click the **Start** button to begin the estimation session. ### **Scenario 2: Existing Estimation Found** If the Jira "Story Points" field already contains an estimation value, you will see a screen like this: ![Shared Estimations - Existing estimation screen](https://atlassianapps.sngular.com/__attachments/a_44d29b630cbe0e60ac5280d1a33e77602984b4c5c875486de952e92f1e57beed/Screenshot%202025-09-02%20at%2006.59.20.png?cb=703705665fc7fca08e51a21c537ee677) Existing estimation screen This screen displays the current estimation. To start a new estimation session, click the **Re-estimate** button. Clicking **Re-estimate** will take you to the setup screen (described in Scenario 1) where you can select the method and anonymity setting for the new estimation round. --- version: "Latest" variant: "Cloud" language: "en" --- # T-Shirt Size **Estimation Process** * When this method is selected, users will vote using the sizes **XS, S, M, L, XL, XXL,** and**XXXL** as options. * During voting, these sizes will be presented in the voting pad * The results will show the distribution of votes across these sizes. **General Purpose** The **T-Shirt Size** method is used for a high-level, less precise estimation, focusing on the relative size or effort required for a task. It's useful for initial planning or when detailed estimation is not yet feasible. **Correlation with Story Points** The **T-Shirt size** values in *Shared Estimations* are directly correlated with the following story point values: | **T-Shirt Size** | **Story Points** | |------------------|------------------| | **XS** | 1 | | **S** | 4 | | **M** | 7 | | **L** | 13 | | **XL** | 20 | | **XXL** | 40 | | **XXXL** | 80 | When a T-Shirt size is selected as the final estimation, the corresponding story point value will be set in the Jira "Story Points" field. --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ“Understanding Estimation Methods ## **A Note on Result Anonymity** Beyond selecting *how* your team estimates (the method), there's also a choice in *how the results are displayed* once voting concludes. Before starting an estimation session, the owner can set the results mode (detailed [**here**](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/starting-the-estimation-process.md#Estimation-Anonymity-Toggle)): * **Anonymous Results (Default):** When results are shown, you'll see the overall vote distribution (e.g., how many people voted '5', how many voted '8') and who participated, but individual votes are *not* linked back to specific participants. * **Non-Anonymous Results:** When results are shown, you'll see the overall distribution *and* the specific vote cast by each participant linked to their name/avatar. **Important:** Regardless of this setting, the *voting process itself* always remains anonymous while it's happening to ensure unbiased input from all participants. This setting only affects the final results display. Click on the links below to learn more about each estimation method available in *Shared Estimations*: * [Fibonacci](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/fibonacci.md) * [Linear](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/linear.md) * [T-Shirt Size](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/t-shirt-size.md) * [Fist to Five](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/fist-to-five.md) * [Wisdom of the Crowd](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/wisdom-of-the-crowd.md) --- version: "Latest" variant: "Cloud" language: "en" --- # โš™๏ธ Using Shared Estimations This section guides you through the core functionalities of *Shared Estimations*. Learn how to initiate estimation sessions, participate in the voting process, understand the different stages of estimation, and view the final results. * [โ–ถ๏ธ Starting the Estimation Process](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/starting-the-estimation-process.md) * [๐Ÿ”„ Re-estimating an Issue](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/re-estimating-an-issue.md) * [๐Ÿ—ณ๏ธ Participating in Estimation Sessions](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/participating-in-estimation-sessions.md) * [๐Ÿ“ˆ Viewing Estimation Results](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/viewing-estimation-results.md) --- version: "Latest" variant: "Cloud" language: "en" --- # ๐Ÿ“ˆ Viewing Estimation Results Once the estimation owner clicks the **Stop** button in the previous step, the results of the voting are displayed. The way results are displayed, specifically whether individual votes are linked to participants, depends on whether the estimation was set to **anonymous** or **non-anonymous** before starting. **Anonymous Views** ![Shared Estimations - Anonymous estimation owner results screen - Bar Chart](https://atlassianapps.sngular.com/__attachments/a_c4a3883c58d5caa6095ef5da1ac8cd349d6fe304d78b20cc9020dd2274241a5d/Screenshot%202025-09-02%20at%2010.42.01.png?cb=b857f09ecf0adfb27f9204a898be39b4) Anonymous estimation owner results screen - Bar Chart ![Shared Estimations - Anonymous estimation owner results screen - Pie Chart](https://atlassianapps.sngular.com/__attachments/a_e7bd41151060571ecb0d85611e36856f36aac4fc01410b0e4f571589c314cd9e/Screenshot%202025-09-02%20at%2010.46.07.png?cb=99cc4e91ab9d0060426b770c4fec0333) Anonymous estimation owner results screen - Pie Chart **Non-Anonymous Views** ![Shared Estimations - Non-anonymous estimation user results screen - Bar Chart](https://atlassianapps.sngular.com/__attachments/a_667d2d955065032d4dfee4fb6c4ab646b1d8088cf3913472a9f70eab27c9334c/image-20250902-095007.png?cb=5ffb7d7bd1cec04834d78eb23f86f57f) Non-anonymous estimation user results screen - Bar Chart ![Shared Estimations - Anonymous estimation user results screen - Pie Chart](https://atlassianapps.sngular.com/__attachments/a_5cd5a515c1fede36dc6c2fbeff80598365588703f3aa08a8e82b522294309688/Screenshot%202025-09-02%20at%2010.52.47.png?cb=6748009206592d2571f2df956bd22042) Anonymous estimation user results screen - Pie Chart * **Estimation Owner Identification** The owner identification bar remains at the top. * **Dashboard** * **For Wisdom of the Crowd:** A **bar** chart displays the frequency of each voted value. * **For the remaining methods:** The distribution of votes is represented using a **pie** chart. * Below the chart, a voting details section can be expanded. * **In Anonymous Mode:** This section shows the avatars of all participants but *not* their individual votes. * **In Non-Anonymous Mode:** This section shows the avatars of all participants *and* the specific value each participant voted for. * **Estimation Owner Controls** The estimation owner's controls are displayed below the dashboard: * **Suggested Estimation:** The most commonly voted value is suggested. For the **Fist to Five** method, the suggested estimation field is disabled, showing the proposed value. * **Action Buttons:** * **Submit:** Click this to finalize the estimation and update the Jira "Story Points" field. * **Restart Voting:** Click this to discard the current results and start another round of voting. **After Submitting the Estimation** When the owner clicks **Submit** , the submitted estimation will be recorded on the Jira "Story Points" field, and the app will reflect the [Existing Estimation Found](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Cloud/starting-the-estimation-process.md#Scenario-2:-Existing-Estimation-Found) state. This means the submitted estimation will be displayed in the *Shared Estimations*section of the Jira issue, and the option to initiate a re-estimation will be available to anyone who accesses it. --- version: "Latest" variant: "Cloud" language: "en" --- # Wisdom of the Crowd **Estimation Process** * When this method is selected, the user initiating the estimation (the owner) will be prompted to enter **four unique numeric values** (1-99). * These four values will be presented as the voting options in the voting pad. * The results will show the distribution of votes across the four options and the list of participants. **General Purpose** This method leverages the collective wisdom of the team by providing a limited set of options chosen by the estimation owner. It's useful when trying to converge on an estimate from a range of possibilities or when seeking diverse perspectives. **Correlation with Story Points** The estimation value the owner submits is stored in the Jira "Story Point" field for the task. --- version: "Latest" variant: "Data Center" language: "en" --- # Shared Estimations for Jira ## Shared Estimations for Jira This app helps teams collaboratively estimate Jira issues in a sync/async manner. This documentation will guide you through Shared Estimations for Jira. Plan, e... ### News * #### [09-05-2025: Estimation Result Anonymity Control](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/09-05-2025-estimation-result-anonymity-control.md) May 09, 2025 * #### [03-04-2025: Version 4 - Update: New UI, Features, and Refactoring](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/03-04-2025-version-4-update-new-ui-features-and-re.md) April 01, 2025 * #### [06-03-2024: Shared Estimations for Jira Data Center Official Launch](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/06-03-2024-shared-estimations-for-jira-data-center.md) March 27, 2025 ### Pinned articles * #### [๐Ÿ“Understanding Estimation Methods](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/understanding-estimation-methods.md) A Note on Result Anonymity Beyond selecting how your team estimates (the method), there's also a choice in how the results are displayed once voting concludes.... ### Documentation * #### [๐Ÿš€Getting started](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/getting-started.md) #### [โš™๏ธ Using Shared Estimations](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/using-shared-estimations.md) #### [๐Ÿ“Understanding Estimation Methods](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/understanding-estimation-methods.md) * #### [๐Ÿ›  Configuration (for Jira Admins)](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/general-configuration.md) * #### [๐Ÿ”„ What's Changed for Existing Users](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/what-s-changed-for-existing-users.md) #### [๐Ÿ—’ Release Notes](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/release-notes.md) * #### [๐Ÿ’ก Troubleshooting](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/faq.md) * #### [โ˜๏ธ Cloud Migration Guide](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/cloud-migration-guide.md) --- version: "Latest" variant: "Data Center" language: "en" --- # 03-04-2025: Version 4 - Update: New UI, Features, and Refactoring **Major Refactoring and Feature Release** This release introduces a significant overhaul of *Shared Estimations*, bringing numerous improvements and new functionalities: * **Completely Redesigned User Interface** A modern and intuitive UI. * **Performance Enhancements** Improved speed and responsiveness throughout the app. * **New Estimation Methods** Introduction of dynamic methods including **Fist to Five** (with owner-proposed value) and **Wisdom of the Crowd** (with owner-defined options and anonymous voting). * **Enhanced Visualization** New chart types for displaying estimation results. * **Streamlined Workflow** Improved and more intuitive estimation process. * **Changes to Existing Methods** * Updated the**Fist to Five** method. * Removal of the **Planning Cards** method. * Trimmed **Linear** method (options 11 and 12 removed, existing votes migrated to 10). * "Coffee" option removed from **Fibonacci** method (existing votes migrated to 1). * **Improved Jira Integration** Seamless integration with Jira's "Story Points" field, with specific mappings for all methods. * **Context Flexibility** Ability to use *Shared Estimations* within Jira issues and on boards (issue sidebar). * **Themed Experience** Full integration with Jira themes for a consistent look and feel. * **Bias Reduction** Estimates remain private until revealed by the owner. * **Improved Real-time Collaboration** Live updates during estimation sessions. * **Dark mode** Full compatibility with Jira's dark mode has been implemented for Jira 10 instances. --- version: "Latest" variant: "Data Center" language: "en" --- # 06-03-2024: Shared Estimations for Jira Data Center Official Launch Shared Estimations for Jira Data Center is officially launched as a paid app with Atlassian approval and full support. This is the first release for the Data Center platform. --- version: "Latest" variant: "Data Center" language: "en" --- # 09-05-2025: Estimation Result Anonymity Control **Version:** 4.1.0 **Estimation Result Anonymity Control** Estimation owners can now configure how results are displayed after voting concludes using a new toggle on the estimation setup screen (when starting or re-estimating). **Two Modes Available:** * **Anonymous Results (Default):** Displays vote distribution and participant list, but does *not* link specific votes to individual users. This is the new default setting. * **Non-Anonymous Results:** Displays vote distribution, participant list, *and* clearly links each specific vote to the participant who cast it. This provides teams with greater flexibility to choose the result display method that best suits their workflow and fosters psychological safety. The voting process itself remains anonymous during the session in both modes to prevent bias. --- version: "Latest" variant: "Data Center" language: "en" --- # 11-01-2024: Shared Estimations Joins TecnoFor Apps Shared Estimations (formerly Open Poker) is now part of TecnoFor Apps --- version: "Latest" variant: "Data Center" language: "en" --- # โ˜๏ธ Cloud Migration Guide **Important:** ++To migrate Shared Estimations data with JCMA,++ your Jira Data Center instance must be running Shared Estimations version **4.4.0** or later. Upgrade before starting the migration. This page explains how to migrate the Shared Estimations app from Jira Data Center to Jira Cloud using the Jira Cloud Migration Assistant (JCMA), and what data will be migrated as part of the process. ## Overview Shared Estimations integrates with the Jira Cloud Migration Assistant (JCMA) to provide a guided and reliable migration path from Data Center to Cloud. When you migrate projects with JCMA, the app-related configuration and estimation data associated with those projects can be migrated automatically to your Jira Cloud site. The migration is project-based: when you select projects for migration in JCMA, the Shared Estimations configuration and data that belong to those projects are included in the migration scope, subject to the limitations described in this guide. ## What Is Migrated ### Global Configuration Shared Estimations provides a global configuration that allows Jira administrators to control where the app is available. As part of a JCMA-driven migration, Global Shared Estimations configuration is migrated to the target Jira Cloud site. ### Issues Estimation Data Estimation data managed by Shared Estimations is migrated automatically when the associated project is migrated with JCMA, provided that: * The project is included in a JCMA migration plan. * Shared Estimations is installed and connected in both the Data Center and Cloud environments. For issues that are in scope of the migration and not archived, Shared Estimations estimation data will be migrated and linked to the corresponding issues in Jira Cloud. ## What Is Not Migrated Archived issue data is not migrated. Estimation data stored by Shared Estimations for archived issues in Jira Data Center will not be available in Jira Cloud after migration. This means: * If an issue is archived in Jira Data Center, its associated Shared Estimations data will not be migrated to Cloud. ## Support and Troubleshooting For help planning or validating your migration, contact our support team with details about your current board setup and desired Cloud configuration. [Open a support ticket](https://jirasupport.atlassian.net/servicedesk/customer/portal/1/group/18/create/105). --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ’ก Troubleshooting ## Migration ### Upgrading from v3 This section details how existing estimations and active sessions from previous versions are handled in this refactored version. * **Fist to Five:** Any active estimation sessions that were in progress using the old **Fist to Five** method will be discarded during the upgrade due to incompatibility. * **Planning Cards:** Existing estimations made with the **Planning Cards** method will be kept. However, this method is no longer available in the refactored version, and any active estimation sessions using this method will also be discarded. * **Linear:** The **Linear** method has been trimmed. Options "11" and "12" have been removed. Any active estimation sessions with votes on options "11" or "12" will have their votes automatically transformed to "10". * **Fibonacci:** The "Coffee" option has been removed from the Fibonacci method. Any active estimation sessions with votes for the "Coffee" option will have their votes automatically reverted to "1". ## FAQ (Frequently Asked Questions) ### **Q: Why are my estimations not being saved to the Jira "Story Points" field?** A: If the app is not saving estimation values to the Jira "Story Points" field, please confirm the following settings in your Jira instance: * **Exact Field Name:** The Jira instance must have a field named exactly **"Story Points"** or at least have a field configured with that exact name in **United States English**. * **Issue Context:** The "Story Points" field needs to be configured to appear within the context of the Jira issue being viewed. If it is not set to a global context or within a "Project -\> Issue" context, the app will not be able to find and interact with it. * **Numeric Field Type:** The "Story Points" field must be of a **numeric** field type. --- version: "Latest" variant: "Data Center" language: "en" --- # Fibonacci **Estimation Process** * When this method is selected, users will vote using the Fibonacci sequence: **1, 2, 3, 5, 8, 13, 21, 34, 55, 89, โˆž, ?** as options. * During voting, these options will be presented in the voting pad. * The results will show the distribution of votes across these values. **General Purpose** We recognize that estimating complex tasks involves inherent uncertainty, especially as complexity increases. The Fibonacci method leverages our natural ability to compare the relative size of tasks. Its sequence, with increasingly larger gaps between numbers, mirrors the growing uncertainty we face when trying to estimate larger and more intricate items. By using this method, teams can more effectively differentiate between tasks based on their relative effort. This encourages valuable discussions among team members, leading to a shared understanding of the work involved and ultimately contributing to improved planning. **Non-numeric Values** * **โˆž (Infinity):** Represents a task too large to estimate accurately now, likely needing to be broken down. * **? (Question Mark):** Indicates a lack of information or understanding required for estimation. **Correlation with Story Points** * Most Fibonacci values (1, 2, 3, 5, 8, 13, 21, 34, 55, 89) are directly used as story point values. * **? (Question Mark):** This value **does not have a related value** to be automatically set in the Jira "Story Points" field. It usually requires further discussion and potentially re-estimation. * **โˆž (Infinity):** This value corresponds to **999** in the Jira "Story Points" field, indicating a very large or undefined amount of effort. --- version: "Latest" variant: "Data Center" language: "en" --- # Fist to Five **Estimation Process** * When this method is selected, the user initiating the estimation (the owner) will be prompted to enter a **proposed numeric value**(1-99). * This proposed value will be displayed on the voting screen above the voting pad. * Voters will use the "Fist to Five" method to indicate their agreement: **Fist, 1, 2, 3, 4, 5**. * **Fist (or 1):** Represents low confidence, disagreement, or major concerns. * **5 Fingers:** Represents high confidence, full agreement, or readiness to proceed. * The results will show the distribution of agreement levels. **General Purpose** This method is used to quickly gauge the team's consensus or level of agreement with a proposed estimate. It's not directly estimating size but rather the confidence in a pre-defined value. **Fist to Five** is often used as a quick method to gauge team consensus or confidence regarding a plan, decision, or a proposed estimate. It helps quickly surface alignment or identify points of disagreement that need further discussion. **Correlation with Story Points** When using the **Fist to Five** method, the proposed value entered by the estimation owner will be stored directly in the Jira "Story Points" field after the estimation process is submitted. The team's votes reflect their level of agreement with this proposed value. --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ›  Configuration (for Jira Admins) **Accessing Project Configuration** Jira administrators can configure *Shared Estimations* for their Jira instance by following these steps: 1. Click the **cogwheel icon โš™๏ธ** (Settings) located at the top right corner of your Jira instance. 2. Select **Manage apps**. 3. In the left sidebar menu, identify and click on the *Shared Estimations* section. **Selecting Jira Projects for Shared Estimations** ![Default configuration](https://atlassianapps.sngular.com/__attachments/a_5c0e08233046a54aa08ad3047230793737dda407bc0c19aad74c118f410f77e7/image-20250327-144129.png?cb=b5639f7940907bf2f7249840481e13ee) Available for all projects by default ![Custom configuration](https://atlassianapps.sngular.com/__attachments/a_4d24769684408121ef272cc3d5ce82e498175d79fd1346f865f2205c9822784e/image-20250327-144304.png?cb=79920fac2a7ea34737ab852b84c2ee4a) Available for selected projects The configuration screen features a multi-select dropdown that allows you to choose the specific Jira projects where you want *Shared Estimations* to be active. * **Selecting Projects:** Click on the dropdown to see a list of your Jira projects. Select the projects where you want to enable Shared Estimations. * **Applying to All Projects:** If the multi-select dropdown is left empty, *Shared Estimations* will be available and will run on all Jira projects within your Jira instance. --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿš€Getting started **Accessing Shared Estimations** You can access and use *Shared Estimations* directly within the Jira issue search, a Jira issue view, or from the Jira board sidebar, providing flexibility based on your workflow. ![Shared Estimations app location](https://atlassianapps.sngular.com/__attachments/a_f2cb5e16e6ed6b9bef49839001fcac4966d5534e36a72c116fdf1bea1311087b/image-20250404-092441.png?cb=999616215e2f10b9e0b2c4e53528c266) Look for the dedicated *Shared Estimations*section on the Jira issue right panel. **Basic Estimation Workflow** 1. Navigate to the Jira issue you want to estimate. 2. Locate the *Shared Estimations* section within the Jira issue view (or access it from the board sidebar). 3. Follow the on-screen prompts to start or join an estimation session. 4. Participate in the voting process. 5. View the results and the finalized estimation. --- version: "Latest" variant: "Data Center" language: "en" --- # Linear **Estimation Process** * When this method is selected, users will vote using the numbers from **1 to 10** as options. * During voting, these numbers will be presented in the voting pad. * The results will show the distribution of votes across these values. **General Purpose** The linear method provides a simple and straightforward way to estimate effort or complexity on a consistent, numerical method. It's often used when tasks are relatively well-understood and the differences in size are perceived as evenly distributed. **Correlation with Story Points** Linear method directly correlates the voted value with story points (e.g., a vote of 5 equals 5 story points). --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ—ณ๏ธ Participating in Estimation Sessions Once an estimation session is started, the user who initiated it becomes the **estimation owner** , and all other participants are **voters.** The **estimation owner** has additional controls to manage the process. **The Voting Screen** ![User voting screen](https://atlassianapps.sngular.com/__attachments/a_ca8d7210972ae5a02eba96ccb584e5b1383e2ff1b8e163cbe71d9229e62f9906/image-20250327-141740.png?cb=da940ff461fa9969216765bf54eca424) User voting screen ![Estimation owner voting screen](https://atlassianapps.sngular.com/__attachments/a_8ad8646bd1ecbeb445c9e6ad6382d36cb6c9ab268d38c44f20417f0ea783fb1c/image-20250327-141632.png?cb=9a08d65b0d740c2ae159c6b3cafc2c9f) Estimation owner voting screen * **Estimation** **Owner Identification** The top of the screen displays a bar identifying the user who started the estimation as the **estimation owner**and the estimation status (on the info icon tooltip). * **Voters List** Below the estimation owner identification, avatars of the voters who have voted during the session are shown. Hovering over an avatar displays the voter's name in a tooltip. If no one has voted yet, the message **"No one estimated yet"** is displayed. ![image-20250327-141935.png](https://atlassianapps.sngular.com/__attachments/a_14d1132b7bc4d07d7fa8d4f2dbc3def388992dc034835becd4a653c0a4441b81/image-20250327-141935.png?cb=b31096130687015f03b6d32f900406fa) Voters list * **Selected Method Identification** The selected estimation method is displayed on the screen. * **Additional Information for Dynamic Methods** * **Fist to Five:** Located above the voting pad on the right, you'll see the **proposed value** entered by the owner. * **Wisdom of the Crowd:** The four **numeric values** entered by the estimation owner are presented as the voting options in the voting pad. * **Voting Pad** Below the method information, a voting pad with all the options from the selected method is presented. * **Estimation Owner Controls** As the estimation owner, you will see two additional buttons below the voting pad: * **Stop:** Click this button to terminate the voting and move on to the results screen. * **Delete:** Click this button to discard the current estimation session and return to the previous step (method selection). **Voter Interaction** As a voter, click on an option in the voting pad to submit your estimate. Your selected option will be highlighted. You can change your vote at any time by clicking on a different option. **Key Aspects** * **Bias-Free Estimations** Your individual estimates remain private and are not visible to other participants until the owner stops the voting. This helps to minimize bias in the estimation process. * **Live Interaction** During a synchronous estimation session, votes and actions are updated instantly for all participants, ensuring a real-time collaborative experience. --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ”„ Re-estimating an Issue Clicking the **Re-estimate** button will take you to the scale selection screen (as described in [Scenario 1: No Existing Estimation - Selecting a Method](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/starting-the-estimation-process.md#Scenario-1:-No-Existing-Estimation---Selecting-a-Scale)), where you can choose the estimation method and set the estimation's anonymity level before starting the new session. You will also see an additional **Cancel** button: ![Re-estimate screen](https://atlassianapps.sngular.com/__attachments/a_c4454dcdcc6e536ee8994626b218eb1f6ed2e36608048e824cc170663a792968/image-20250404-094224.png?cb=f07c5375e57e49dff95b8140021535f3) Re-estimate screen Clicking **Cancel** will take you back to the screen showing the current estimation without starting a new session. --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ—’ Release Notes This page provides a comprehensive overview of the release history for Shared Estimations for Jira. Browse the entries below to learn about new features, bug fixes, and important announcements. **Entries:** * [09-05-2025: Estimation Result Anonymity Control](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/09-05-2025-estimation-result-anonymity-control.md) * [03-04-2025: Version 4 - Update: New UI, Features, and Refactoring](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/03-04-2025-version-4-update-new-ui-features-and-re.md) * [06-03-2024: Shared Estimations for Jira Data Center Official Launch](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/06-03-2024-shared-estimations-for-jira-data-center.md) * [11-01-2024: Shared Estimations Joins TecnoFor Apps](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/11-01-2024-shared-estimations-joins-tecnofor-apps.md) --- version: "Latest" variant: "Data Center" language: "en" --- # โ–ถ๏ธ Starting the Estimation Process The initial screen you see when accessing*Shared Estimations* for a Jira issue depends on whether the designated Jira "Story Points" field already contains a value. ## **Scenario 1: No Existing Estimation - Selecting a Method** If the Jira "Story Points" field is empty and this is the first time you are estimating this issue, you'll see this screen. ![Scale selection form](https://atlassianapps.sngular.com/__attachments/a_f538516b646fb63baa8d1bca2e7b3077d5ee8d9c6e6ca543810bd71eaad4ac04/image-20250404-092621.png?cb=5f350631a73b4a5acd3cde30ff410b5f) Selecting estimation method This screen presents several options to configure before starting the estimation: ### **Estimation Method** Choose an estimation method from the dropdown menu. 1. Some options are **Dynamic Methods**, where participants propose their own numerical value instead of selecting from a predefined list. These require additional input when starting the estimation: * **Fist to Five:** If selected, the estimation owner will be prompted to enter a proposed value (1-99) to initiate the discussion. ![Fist to five](/__attachments/a_174e781bca386dfe3127f092ce1a35a427740f37ccdc0bca0374b02cbe96e09b/image-20250404-092727.png?cb=e2faad7022e404ccc084ecfa1e2e44aa) Fist to five method * **Wisdom of the Crowd:** If selected, the estimation owner will be prompted to enter four unique numeric values (1-99) as initial proposals. ![Wisdom of the crowd](/__attachments/a_9bd4af84d554f6c6f16709002d4c98fab352181f259122cce6fb5805ba99a9e7/image-20250404-092814.png?cb=b91a9779e2931a014696411cefe59b44) Wisdom of the crowd method **Estimation Anonymity Toggle** * A toggle allows the estimation owner to choose whether the *results* of the estimation will be anonymous or non-anonymous. * **Default:** Estimations are **anonymous** by default. * **Anonymous Mode:** * During the voting phase, participant votes are *always* hidden to prevent bias. * When the estimation concludes and results are displayed, you will see the distribution of votes and the list of participants, but individual votes *will not* be linked to specific participants. * **Non-Anonymous Mode:** * During the voting phase, participant votes are *always* hidden to prevent bias (same as anonymous mode). * When the estimation concludes and results are displayed, the specific vote cast by each participant *will be shown* next to their name. 2. **Start Estimation** Once you have selected a method, provided any required input (for Dynamic Methods), **and set the desired anonymity level** , click the **Start** button to begin the estimation session. ### **Scenario 2: Existing Estimation Found** If the Jira "Story Points" field already contains an estimation value, you will see a screen like this: ![Re-estimate screen](https://atlassianapps.sngular.com/__attachments/a_cb0fd4eb816b207688845f8ccb77aef3cc82d126c62bd682dda9bd1f90ccf0e6/image-20250327-141205.png?cb=6fdf07c4ca42a0f3fb6a1edce5e673d6) Existing estimation screen This screen displays the current estimation. To start a new estimation session, click the **Re-estimate** button. Clicking **Re-estimate** will take you to the setup screen (described in Scenario 1) where you can select the method and anonymity setting for the new estimation round. --- version: "Latest" variant: "Data Center" language: "en" --- # T-Shirt Size **Estimation Process** * When this method is selected, users will vote using the sizes **XS, S, M, L, XL, XXL,** and**XXXL** as options. * During voting, these sizes will be presented in the voting pad * The results will show the distribution of votes across these sizes. **General Purpose** The **T-Shirt Size** method is used for a high-level, less precise estimation, focusing on the relative size or effort required for a task. It's useful for initial planning or when detailed estimation is not yet feasible. **Correlation with Story Points** The **T-Shirt size** values in *Shared Estimations* are directly correlated with the following story point values: | **T-Shirt Size** | **Story Points** | |------------------|------------------| | **XS** | 1 | | **S** | 4 | | **M** | 7 | | **L** | 13 | | **XL** | 20 | | **XXL** | 40 | | **XXXL** | 80 | When a T-Shirt size is selected as the final estimation, the corresponding story point value will be set in the Jira "Story Points" field. --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ“Understanding Estimation Methods ## **A Note on Result Anonymity** Beyond selecting *how* your team estimates (the method), there's also a choice in *how the results are displayed* once voting concludes. Before starting an estimation session, the owner can set the results mode (detailed [**here**](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/starting-the-estimation-process.md#Estimation-Anonymity-Toggle)): * **Anonymous Results (Default):** When results are shown, you'll see the overall vote distribution (e.g., how many people voted '5', how many voted '8') and who participated, but individual votes are *not* linked back to specific participants. * **Non-Anonymous Results:** When results are shown, you'll see the overall distribution *and* the specific vote cast by each participant linked to their name/avatar. **Important:** Regardless of this setting, the *voting process itself* always remains anonymous while it's happening to ensure unbiased input from all participants. This setting only affects the final results display. Click on the links below to learn more about each estimation method available in *Shared Estimations*: * [Fibonacci](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/fibonacci.md) * [Linear](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/linear.md) * [T-Shirt Size](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/t-shirt-size.md) * [Fist to Five](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/fist-to-five.md) * [Wisdom of the Crowd](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/wisdom-of-the-crowd.md) --- version: "Latest" variant: "Data Center" language: "en" --- # โš™๏ธ Using Shared Estimations This section guides you through the core functionalities of *Shared Estimations*. Learn how to initiate estimation sessions, participate in the voting process, understand the different stages of estimation, and view the final results. * [โ–ถ๏ธ Starting the Estimation Process](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/starting-the-estimation-process.md) * [๐Ÿ”„ Re-estimating an Issue](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/re-estimating-an-issue.md) * [๐Ÿ—ณ๏ธ Participating in Estimation Sessions](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/participating-in-estimation-sessions.md) * [๐Ÿ“ˆ Viewing Estimation Results](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/viewing-estimation-results.md) --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ“ˆ Viewing Estimation Results Once the estimation owner clicks the **Stop** button in the previous step, the results of the voting are displayed. The way results are displayed, specifically whether individual votes are linked to participants, depends on whether the estimation was set to **anonymous** or **non-anonymous** before starting. ![Estimation owner results screen - Bar Chart](https://atlassianapps.sngular.com/__attachments/a_d36b5301affa46ee0df765c77d14b84071ee1d4e4c7d4785e9a3ca19a6c5e3bf/image-20250408-122148.png?cb=eb671f8e7ae94d5395fd45d3a568cf2f) Anonymous estimation owner results screen - Bar Chart ![Estimation owner results screen - Pie Chart](https://atlassianapps.sngular.com/__attachments/a_45e0bb50cd86f7a199ae7c28b005c29877d3bd1954a6e5d2c34150748d7fbb68/image-20250408-121922.png?cb=f8ae1e60579392d3a915ec943f5cd5a7) Anonymous estimation owner results screen - Pie Chart ![Non-anonymous estimation results screen - Bar Chart](https://atlassianapps.sngular.com/__attachments/a_6106626e8edf2f16e43062dbfa6bf6f241fa330e1b8cbbf4bc211bbbdb9e1c25/image-20250408-122324.png?cb=3f47560848c31eab8ab9319264d007cf) Non-anonymous estimation user results screen - Bar Chart ![Anonymous estimation user results screen - Pie Chart](https://atlassianapps.sngular.com/__attachments/a_c1776b64e630d1fbb3a4b4d5914d0e59f6579ff6ca2ccf16912a2fb20275b345/image-20250408-122016.png?cb=be5a83db448c9212d3946a1f013020a2) Anonymous estimation user results screen - Pie Chart * **Estimation Owner Identification** The owner identification bar remains at the top. * **Dashboard** * **For Wisdom of the Crowd:** A **bar** chart displays the frequency of each voted value. * **For the remaining methods:** The distribution of votes is represented using a **pie** chart. * Below the chart, a voting details section can be expanded. * **In Anonymous Mode:** This section shows the avatars of all participants but *not* their individual votes. * **In Non-Anonymous Mode:** This section shows the avatars of all participants *and* the specific value each participant voted for. * **Estimation Owner Controls** The estimation owner's controls are displayed below the dashboard: * **Suggested Estimation:** The most commonly voted value is suggested. For the **Fist to Five** method, the suggested estimation field is disabled, showing the proposed value. * **Action Buttons:** * **Submit:** Click this to finalize the estimation and update the Jira "Story Points" field. * **Restart Voting:** Click this to discard the current results and start another round of voting. **After Submitting the Estimation** When the owner clicks **Submit** , the submitted estimation will be recorded on the Jira "Story Points" field, and the app will reflect the [Existing Estimation Found](https://atlassianapps.sngular.com/shared-estimations-for-jira/Working-version/Data-Center/starting-the-estimation-process.md#Scenario-2:-Existing-Estimation-Found) state. This means the submitted estimation will be displayed in the *Shared Estimations*section of the Jira issue, and the option to initiate a re-estimation will be available to anyone who accesses it. --- version: "Latest" variant: "Data Center" language: "en" --- # ๐Ÿ”„ What's Changed for Existing Users # ๐Ÿ”„ What's Changed for Existing Users This version of *Shared Estimations* has been significantly refactored to provide a better user experience, improved performance, and a foundation for future enhancements. Key changes include: * **Seamless Jira Integration:** The app seamlessly integrates with Jira's "Story Points" field, ensuring that finalized estimations are directly reflected in your Jira issues. * **UI Redesign:** The most noticeable change is the completely new user interface. Familiarize yourself with the new layout and workflows. * **Enhanced Performance:** Under-the-hood improvements for faster loading and smoother interactions. * **New Features:** Introduction of dynamic methods (Fist to Five and Wisdom of the Crowd), anonymous methods, different chart types for results, and improved voting interaction. * The **Fist to Five** method has been updated and is incompatible with previous estimations. Existing active sessions will be removed during the upgrade due to this incompatibility. All the saved estimations will be preserved. * New dynamic methods (**Fist to Five** requiring a proposed value and **Wisdom of the Crowd** with custom options) have been introduced. * A method has been removed: **Planning Cards,** due to its high similarity with the Fibonacci method. All the saved estimations will be preserved. * **Control Over Estimation Result Anonymity:** A major addition is the ability for the estimation owner to choose how results are displayed *after* voting ends. A new toggle on the estimation setup screen allows selecting: * **Anonymous Results (Default):** Shows vote distribution and participants but *not* who voted for what. **This is the new default setting.** * **Non-Anonymous Results:**Shows who voted for what. * *(Clarification: While voting is in progress, it always remains anonymous in both modes to prevent bias. This setting only affects the final results display.)* * **Technology Upgrade:** The app has been rebuilt using modern technologies. * **Streamlined Estimation:** The core estimation methods have been restructured into a clear and prioritized flow. * **Themed Consistency:** Shared Estimations seamlessly integrates with your Jira theme, providing a native and consistent user experience, and full compatibility with Jira's dark mode has been implemented for Jira 10 instances. --- version: "Latest" variant: "Data Center" language: "en" --- # Wisdom of the Crowd **Estimation Process** * When this method is selected, the user initiating the estimation (the owner) will be prompted to enter **four unique numeric values** (1-99). * These four values will be presented as the voting options in the voting pad. * The results will show the distribution of votes across the four options and the list of participants. **General Purpose** This method leverages the collective wisdom of the team by providing a limited set of options chosen by the estimation owner. It's useful when trying to converge on an estimate from a range of possibilities or when seeking diverse perspectives. **Correlation with Story Points** The estimation value the owner submits is stored in the Jira "Story Point" field for the task. --- version: "Working version" variant: "Cloud" language: "en" --- # Marked for Confluence ## Marked for Confluence Keep your Confluence pages always up to date by rendering remote content in markdown ### News * #### [New documentation of the App in http://wiki.tecnofor.es](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/new-documentation-of-the-app-in-http-wiki-tecnofor.md) July 17, 2024 ### Pinned articles * #### [๐ŸŽž Video-tutorials](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/video-tutorials.md) Video-tutorials https://www.youtube.com/watch?v=TiQIYrGS6_4 ### Documentation * #### [๐Ÿš€Getting started](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/copy-of-getting-started.md) * #### [๐Ÿ›  General Configuration](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/general-configuration.md) * #### [๐ŸŒˆ General Usage](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/general-usage.md) * #### [๐Ÿ’ก FAQ](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/faq.md) #### [๐Ÿ—’ Release Notes](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/release-notes.md) * #### [๐ŸŽž Video-tutorials](https://atlassianapps.sngular.com/marked-for-confluence/Working-version/Cloud/video-tutorials.md) --- version: "Working version" variant: "Cloud" language: "en" --- # ๐Ÿš€Getting started ## Install the App ## Install and configuration Follow the classic way to install using the ***Find new apps*** , and look for "***Marked***" 1. Log into your Confluence instance as an admin. 2. Click the admin dropdown and choose **Add-ons** . The *Manage add-ons* screen loads. 3. Click **Find new add-ons** from the left-hand side of the page. 4. Locate **marked** via search. Results include add-on versions compatible with your Confluence instance. 5. Click **Install** to download and install your add-on. 6. You're all set! Click **Close** in the *Installed and ready to go* dialog. ![https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_01_09.png?version=1&modificationDate=1712584946172&api=v2](https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_01_09.png?version=1&modificationDate=1712584946172&api=v2) --- version: "Working version" variant: "Cloud" language: "en" --- # ๐Ÿ’ก FAQ ## FAQ --- version: "Working version" variant: "Cloud" language: "en" --- # ๐Ÿ›  General Configuration ## General Configuration ๐Ÿ˜€ ### No General Configuration is needed. Just use it --- version: "Working version" variant: "Cloud" language: "en" --- # ๐ŸŒˆ General Usage ## Usage ### Put the Marked macro in your page: 1. Select *Remote MArkdown* in the *Select macro* dialog. 2. Insert the URL of your raw markdown resource in the input field labeled with *URL*. 3. Preview the rendered result by clicking on *Preview*. 4. Insert the rendered content by clicking on *Insert*. You can now preview and save the document. ![https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_03_04.png?version=2&modificationDate=1712585132200&api=v2](https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_03_04.png?version=2&modificationDate=1712585132200&api=v2) **And put a link to your mardown file** ![https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_01_59.png?version=1&modificationDate=1712585097283&api=v2](https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_01_59.png?version=1&modificationDate=1712585097283&api=v2) **Result:** ![https://confluenceextranet.tecnofor.es/download/attachments/153059341/Marked2.png?version=1&modificationDate=1712584650748&api=v2](https://confluenceextranet.tecnofor.es/download/attachments/153059341/Marked2.png?version=1&modificationDate=1712584650748&api=v2) **๐Ÿ‘‡** ![https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_06_04.png?version=1&modificationDate=1712585204060&api=v2](https://confluenceextranet.tecnofor.es/download/attachments/153059341/Calendario_%20Ra%C3%BAl%20Pel%C3%A1ez%20Mendoza%20-%20Outlook%20-%20Google%20Chrome%2008_04_2024%2016_06_04.png?version=1&modificationDate=1712585204060&api=v2) --- version: "Working version" variant: "Cloud" language: "en" --- # New documentation of the App in http://wiki.tecnofor.es New documentation of the App in [http://wiki.tecnofor.es](http://wiki.tecnofor.es/) [Next Page](https://atlassianapps.sngular.com/llms-full.txt/1)