Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Qodo automatically verifies PR complies with Jira ticket or GitHub issue

qodo.ai

Post reply on HN
Print view View original

1–10 of 13 posts

Re: Qodo automatically verifies PR complies with Jira ticket or GitHub issue

#3

Post by truculent »

> explore how AI can assist in this workflow, and discuss how Qodo Merge, which just released support for Jira tickets, can help with maintaining code quality

“And now it begins,” said Ser Arthur Dayne, the Sword of the Morning. He unsheathed Dawn and held it with both hands. The blade was pale as milkglass, alive with light. “No,” Ned said with sadness in his voice. “Now it ends.”

Re: Qodo automatically verifies PR complies with Jira ticket or GitHub issue

#4

Post by Spivak »

This marketing page is the word equivalent of those As Seen on TV ads that try to portray simple tasks as utterly impossible. Oh no your developers with 2+ screens might have to Alt-Tab sometimes, the horror.

Definitely a product that exists simply because it was easy to build not because it's actually useful.

Re: Qodo automatically verifies PR complies with Jira ticket or GitHub issue

#5

Post by KingOfCoders »

I got excited, but then there is no "automatically verifies PR compliancy" in the text. As far as I can see it searches JIRA etc. and puts the data next to the PR for the developer to verify.

"With Qodo Merge, the team can effortlessly view each ticket’s details within their code editor or PR, reducing interruptions and enabling a more cohesive workflow. Developers can easily cross-check code with ticket requirements as they work."

The title is beyond click-bait and marketing.

Re: Qodo automatically verifies PR complies with Jira ticket or GitHub issue

#6

Post by alias_neo »

Spivak wrote: post #4

This marketing page is the word equivalent of those As Seen on TV ads that try to portray simple tasks as utterly impossible. Oh no your developers with 2+ screens might have to Alt-Tab sometimes, the horror . Definitely a product that exists simply because it was easy to build not because it's actually useful.

I mean, I don't think something that can show me the requirements alongside the thing I'm working on is entirely useless; especially if I'm jumping between projects/tickets, which I do, but I'm not sure why it needs ML/AI, like you say, the text of the ticket/requirement on another screen is good enough, an improvement would be showing it in the same pane with auto-context-switching, but this doesn't appear to be that.

Re: Qodo automatically verifies PR complies with Jira ticket or GitHub issue

#8

Post by bobismyuncle »

KingOfCoders wrote: post #5

I got excited, but then there is no "automatically verifies PR compliancy" in the text. As far as I can see it searches JIRA etc. and puts the data next to the PR for the developer to verify. "With Qodo Merge, the team can effortlessly view each ticket’s details within their code editor or PR, reducing interruptions and enabling a more cohesive workflow. Developers can easily cross-check code with ticket requirements…

I think it does actually do automated compliance checks.

"The Qodo Merge code review agent addresses these challenges by establishing an automated connection between ticket management systems and code reviews. The tool fetches ticket context from Jira or GitHub Issues when referenced in pull requests, then evaluates how closely the code changes align with the ticket’s requirements. It assigns compliance levels of “Fully compliant,” “Partially compliant,” or “Not compliant,” while maintaining a detailed audit trail of all reviews and changes."

From here: https://sdtimes.com/qodo-launches-automated-compliance-check...

Re: Qodo automatically verifies PR complies with Jira ticket or GitHub issue

#10

Post by onionisafruit »

mdaniel wrote: post #7

Heh, the person who thought up this idea clearly does not work where I work, because no one, AI or not, has any idea what complying with the Jira would mean

This part seems like pure fantasy to me. I’ve never worked anywhere that had detailed tickets. I’m lucky to get a two sentence description beyond the issue title. Although the few times I’ve had somebody try to fully spec out a ticket it’s been riddled with so many wrong assumptions that my first task was rewriting it.

> These tickets often include detailed functional specifications, design mockups, data models, and interface definitions that outline what needs to be developed. They also specify non-functional requirements such as performance benchmarks, security protocols, scalability considerations, and compliance standards that dictate how the solution should be implemented.

Post reply on HN