4 ms·

A first party version of apps that have been built with langchain is great but I'm dissapointed to not see Jira here yet. I have been playing around with GPT-4

A first party version of apps that have been built with langchain is great but I'm dissapointed to not see Jira here yet. I have been playing around with GPT-4 parsing plaintext tickets and it is amazing what it does with the proper amount of context. It can draft tickets, familiarize itself with your stack by knowing all the tickets, understand the relationship between blockers, tell you why tickets are being blocked and the importance behind it. It can tell you what tickets should be prioritized and if you let it roleplay as a PM it'll suggest what role to be hiring for. I've only used it for a side project and I've always felt lonely working on solo side projects, but it is genuinly exciting to give it updates and have it draft emails on the latest progress. The first issue tracker to develop a plugin is what I'm moving towards.

jasondigitized 4y ago
Tell me more. Are you feeding it a epic and all stories and subtasks? What are your prompts?
- JCharante 4y ago
  I gave it a paragraph "hiring" GPT-4 and explaining our mission. Then a sentence overview of our two projects (api and app) as well as a description of similar apps and how we're different. Then I have about 12 tickets written in plaintext like this: Issue ID: GD-012 Type: Task Title: [api] Migrate to TRPC from express/rest Assignee: John Status: In Progress --Description Beginning-- --Description End-- Because the outputs are really long, here's an example of my interactions with Dave (the name I gave to GPT-4). There's also emails Dave has created to fictional stakeholders but that's too high up. Right now the problem I'm having is that sometimes Dave can remember the issue tracker state but when trying to output (so that I can store it) it can't produce a long enough output (now, it worked before when I had 6 tickets). If I were to cram everything into 1 prompt then it would probably work, but a better solution is to use langchain and a document loader for issues. I believe that if I was able to vectorize the codebase so that if could search for relavent portions of code (at work a lot of our tickets were "update this endpoint to handle case X, we did it to this other endpoint 6 months ago (link to PR)) and have a proper store of issues then it could be powerful. Creating epics: https://poe.com/s/Qu62LtlV2yKGZXlXTTS1 https://poe.com/s/Qu62LtlV2yKGZXlXTTS1 Explaining blockers: https://poe.com/s/vnE0SsI3e55WT1t6fkNW https://poe.com/s/vnE0SsI3e55WT1t6fkNW Creating tickets with a recommended checklist of tasks: https://poe.com/s/SJ3RPF7ecHSYEBJKS76z https://poe.com/s/SJ3RPF7ecHSYEBJKS76z
  - Jayakumark 4y ago
    This is awesome , will you be able to share the initial prompt. When I tried the same prompt to create epic, it’s missing multiple stories on GPT-4. Like validating OTP, Resending OTP and Logging for audit it did generate the other 3 though. Not sure why. But yours is spot on.

jasondigitized 4y ago

Tell me more. Are you feeding it a epic and all stories and subtasks? What are your prompts?

JCharante 4y ago
I gave it a paragraph "hiring" GPT-4 and explaining our mission. Then a sentence overview of our two projects (api and app) as well as a description of similar apps and how we're different. Then I have about 12 tickets written in plaintext like this: Issue ID: GD-012 Type: Task Title: [api] Migrate to TRPC from express/rest Assignee: John Status: In Progress --Description Beginning-- --Description End-- Because the outputs are really long, here's an example of my interactions with Dave (the name I gave to GPT-4). There's also emails Dave has created to fictional stakeholders but that's too high up. Right now the problem I'm having is that sometimes Dave can remember the issue tracker state but when trying to output (so that I can store it) it can't produce a long enough output (now, it worked before when I had 6 tickets). If I were to cram everything into 1 prompt then it would probably work, but a better solution is to use langchain and a document loader for issues. I believe that if I was able to vectorize the codebase so that if could search for relavent portions of code (at work a lot of our tickets were "update this endpoint to handle case X, we did it to this other endpoint 6 months ago (link to PR)) and have a proper store of issues then it could be powerful. Creating epics: https://poe.com/s/Qu62LtlV2yKGZXlXTTS1 https://poe.com/s/Qu62LtlV2yKGZXlXTTS1 Explaining blockers: https://poe.com/s/vnE0SsI3e55WT1t6fkNW https://poe.com/s/vnE0SsI3e55WT1t6fkNW Creating tickets with a recommended checklist of tasks: https://poe.com/s/SJ3RPF7ecHSYEBJKS76z https://poe.com/s/SJ3RPF7ecHSYEBJKS76z
- Jayakumark 4y ago
  This is awesome , will you be able to share the initial prompt. When I tried the same prompt to create epic, it’s missing multiple stories on GPT-4. Like validating OTP, Resending OTP and Logging for audit it did generate the other 3 though. Not sure why. But yours is spot on.