WeOS | Devpost

Inspiration

JIRA is a fantastic project management tool, but it does have its faults. We've used JIRA for years and even as seasoned as we are, we still have challenges finding the information we want. There's always a lever to pull, a report to run or a special section to go to track down the information you need.

As a team that utilizes scrum with 2-week sprints, we rely heavily on the data within JIRA to plan, execute and review our performance on software development projects. So we took on this challenge, not only to win 20k (as nice as that would be) but to also solve some of our own pains and hopefully help other teams like ours.

What it does

WeOS allows you to query your project within JIRA using natural language and get insights instantly. Ask simple questions like:

How did the team perform last sprint/Sprint X?
How many tasks are in the backlog?
Which tickets are assigned to me?

Or more complex questions like

What will be the team’s velocity if Akeem goes on vacation for 4 days next sprint?

With WeOS, you can get answers to these questions and more without the need to navigate through all of JIRA

How we built it

We created a REST api that takes the message that the user sends and passes it to a LLM
The Forge App uses the response from the api to make calls to the JIRA apis that are needed
No information from JIRA is sent to the api (unless the user enters it in the chat)
We made use of the storage api to store the intents and async events to extend the time taken to get a response
We used the latest preview of Forge
UI Kit 2
Storage entities

Challenges we ran into

UI Kit 2 - Limited control on some of the basic components.

Accomplishments that we're proud of

Getting it done in 5 days! (we were initially thinking we would do it as a Connect App but had to adjust after we read the rules properly)
Learning Forge so quickly
Using so much of the "preview" Forge stuff

What we learned

We didn't know much about Forge Apps but it was straightforward to get started with.
There are some nuances, but the documentation helped get to them quickly (most of them)