Content Comparison

...

If you have a project with issues to estimate, you can start your game. You can initiate your game either from the Planning Poker app dashboard or the Jira Backlog view.

If you haven’t created any games yet:	From the Planning Poker app dashboard:	From Jira Backlog view:
Your dashboard will look like this: Image Modified Simply click New game to start configuring your game.	Open the Planning Poker dashboard (Apps > Planning Poker), click New Game. Image Modified	To start a game from Jira Backlog View, you need to have started a sprint in a project. The sprint must include issues you want to estimate. Panel panelIconId atlassian-warning panelIcon :warning: bgColor #F4F5F7 This feature is currently available only in Company-managed projects. Image Modified Go to Backlog view in your project sidebar, and click Open in Planning Poker from the options dropdown. Panel panelIconId atlassian-question_mark panelIcon :question_mark: panelIconText :question_mark: bgColor #F4F5F7 Can’t see the Open in Planning Poker option? This could be because you have the Enhance my board and backlog toggle enabled. Disable it, and try again. Image Modified

...

Step 2: Configure the Planning Poker game

...

3. Estimation field – Select a field from the issue object where the estimated points value will be stored once the issue is estimated. We show you both the field name and its ID, making it easy to distinguish between default fields and fields you've created yourself. You can use the following fields:

   • Story Points: This field stores integers and is suitable for saving numerical estimations like Fibonacci deck-type cards or custom numerical deck cards. It's the default estimation field for Company-managed Jira projects and is recommended.

   • Story Point Estimate: Similar to the previous field, this one also stores integers and serves as the default estimation field for Company-managed projects.

   • Comments: This field stores string values, making it ideal for abstract estimations such as t-shirt sizes or custom deck non-numerical estimation values. It's available by default in all project types.

   • Original Estimate: This field stores time units like 1h, 30m, 5m, etc. It works well with an hours deck type or a custom deck containing cards with time unit estimation values.

   • Custom fields:

...

4. Card deck – Choose the front values on cards that players will use to vote when estimating an issue. You can select from predefined card deck templates or customize them as needed. You can also employ labels to conceal specific values, allowing you to focus on relative sizes rather than fixating on exact numerical values during estimation.

   • Fibonacci: Includes cards with values 1, 2, 3, 5, 8, 13, 21, 34, and 55.

   • T-shirt: Features cards labeled as XXS, XS, S, M, L, XL, and XXL.

   • Labeled T-Shirt: Combines labels with values, such as XXS=0.5, XS=1, S=2, M=3, L=5, XL=8, and XXL=13.

   • Hours: Consists of cards marked as 1h, 2h, 3h, 4h, 5h, 6h, 7h, 8h, 9h, 10h, 11h, and 12h.

   • Custom: Whenever you customize a card deck template using special input, it switches itself to a Custom card deck. When you customize the card deck, use commas to separate different values. This tells you what type of card it is and how many of them there are. If you put in three values separated by commas, players get only three cards for estimating issues in the game.

...

...

...

...

5. Add "?" and "coffee" cards to the deck – If enabled, this adds two extra cards to your deck:

   

   • "?" – Allows a player to express uncertainty when estimating the current issue.

   • "coffee" – Allows a player to inform other game participants that they need a break.

6. Game administrators – Select who will manage the session. By default, the game creator has full administrative control. Here you can also add multiple game admins by simply selecting their names from the dropdown. This list will also display users who currently have administrative privileges regarding the game. To take away their admin privileges, simply click the red cross icon next to the user's name.
   Estimators – Select the estimators.
   Spectators – If there are any, select the spectators.

...

7. Invite participants via email – Notify project participants about their involvement in a Planning Poker game via email. This is useful if the estimation session is being held remotely or you’ve set the game type to be Private. Notification email(s), which contain a URL for seamless access to the game, will be sent in bulk to all the users in the list.

   

...

8. Add custom fields to game layout – Custom field fields will be automatically distributed by the order of selection.
   

...

9. Enable estimation context – This powerful feature in Planning Poker helps you make better estimations in a Scrum approach. When the voting phase starts and you hover over a card with a value (e.g., 3), Planning Poker will search for all previous issues in the project that were estimated as 3. This helps you see how similar issues were estimated in the past:

   

   Limit issues pool for estimation context – Here you can control the context to fit your needs. Use this to reduce the default scope of the estimation context JQL. This will be an additional query command merged as AND condition. For example, you could set the Estimation context to display only display issues with specific labels, like design and UX, by entering the following JQL query into the Estimation context settings input: labels IN (design, UX).

10. Labels –

    • Add labels after estimation – To tag estimated issues, just enter the label you want. When you save the estimation, the label will be added to the issue.

    • Add labels to skipped issues – To tag issues that are postponed or canceled, enter the desired label. The label will be added to an issue when the admin clicks either the "Skip and postpone" or "Skip and remove" button.

...

1. Issue name – Search for specific issues using this search box.

2. Project – Choose specific Jira projects from which the issues will be sourced for estimation.

3. Issue Type – Filter issues based on their type, such as Change, Incident, Bug, Epic, Problem, Service request, and more.

4. Status – Select issues based on their current status within the workflow. Options could include Authorize, Draft, Awaiting approval, and more.

5. Sprint – Filter issues associated with a particular sprint.

6. + More – Use this dropdown to add additional filters to your filter bar. Once the filter is selected in the dropdown, it will be added to your filters bar and you will be able to use it along with the default filters.

7. Order by – This option enables you to organize items in the game backlog effectively. You can sort items based on various criteria, including Jira rank, priority, and status, with the flexibility to arrange them in either ascending or descending order. When sorting by a single field, you have the option to toggle between filter mode and JQL mode. By default, the order by rank is set to ascending, consistent with JQL settings.

...

1. .

8. JQL – For advanced users, this button offers the option to switch to Jira Query Language (JQL) for more complex and customized queries. If you're a seasoned Jira user, you can write your own JQL query into input to find issues you want to add to your Planning Poker game. Building a custom JQL query is a flexible approach to commence search in your Jira projects, but to master it you have to know how to deal with operators, expressions, and other features of JQL. Feel free to surf Jira tutorials to learn more about JQL.

...

...

Then, further refine the issues and order them accordingly.

...

Once you have tailored your backlog to best suit your needs, click Start game to start the Planning Poker session. For a breakdown of the game process, refer to the Game flow page.

...

...

...