Assign Jira issues to devboxes
Set up devboxes in Jira
- Sign up for free.
- Connect your Jira site with an account for devboxes, and choose which Jira project belongs to which devboxes project.
- Assign an issue to the devboxes account. Comments on the issue continue the conversation.
What devboxes sees
devboxes works only in the places you connect, on the projects you choose. It uses AI models, and their output can be wrong, so check the results before you rely on them.
support
-
@devboxes can you pick up
DEV-31? enterprise customers get payment reminders before their grace period is over -
Looked at 4 sources - Read DEV-31 and its comments
- Opened src/dunning/schedule.ts
- Found gracePeriodDays on customers
- Moved DEV-31 to In Review
#52 is up. The first reminder now waits out the customer's grace period, which was already on the customer record. Checks pass and DEV-31 is in review. Jira DEV-31 Payment reminders ignore the enterprise grace period
In Review Dunning
GitHub #52 Respect the contract's grace period before reminding
Open
devboxes/dev-313 checks passedOpened #52
-
-
@devboxes Nina wants the grace period on
#52 in business days, that's how the contracts are written -
Looked at 3 sources - Read Nina's comment on #52
- Found the reminders' calendar
- Ran the tests
Done.
#52 now counts business days with the same calendar the reminders use, and there's a test for a due date right before a weekend. Updated #52
-
Tasks that use Jira
- Turn a customer report into an issue Files the report with the team that owns it, so they start with the cause already found and a fix to try.
- Check whether a customer's problem is a known bug Tells you whether the team already knows about a customer's problem, and adds the new report to the issue that matches.
- Check whether a fix has shipped Tells you whether a customer's fix has shipped and which release first included it.
- Find out whether your product already does something Tells you whether your product already does what a customer is asking for, before you answer them.
- Prepare for a customer's renewal call Lists what a customer reported this year, and whether each report is fixed or open, before you talk to them.
- Scope a feature request into an issue Takes a request customers keep making and turns it into an issue that spells out what would have to change.
- Add acceptance criteria to an issue Adds acceptance criteria to a short issue, so the team builds what was actually meant.
- Split a large feature into smaller issues Breaks a feature that's too big for one change into smaller linked issues the team can take one at a time.
- Size a request before planning Gives you a rough size for a request before it goes into a plan, and says what drives that size.
