Inspiration
Sometimes a Jira card takes a lot longer to move to a completed status than expected, but looking at the description, comments and even time spent it can be hard to figure out why. Was the card left unassigned for days, forgotten about? Was it assigned to the wrong person? Was the description too vague that it needed to be passed back and forth until the details were clear?
Finding out who the card has been assigned to and for how long, helps to quickly answer these questions.
What it does
Assignee History searches through the history of all the users that have been assigned to the Jira card. It then calculates the duration each user was assigned to the card as either a total or in a timeline. This makes it easy to detect why a card might be taking so long to reach completion.
How we built it
Assignee History is built with Atlassian Forge, using Forge UI components and Forge APIs.
Challenges we ran into
It took some time understand which APIs and parameters were needed to get the required data, but once that was figured out the development went smoothly.
Accomplishments that we're proud of
This was my first time using Atlassian Forge but I feel I now have a good understanding of it and feel competent using it as a development tool in the future.
What we learned
I have learnt a lot about Atlassian Forge and how to use it to easily create for Jira and Confluence.
What's next for Assignee History
The next step for Assignee History would be adding the ability to display the data in a graph not just in a table so it is even easier to see where the card spent the majority/minority of its time assigned.
Log in or sign up for Devpost to join the conversation.