Skip to main content
Skip table of contents

đź’ˇ 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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.