Simple Planning Poker

Voting integration
Overview over all votes
Settings

Inspiration

Ticket estimation is quite an important part in the development cycle and takes a lot of time and effort if done right. Most teams do the estimation on a consensus-based voting with all team members, where games like planning poker can improve the estimation process a lot. Jira marketplace offers several solutions for playing Planning Poker to estimate Story Points, but they are all pretty complicated and just overkill, so with most of our teams we started to write our vote/estimation in a chat, which is annoying for everyone involved.

What it does

Simple Planning Poker integrates directly into the Jira issue and enables all team members to vote (even asynchrounus), calculates the result, updates the story point estimation on the ticket and shows the votes of all members. It is customizable, simple to use and understand.

How I built it

It was build with the Forge Beta and has no external dependencies.

Challenges I ran into

Finding the correct name for the story point field because it is a jira custom field
Updating the story point value, as it seems there is a bug in Jira where the field permissions seem the be incorrect (i can see the story point field on the ticket, in the ticket settings but it is missing in the schema so I cant update it)
Currently with forge it is not possible to "refresh" the UI based on events, so the I needed a refresh-button as workaround

Accomplishments that I'm proud of

The code architecture is quite well.

What I learned

How complicated but interesting it can be to work with Atlassian Products on the development side. That FaaS can be nicely used for integrating widget-like snippets.