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.

Get started for free

What you ask

Search Acme

product

2

  1. Lisa

    @devboxes ENG-224 is too big for one go. can you split it into issues the team can pick up one at a time?

  2. devboxes APP

    I'd split it into three: the customer language setting first, then the invoice text and the reminder emails, which both need the setting. Should I file them?

  3. Lisa

    yes please

  4. devboxes APP

    Filed ENG-231, ENG-232 and ENG-233 under ENG-224.

What devboxes does

  1. Read the feature

    • devboxes sums up what the feature asks for.

  2. Map the parts it touches

    • Each part is listed with the change it needs and references to the files.

  3. Agree the split with you

    • You confirm how to split it.

  4. File the linked issues

    • Every issue you confirmed gets filed and linked to the original.

What you get back

Report posted by devboxes

ENG-224, split

  • ENG-231 Add a language setting to the customer, German by default.
  • ENG-232 Move the invoice text into German and English translation files.
  • ENG-233 Do the same for the three reminder emails.

Good for

Startups

More tasks to plan what to build

Ask devboxes to split a large feature into smaller issues

Get started for free