Hot desking for Confluence - The Smart Office

hot desking for Jira

Inspiration

All members of our company are within the Atlassian ecosystem. When the first member joins the company, we first give the member an email, Jira, and Confluence licenses. When there was a requirement for a mobile office for the first time, it was burdensome to introduce new external apps and license our members again. And there is also budget issue. Many members are already familiar with the Confluence and Jira environment, so we thought about using this environment. Therefore, the thought of starting to configure the physical environment from this virtual environment that everyone is using was the beginning of Hot Desking for Confluence.

What it does

Hot Desking for Confluence allows all users within the Atlassian ecosystem (i.e., all members of our company, furthermore all Confluence users) to go deeper than their flexibility, and drive success further with team and community. Therefore, many users can strengthen collaboration through the Atlassian ecosystem and even promote flexibility through Hot Desking for Cofluence. Ultimately, it is to achieve all collaborations in the physical and virtual sense within the Atlassian ecosystem. Our goal is to create a collaborative environment of all types within the Atlassian ecosystem.

How we built it

Define functions with HR team
Team Building
Create a UI with Figma
Implementing features with Forge
Develop using custom UI Because it was developed with Forge, there was no burden on infrastructure design and construction. Because Forge's various development environments were utilized, even in the absence of planners and infrastructure engineers, it was a great help to the development because it was possible to focus on development without much burden.

Challenges we ran into

For the first time, I started to develop without a planning team, and started working with a few functions without a big picture, so it was difficult to improve the functions later. In the HR team standard, the necessary functions were defined first, but users who would use those functions were inconvenient. Since the requirements were not defined properly from the beginning, the design was changed due to the added requirements. However, I was able to develop a clearer app because I could hear and reflect the functions I wanted in the real world. I was worried because there was no infrastructure engineer, but I was able to focus on development without a lot of pressure on that part by developing with Forge.

Accomplishments that we're proud of

While developing “Hot desking for Confluence,” it felt great to actually develop an output that everyone in the organization could use. In fact, the organization was able to save about $3,000/year for the separate Smart Office app, and it was said that the members of the organization were also comfortable because they did not have to go through the process of accessing other apps and managing separate licenses.

What we learned

By implementing many desks as front-end, the understanding of multiple components has increased. I learned the importance of a TEAM 💌

What's next for HOT Desking for Confluence - The Smart Office

First, the goal is to implement meeting room reservations as soon as possible. The next step is to get ideas for developing additional features while using them within our organization, and try to modernize the app. (Status, counting, interworking with external HR systems, etc.) After the final development, I would like to upload the app to the Atlassian Marketplace so that most users in the Atlassian ecosystem can meet Hot Desking for Confluence!