Page Comparison

You can check the price here.

According to Atlassian’s pricing policy, apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum number of users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Management (10 agents) in the same instance, you pay the 50-user price for apps.

You can check the price here.

According to Atlassian’s pricing policy, apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum number of users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Management (10 agents) in the same instance, you pay the 50-user price for apps.

To access the Planning Poker for Jira plugin, simply navigate to the left side menu within each project or board. Look for the app section and select the Planning Poker for Jira tab to access the dedicated dashboard. Additionally, you can also find the application conveniently located in the upper right corner of the native Board view.

Once installed, the Planning Poker will add a new menu item in the Jira top menu and project sidebar.

Jira top menu App > Planning Poker	Software project sidebar

Planning Poker for Jira offers different user roles to ensure effective collaboration. During configuration, specific roles are assigned to users. Only moderators and estimators have the privilege to vote for issues, while spectators do not possess this capability.

If you find yourself unable to vote for issues in Planning Poker for Jira, it is recommended to review the Estimators configuration to determine your assigned role. By checking your role, you can understand the limitations and capabilities associated with your account in the Planning Poker session.

This error happens when it is not possible to set the custom field. In most cases, this is about Story Points field, which is by default not visible on the issue detail view. To fix this problem do the following steps:

1. Go to Project Settings.

2. Click Screens from the sidebar.

   Image RemovedImage Added

3. Click the Screen name of the needed Issue Type.

   Image RemovedImage Added

4. Add your field via the Select Field search box.

   Image RemovedImage Added

5. If you're using Issue New Layout, click on the Issue Layout.

   Image RemovedImage Added

6. Make sure the Story Points field is always visible.

   Image RemovedImage Added

In Planning Poker for Jira, the estimation process within a session is initiated by the moderator. When a new session is created, the moderator needs to manually select the first issue for estimation to commence. This process does not occur automatically. Consequently, participants in the session will see the message "Wait for the moderator to start" until the moderator selects the initial issue and officially begins the estimation.

Simply go to the project sidebar and click Project Settings > Planning Poker. Then turn on the Hide Planning Poker button in the sidebar toggle.

Certainly! Navigate to Manage Apps > Planning Poker > Configure, and check the Disable mobile version box.

Navigate to Manage Apps > Planning Poker > Configure, enable the User permissions will be checked option, and then choose the desired user groups that should have access to Planning Poker.

You can check the price here.

Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
According to Atlassian’s pricing policy, apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Management (25 agents) on the same instance, you should purchase the 500-user tier for apps.

For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.

To access the Planning Poker for Jira DC plugin, simply navigate to the left side menu within each project or board. Look for the Jira navigation bar and select the Planning Poker for Jira tab to access the dedicated dashboard. Additionally, you can also find the application conveniently located in the upper right corner of the native Board view.

Planning Poker for Jira offers different user roles to ensure effective collaboration. During configuration, specific roles are assigned to users. Only moderators and estimators have the privilege to vote for issues, while spectators do not possess this capability.

If you find yourself unable to vote for issues in Planning Poker for Jira, it is recommended to review the Estimators configuration to determine your assigned role. By checking your role, you can understand the limitations and capabilities associated with your account in the Planning Poker session.

In Planning Poker for Jira, the estimation process within a session is initiated by the moderator. When a new session is created, the moderator needs to manually select the first issue for estimation to commence. This process does not occur automatically. Consequently, participants in the session will see the message "Please wait — Game Admin is choosing a story to estimate" until the moderator selects the initial issue and officially begins the estimation.

Alternatively, if the moderator sees "Wait for the moderator to start", there might be a technical issue with the way Jira communicates with the Apache server. There is an option to change the way Planning Poker connects to the Apache server.

By default, it establishes a long-time connection, and you can change the app’s behavior. To do this, navigate to the Manage Apps section in your Administration settings, then go to Planning Poker configuration at the bottom of the left-side menu. Enable the alternative socket transport mode. You can find instructions on how to do this in the following link: poker-server-polling.mp4

This error happens when it is not possible to set the custom field.

In most cases, this is about the Story Points field, which is by default not visible on the issue detail view. To fix this problem, do the following steps:

1. Click the Jira cog icon, and then Issues.

2. Click Screens from the sidebar.

   

3. Navigate to the Screen name of the needed Issue Type, and click Configure.

4. Add your field via the Select Field search box.

   

5. Go to any issue in that project, and click Edit Issue > Configure Fields to make sure the Story Points field is always visible.

   

Simply go to the global settings and click Manage app > OTHER > Planning Poker Configuration. Then turn on the Hide top menu "Planning Poker” link box. 

Certainly! Navigate to Manage app > OTHER > Planning Poker Configuration, and check the Disable mobile version box.