website-11 Automating Tickets

Ticket · History

October 20, 2026 Created (title: Automating Tickets, status: open, type: enhancement)

Changes

@@ -0,0 +1,10 @@+---+title: Automating Tickets+status: open+type: enhancement+---++Automating the creation of [[Tickets]].++- [x] Obsidian plugin to create them faster+- [ ] Auto-generate the main ticket page, such as [[website-tickets|Website Tickets]], so you only have to create a new ticket (partially complete)

October 20, 2026 Automate history pages

Changes

@@ -7,4 +7,7 @@ Automating the creation of [[Tickets]].  - [x] Obsidian plugin to create them faster-- [ ] Auto-generate the main ticket page, such as [[website-tickets|Website Tickets]], so you only have to create a new ticket (partially complete)+- [ ] Auto-generate the main ticket page, such as [[website-tickets|Website Tickets]], so you only have to create a new ticket (partially complete, it doesn't look super good right now, and the old tickets need migrated to this new format)+++The old manual history pages I think can just be removed, since they will be tracked with git anyway?

October 23, 2026 Edited (status: open → closed)

Changes

@@ -1,13 +1,19 @@ --- title: Automating Tickets-status: open+status: closed type: enhancement ---  Automating the creation of [[Tickets]].  - [x] Obsidian plugin to create them faster-- [ ] Auto-generate the main ticket page, such as [[website-tickets|Website Tickets]], so you only have to create a new ticket (partially complete, it doesn't look super good right now, and the old tickets need migrated to this new format)+- [x] Auto-generate the main ticket page, such as [[website-tickets|Website Tickets]], so you only have to create a new ticket (partially complete, it doesn't look super good right now, and the old tickets need migrated to this new format)   The old manual history pages I think can just be removed, since they will be tracked with git anyway?++## Completed++The main ticket page is now automated, and creating new tickets is very easy.++The main ticket page still looks kinda funky, but this is a separate issue that I don't feel like fixing right now.

October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from website@11.md, title: Automating Tickets → none)
Changes
```
@@ -1,5 +1,4 @@ ----title: Automating Tickets status: closed type: enhancement ---
```
October 24, 2026 Replace ticket status, category and resolution with ticket (status: closed → none)
Changes
```
@@ -1,5 +1,5 @@ ----status: closed+ticket: dismissed type: enhancement --- 
```

October 24, 2026 Edited

Changes

@@ -1,5 +1,5 @@ ----ticket: dismissed+ticket: completed type: enhancement ---

October 24, 2026 Rename tickets pages to <Project> Tickets

Changes

@@ -6,7 +6,7 @@ Automating the creation of [[Tickets]].  - [x] Obsidian plugin to create them faster-- [x] Auto-generate the main ticket page, such as [[website-tickets|Website Tickets]], so you only have to create a new ticket (partially complete, it doesn't look super good right now, and the old tickets need migrated to this new format)+- [x] Auto-generate the main ticket page, such as [[Website Tickets]], so you only have to create a new ticket (partially complete, it doesn't look super good right now, and the old tickets need migrated to this new format)   The old manual history pages I think can just be removed, since they will be tracked with git anyway?

October 24, 2026 Edited

Changes

@@ -8,7 +8,6 @@ - [x] Obsidian plugin to create them faster - [x] Auto-generate the main ticket page, such as [[Website Tickets]], so you only have to create a new ticket (partially complete, it doesn't look super good right now, and the old tickets need migrated to this new format) - The old manual history pages I think can just be removed, since they will be tracked with git anyway?  ## Completed