--- title: "Understanding Project Assignment in BigPicture Classic Project Boxes" canonical: "https://support.appfire.com/space/SUPPORT/3407446111/Understanding%20Project%20Assignment%20in%20BigPicture%20Classic%20Project%20Boxes" format: markdown --- This article explains how project assignment works for **Classic project** boxes in BigPicture Enterprise and clarifies why selecting a box type does not automatically expose a dedicated project mapping setting in the box type configuration. > ℹ️ In BigPicture, a **box type** defines the template and default behavior of a box, while the **data source** for a specific box is configured separately at the individual box level through **Scope definition**. # What was the issue? A customer noticed that when adding a **Classic project** type in Box configuration, there was no visible option to specify which Jira project should be mapped to that box. The main questions were: - Why is project selection not part of that configuration? - How can a project source be added to the box? - Is the list of project types configurable? # How the functionality works BigPicture separates **box type configuration** from **box-level scope configuration**. This distinction is important for understanding the behavior. ## Box type configuration The box type acts as a reusable template. It controls default settings such as: - Available modules - Scheduling mode - General structure and behavior of boxes created from that type It does **not** define the final Jira project source for every future box based on that type. ## Box-level configuration The actual Jira data source is assigned to each individual box. This means the Jira project, board, or filter is selected when the box is created or later updated in that box’s scope settings. > 📝 This design gives administrators more flexibility. Multiple boxes can use the same box type while still being connected to different Jira projects, boards, or JQL filters. # Why there is no project selector in the box type configuration The absence of a project selector in the **Classic project** box type configuration is intentional. The project assignment is not treated as a property of the type itself. Instead, it belongs to the specific box instance. That means: - A box type can be reused many times - Each box created from that type can point to a different Jira source - Administrators do not need to create a separate box type for every project > Think of the box type as a template, and the box itself as the working container where the actual Jira scope is defined. # How to add a project source to a Classic project box You can assign the Jira source in one of two ways. ## Option 1: During box creation When creating a new box, BigPicture provides a **Jira Project** field in the creation dialog. This allows you to associate one or more Jira projects with the box immediately. ## Option 2: After the box is created If the box already exists, you can define or change its source from the box configuration. 1. Open the target box 2. Go to **Box configuration** 3. Open **Tasks** 4. Select **Scope definition** or **Work items from Jira** 5. Add the desired Jira project, board, or saved JQL filter 6. Save the changes You can also access scope management from operational modules such as Gantt or Scope using **Add task → Manage scope definition**. > ℹ️ A box can use more than one Jira source. You can combine multiple projects or use filters to narrow the scope of work items displayed in the box. # What can be used as a box source? A Classic project box is not limited to a single project. Depending on your setup, the scope can be built from different Jira sources: - One Jira project - Multiple Jira projects - A Jira board - A saved JQL filter - A combination of sources, where supported by the configuration This is another reason project assignment is handled at the box level rather than locked into the box type definition. # Is the project type list configurable? Yes. In **BigPicture Enterprise**, box types are configurable, and administrators can create custom box types. This includes the ability to: - Modify existing box types - Create new box types - Adjust default modules and settings for each type To manage box types, go to: **App Settings** (wrench icon) → **Administration** → **Box types** > ✅ BigPicture Enterprise supports extensive box type customization, which makes it possible to tailor the application to different planning, portfolio, and delivery scenarios. # Practical example A company may create a single **Classic project** box type called **Delivery Project**. That type can define the standard modules and planning approach for delivery teams. Then: - Box A can be linked to Jira Project Alpha - Box B can be linked to Jira Project Beta - Box C can be linked to a board that spans several Jira projects All three boxes use the same type, but each has its own scope definition. # Key takeaways - **Box type** defines the template and defaults - **Box scope** defines the actual Jira source - Project mapping is done per box, not in the box type definition - Scope can be configured during box creation or later in **Scope definition** - BigPicture Enterprise allows full customization of box types
FAQ **Can one box be linked to more than one Jira project?** Yes. A box can include multiple Jira projects, depending on how its scope is configured. **Do I need a separate box type for each Jira project?** No. One box type can be reused across many boxes, each with its own Jira source. **Where should I go if I cannot find the project assignment?** Open the specific box and check **Box configuration → Tasks → Scope definition** or **Work items from Jira**. **Can I create my own custom box types?** Yes. In BigPicture Enterprise, custom box types can be created and managed in the administration settings.