# Feature BNE-30 - Macro: Batch create work packages (size: small-block)

Project: Stream BlockNote extensions
Status: needs clarification
URL: https://community.openproject.org/work_packages/BNE-30

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| BNE-9 | How to decide if an embed is block-level or in-line? | resolved |  |
| BNE-10 | Are project, status, type, ... editable in the creation flow? | rejected |  |
| BNE-11 | How do we deal with required fields? | decided | Show edit form in a modal with required and important fields |
| BNE-41 | Is there a pattern for creating another block after the first? | new |  |

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Documents |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a user  
**I want to** quickly create multiple new work packages from the document and have a rich representation of them in the document.  
**so that** I can take note of multiple tasks without switching from my context.

**Acceptance criteria**

*   Invoke via Slash command
    
    *   TODO: define command and keywords
        
*   If using the &#x27;create work package command&#x27; in a list
    
*   Defaults are set for project (current project), status (?) and type (?)
    
*   Next element (work package) should use project and type from last created element as default
    

**Translation considerations**

*   _Key terms and phrases in the key languages_
