Here are the answers to some of your most frequently asked questions. If you think we’re missing any critical tips, let us know by getting in touch with us through the Appfire Support Portal.
🎯 On this page:
What is the price for the plugin? Can I pay only for users that use Agile Poker for Jira?
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.
How can I access Agile Poker for Jira Cloud plugin?
To access the Agile Poker for Jira plugin, simply navigate to the left side menu within each project or board. Look for the app section and select the Agile 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.
What’s the difference between Asynchronous and Interactive estimation sessions?
In the Interactive session, the moderator takes a story or task from the backlog, discusses the details, and then each team member shares his or her estimate for the story point value. The Asynchronous method is similar in that each team member shares their estimate, but this doesn’t happen in real-time. It is frequently used by teams working remotely, especially ones that have members living in different time zones. Check out some of the differences listed below:
Interactive Session | Asynchronous Session | |
---|---|---|
Collaboration | Real-time collaboration among team members. Team members discuss and estimate together. | Participants estimate individually and at their convenience. The final estimates can be submitted asynchronously or interactively based on the team’s preferences. |
Time Flexibility | Requires synchronous participation. | Allows flexibility for participants' time. |
Observer |
|
|
Result | Consensus-based estimations | Consultation-based estimations |
What’s the difference between Relative and Bucket Sizing estimation sessions?
During Relative estimation, teams estimate the effort required to complete a project by comparing each task to another one. Meanwhile, during Bucket Sizing, teams sort issues into predefined columns based on their estimation. It’s a little like using Relative estimation, but more focused because your estimation values (your “buckets”) are already set. Team members just drop each issue into the right size “bucket.” Check out the table below for a brief overview of the key differences:
Relative Session | Bucket Sizing Session | |
---|---|---|
Estimation Method | Participants compare issues to each other by dragging and dropping them across the board. The estimation values are given at the end. | Participants place issues into labeled buckets based on relative size. |
Speed | Fast, but it’s slower than Bucket Sizing | Fastest session type |
Why can’t I save the estimate to Jira?
The inability to save the estimate to Jira could be due to specific configuration settings. It is essential to ensure that the estimation field is correctly set as valid for the appropriate issue types. If certain issues like bugs or tasks are not visible in Agile Poker for Jira, it indicates the need to add an estimation field, such as Story Points, to the relevant issue type. For detailed instructions on configuration, you can refer to the documentation available here. By following these steps, you'll be able to seamlessly save estimates in Jira.
Why don’t I see any sessions in the project while others see them?
Agile Poker for Jira has been designed in the context of Jira boards. If there are multiple boards within the project, it is possible for users to see different sessions based on the specific boards, even if they are part of the same project. If you are unable to see a particular session, please ensure that you are accessing Agile Poker for Jira from the correct board. By navigating to the appropriate board, you should be able to view the sessions and participate seamlessly.
Why can’t I vote for issues in the Agile Poker session?
Agile Poker for Jira offers different user roles to ensure effective collaboration. During configuration, specific roles are assigned to users. In this case, only moderators and estimators have the privilege to vote for issues, while observers do not possess this capability.
If you find yourself unable to vote for issues in Agile Poker for Jira, it is recommended to review the Participants configuration to determine your assigned role. By checking your role, you can understand the limitations and capabilities associated with your account in the Agile Poker session.
Why do I only see the message "Wait for the moderator to start" while I'm in the session?
In Agile 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.
As the moderator, how can invite users to the session?
Every session created in Agile Poker for Jira Cloud generates a unique link that can be shared via email or any other convenient communication channel. For Asynchronous sessions, participants can be invited via Slack as well.
To retrieve the session link, navigate to the session configuration and locate the Participant section. Under the Session link field, you will find the link. Alternatively, you can copy the link from the browser’s address bar or use a copy link option from the estimation session’s breadcrumbs (the copy link button displays when you hover over the breadcrumbs).
The benefit of sharing the link is that you don't need to individually add users as participants. When users access the session through the shared link, they will automatically be added as participants.
Is it possible to estimate more than one estimation field?
Absolutely! Agile Poker for Jira offers the flexibility to create Multi-field estimation sessions in Interactive and Asynchronous session types. In the Create session view for these session types, you can enable the Multi-field estimation toggle. This allows you to select multiple Estimation fields for your session. You can choose as many estimation fields as needed to capture different aspects or dimensions of estimation. There is also an option to select the Final score formula, which calculates the overall score based on the selected estimation fields.
Can I estimate Epics and Subtasks as well?
Agile Poker for Jira gives the ability to also estimate the Epics and Subtasks. When selecting issues for estimation, the moderator has the ability to choose which issue types should be included. This option can be found in the Select Issues view. Simply locate the Issue type dropdown next to the Filter field and toggle the option accordingly. By enabling this toggle, you can include Epics and Subtasks in the estimation process, gaining a more comprehensive understanding of effort across different levels of work granularity.
Is it possible to estimate issues from various projects in one Agile Poker session?
Sure! This capability is available for Company-Managed Projects (Classic). To include issues from multiple projects, you can edit the board filter to encompass the desired projects. It is essential to ensure that the same estimation field (e.g. Story Points) is being used across all projects. Once you have modified the board scope, whenever you access Agile Poker for Jira from this board, you will be able to select and estimate issues from the adjusted project scope.
Can I have more than one moderator?
Yes, the option to select the moderator is available under the Participants section. In the Moderator field, you have the option to select one specific moderator. However, if you leave this field empty, each user accessing the session will be granted moderator rights.