(Psst... The article is written with the help of AI 🙃)
🌃 Introduction
As a software developer, I frequently use JIRA for ticket management. Recently, JIRA has integrated AI features that summarize documents and provide AI-generated answers from searches.
However, it cannot still summarize comments and generate ticket descriptions. You might wonder why these features are necessary. When working with cross-functional teams on a significant feature, extensive planning and discussions occur in JIRA comments. Over time, it becomes challenging to track these discussions, and crucial decisions can be overlooked during the development phase. AI can help by summarizing all discussions and highlighting key decisions and steps.
Additionally, writing clear and concise ticket descriptions is essential to avoid confusion among colleagues picking up tasks. Effective communication is a vital skill for software developers, but it can be challenging to master and requires practice. Leveraging AI can assist in crafting better task descriptions and sharing ideas more effectively.
🔗 Useful Links
Live Website - https://project-ai-wheat.vercel.app/
Github - https://github.com/rushilp2311/project-ai
Demo Login for the website
demo@pinpoint.com // Demo1234
Don't have time to go through website yourself. Check the walkthrough video below.
💥 Features
Create Projects
Add Tasks for the features under the project
Assign tasks to users
Update the status of the task
Add comments for discussion under a task
Generate descriptions with AI
Create summaries from comments with AI
🎥 Walkthrough
💻 Technologies used
Here is the list of frameworks and tools used.
NextJS - with Typescript
Postgres - Hosted by Vercel
TailwindCSS
ShadCN UI - For components
Groq Cloud for LLM APIs - llama3-8b-8192 is the choice of LLM
Vercel Analytics for basic user metrics
https://www.logotouse.com/ for logo
I have used the Next.js App router and Vercel to deploy the website and PostgreSQL.
Groq Cloud provides a generous free tier to use AI models. I would recommend using it.
Ending Note
I will be updating the GitHub repo and this article in the coming days before the deadline. So stay tuned for more info on the contribution guide and how the code is structured.
In the end, I would say that I had fun working on this project. I will try adding more features in the future, so any contributions are most welcome.