Some of the information we put in confluence are time-sensitive and need to update or delete after a certain period. But confluence doesn't have out of box support to configure expiry dates for pages and easily find out expired content. This was a major problem for our team as we kick-off new phase of the project in every quarter and we have to update some pages at the end and start of each quarter. And one of our recent audit findings was having outdated information in our project documentation. This all inspired me to develop this add-on.
What it does
This add-on allows users to set expiry dates for confluence pages and blog posts. Then the pages will display expiry status on top of the page and that status will be automatically updated after the expiry date from 'Up to date' to 'Expired'. Moreover, the add-on enables users to search pages by expiry date and status. So users can easily find out expired pages and pages which are going to expire soon.
How I built it
Using Atlassian Connect Express. I configured MySQL database for storing data and use AWS to deploy the product.
Challenges I ran into
Understanding how Atlassian Connect Express work was challenging. I had to go through the source code and understand how the framework works in certain scenarios.
Accomplishments that I'm proud of
This is my first confluence add-on as well as my first nodejs application. Also, I'm proud of the fact that this add-on is going solve a real problem most confluence-users have.
What I learned
- Developing Atlassian Connect add-ons
- Nodejs development
- AWS Beanstalk
What's next for Expirator
- Assign user who is responsible for keep a page up to date
- Send notification to watches and assignee
- Macro to display list of expired pages
- Macro which allows configuring different expire dates for different sections on the same page