Open sebastian-sommerfeld-io opened 3 months ago
You can store business value and story points for each user story by using custom fields in GitHub Issues. Here’s how you can do it:
Custom Labels: Use labels to represent business value and story points. For example, you can create labels like business-value: high, story-points: 5.
Issue Templates: Create issue templates that include fields for business value and story points.
Querying: Use GitHub’s search and filtering capabilities to filter issues based on these labels.
For instance, to filter issues with high business value, you can search for label:"business-value: high".
Would you like more detailed steps or help with setting up specific filters?
When you use issue templates in GitHub, the inputs are stored as a single text block in the resulting issue. However, you can still make the fields queryable by using labels or structured text within the issue.
Labels:
label:"story-points: 5"
and label:"business-value: high"
.Structured Text:
Story Points: 5
and Business Value: High
.To filter issues based on these fields, you can use GitHub's search functionality with appropriate queries. For example:
is:issue "Story Points: 5"
is:issue "Business Value: High"
Would you like to see an example of an issue template structure for this?
---
name: User Story
about: Create a new user story
title: "[User Story] "
labels: user-story
assignees: ''
---
**Story Points:**
**Business Value:**
**Description**
Provide a detailed description of the user story.
To filter issues with 5 story points:
is:issue "Story Points: 5"
To filter issues with high business value:
is:issue "Business Value: High"
Using labels to tag issues can make it easier to filter and manage them.
Both are correct, but "needs triage" is more commonly recognized in a broader context.
Using Labels:
As Part of the Issue Description:
story-points: 5
). This allows you to quickly filter and see the complexity of issues at a glance.Would you like specific examples or further assistance with setting up labels or issue templates?
Yes, that distinction makes sense:
Using both labels can help clarify the stages of issue processing in your workflow.
curl \
-H 'Content-Type: application/json' \
-d '{"contents":[{"parts":[{"text":"Explain how AI works"}]}]}' \
-X POST 'https://generativelanguage.googleapis.com/v1beta/models/gemini-1.5-flash-latest:generateContent?key=<API_TOKEN>'
{
"error": {
"code": 400,
"message": "Gemini API free tier is not available in your country. Please enable billing on your project in Google AI Studio.",
"status": "FAILED_PRECONDITION"
}
}
Relates to
ChatGPT infos
:zap: The issue with automated Code Reviews (due to available services)
Using ChatGPT with GitHub Actions like code-review-gpt or using the OpenAI API directly consumes credits for ChatGPT. I already pay for GitHub Copilot. I do not want to pay for a second AI solution. Plus (I assume) it is only a matter of time until Copilot is deeply integrated into GitHub and allows working with PRs and Issues and everything.
Additional non-AI logic
:warning: for Backlog refinement, not Code Reviews
:thought_balloon: It might be better to not just prioritize issues based on score but to use an AI solution right from the start where the score is combined with some AI recommendations.