search

srg-kostyrko / obsidian-journal

MIT License
120 stars 7 forks source link

Enhancement of intervall based journals #61

Open Volker-brdb opened 3 months ago

Volker-brdb commented 3 months ago

Hi,

i would love to use intervall based journals in some cases but the way this journal-type uses indexing doesn't fit for me. E.g. talking about sprints. You just can increase index by 1. So if starting with Sprint 1 and letting run for a while you end up by e.g. Sprint 234. Or if choosing yearly reset you get Sprint 1 to Sprint 26 (just example number) each year.

But that's not what I need. For example if the cadence are Releases. Than I need Release1-Sprint1 to Release1-Sprint7 and then next Sprints are called Release2-Sprint1 to Release2-Sprint7. So as you can see there are more increasing numbers than just an index-number at the end as it's implemented now.

Other use-case are Planning-Intervals called PI24-1, PI24-2, PI24-3, PI24-4, PI25-1, PI25-2 and so on. Don't want to use calendar-based quarters here because PIs start-dates don't match with calendar-quarters.

BR Volli

srg-kostyrko commented 3 months ago

If I get correctly second example by - there interval based with 3 month duration and yearly index reset should work Or are there other conditions for it?

as for Release - Sprint example could you please give more context

Volker-brdb commented 3 months ago

If I get correctly second example by - there interval based with 3 month duration and yearly index reset should work

If the interval is in line with the calendar , yes.

Or are there other conditions for it?

Yes, simple example would be if someone want's to plan not along calendar but along his age/life-years. In this case the reset is not at the end of a year but on his birthday.

I could imagine a third option for "index change" here: "reset after x occurences" So as a user you can say "after (e.g.) 4 journal-pages are created reset index"

as for Release - Sprint example could you please give more context

  • is Release duration fixed or it can fluctuate?
  • is there other level possible (like milestone or whatever)
  • how would you invision configuring this? as I don't have a good idea for now
  • same as above: "reset after x occurences"
  • allow more than one index (in all use cases that come to my mind just 2 diffrent index-numbers + "reset after x occurences" would be sufficient.

for the Release-Sprint-example {{journal_name}}{{index1}}Sprint{{index2}} Journal Name: Release Index1= 4711 Index change "increasing" Index2 = 1 Index change "reset after 6 occurences" would lead to:

for the Age-related example above {{journal_name}}{{index1}}-{{index2}} Journal Name: Age Index1= 35 Index change "increasing" Index2 = 1 Index change "reset after 4 occurences" would lead to:

srg-kostyrko commented 3 months ago

thanks for examples

Index1= 35
Index change "increasing"
Index2 = 1
Index change "reset after 4 occurences"

just increasing index in first case won't be enough as it doesn't need to increase with every node (as increasing does) but rather on index3 reset

nevertheless I got the idea and will think on how to better implement it

Volker-brdb commented 3 months ago

oh, yes your right. Thank you for thinking about it