Hi Everyone,
We have a specific business requirement related to task creation and visualization on the Sprint Board. I’d really appreciate guidance or best practices from the community.
Requirement Overview:
We want to enhance the task creation experience directly from the Sprint Board with the following capabilities:
- Task Type Selection During Creation:
- When a user clicks to create a new Task on the Sprint Board, instead of directly creating a standard task, the system should prompt the user to choose between:
- Default Task
- Bug Task (a separate Record Type)
- Based on the selection, the corresponding record type should be assigned automatically.
- When a user clicks to create a new Task on the Sprint Board, instead of directly creating a standard task, the system should prompt the user to choose between:
- Support for Bug Record Type:
- We already plan to configure a separate Record Type (Bug) for Tasks with its own fields, layouts, and validation logic.
- The challenge is integrating this choice seamlessly into the Sprint Board UI.
- Visual Differentiation on Sprint Board:
- Once tasks are created, we want clear color coding (or visual indicators) on the Sprint Board to distinguish:
- Default Tasks
- Bug Tasks
- This should help team members quickly identify and prioritize bug-related work.
- Once tasks are created, we want clear color coding (or visual indicators) on the Sprint Board to distinguish:
Key Questions:
- Is it possible to introduce a record type selection prompt during task creation directly from the Agile Accelerator Sprint Board?
- What would be the recommended approach to implement this? (e.g., Lightning Components, overrides, or customization within Agile Accelerator components)
- How can we implement color coding or UI differentiation on the Sprint Board based on record type?
- Are there any existing extensions, configurations, or known limitations within Agile Accelerator that we should be aware of?
#CRM Configuration
,
The image outlines a common challenge when using the Salesforce
Agile Accelerator managed package: wanting more flexibility than the "out-of-the-box" (OOTB) Sprint Board provides.Since Agile Accelerator is a managed package, its core UI components (like the Sprint Board) are often "locked," meaning you cannot easily inject a custom record type picker directly into the "New Task" button without significant custom development.
Here is a breakdown of how to approach these requirements.
1. Task Type Selection (Record Types)
The Challenge: The "New Task" button on the Agile Accelerator Sprint Board is designed to quickly create a standard Task record. It does not natively trigger the standard Salesforce Record Type selection screen.
Recommended Approaches:
- The "Low-Code" Workaround (Screen Flow): Instead of using the native "New Task" button, create a Global Action or a Quick Action that launches a Screen Flow. The Flow can ask "Is this a Bug?" and then create the task with the correct Record Type. You would place this button in the utility bar or at the top of the page, though it won't live inside the board's white space.
- The "Pro-Code" Approach (LWC Override): You could build a custom Lightning Web Component (LWC) that wraps or replaces the task creation logic. However, since the Sprint Board is part of a managed package, you cannot easily modify the internal "Add" button code. Most teams choose to train users to create Bugs via a separate tab or global action.
2. Visual Differentiation (Color Coding)
The Challenge: The Agile Accelerator Sprint Board has limited styling configurations. It typically displays tasks as uniform cards.
Recommended Approaches:
- Formula Fields with Images: While you can't easily change the background color of the card, you can add a Formula Field to the Task object that displays a small traffic light or icon based on the Record Type (e.g., a red circle for Bugs).
- Implementation: Go to Task Fields -> New Formula (Text) -> Use the IMAGE() function.
- Display: Ensure this field is added to the Compact Layout for Tasks, as Agile Accelerator often pulls fields from there to display on the card.
- Custom CSS (Not Recommended): You could technically use a "Lightning Bolt" or a browser extension to inject CSS to color cards based on text strings, but this is brittle and will break during Salesforce updates.
3. Known Limitations & Considerations
Before you dive into heavy customization, keep these Agile Accelerator constraints in mind:
- Managed Package Constraints: You cannot modify the underlying Apex or Javascript controllers of the Sprint Board. Any "seamless" integration usually requires building a fully custom board, which is a massive undertaking.
- Field Mapping: Ensure that your new "Bug" Record Type still contains the mandatory fields required by Agile Accelerator (like Sprint, Status, and Work) or the tasks won't appear on the board at all.
- Syncing: If you use a separate object for Bugs (instead of just a Record Type on Tasks), they will not show up on the Sprint Board unless you write a trigger to sync them to the Task object. Sticking to Record Types on the Task object is the correct path.
