BoxThatBeat / BoxThatBeat/obsidian-agile-task-notes

[Feature] Task Title Parts for Note Naming

Open
#38 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
55
Forks
22
PR merge metrics
No merged PRs in 30d

Description

Currently, the note naming feature supports variables such as {{TASK_ID}}, {{TASK_TYPE}}, {{TASK_STATE}}, {{TASK_ASSIGNEDTO}}, {{TASK_TITLE}} (#34), and {{TASK_TITLEPART_0}}, {{TASK_TITLEPART_1}}, {{TASK_TITLEPART_2}}. However, the {{TASK_TITLEPART_X}} variables default to the whole title if the specified part is empty. This feature request proposes an enhancement to allow more flexible and customizable task title parts.

Proposed Changes:
- Allow users to specify a delimiter (e.g., space, hyphen) to split the task title into parts.
- Provide an option to define a default value for each {{TASK_TITLEPART_X}} if the specified part is empty.
- Add support for more title parts (e.g., {{TASK_TITLEPART_3}}, {{TASK_TITLEPART_4}}, etc.).

Benefits:
- Improved customization and flexibility in note naming.
- Better organization and readability of task notes.
- Enhanced user experience with more control over task title formatting.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the existing note-naming handling for TASK_TITLEPART_0, TASK_TITLEPART_1, and TASK_TITLEPART_2. Review how empty parts currently fall back to the whole title, then define the delimiter, per-part default values, and behavior for additional parts before implementing and testing the expanded naming options.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
content
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.