ctengel / taskmaster Goto Github PK

newtask [-f imp file] [options] [task]
Print IDs

• More complex DB with relationships?
• Real RDBMS vs sqlite
  Split from #4

Endpoint that will show existing due and wakeup dates... bulk move of events
Mostly for auto fill

Create a web based system to interface

Task closure currently indicates completion

Add an API to signify closing without completion

• Should this be DELETE?
• what kind of a paper trail?
• how to do this in CLI?

For basic CLI, see if there is a way to go through all triageable, then all schedulable, etc one by one.

Triage sort of has this already since once triaged a task disappears.

But schedulable doesn't?

https://flask.palletsprojects.com/en/2.0.x/testing/

Split from #3 which is now focused on server-side, and includes the basis for modes/lifecycle

Features

• Urgent Important ABC Frog - just push a key 0/1/2... Timing
• Shift key for filter/sort
• Enter to confirm, escape to cancel

Enablers

• ncurses
• https://github.com/python-cmd2/cmd2
• https://github.com/CITGuru/PyInquirer

Split from #4 (fully API based)

Just basic CRUD so this becomes usable for daily tasks...enhance with #11 later

Multiple timestamped per task

Needed for #20

And if it is does it designate a "warm" "frog"... or an "awake" "frog"... or both?

What,When,Pri,Completed,Notes

User story:
I want to easily take something I GET-ted from one tm instance and POST it directly to another with minimal/no processing on my part.

What's needed:
Modify POST endpoint to accept JSON object payloads with items that normally are not allowed in POST (i.e. ID, etc) and strip/replace the unallowed.

Related:

• Split from #13
• Related to #8
• Will also need import/export CLI to be more useful
• Will allow work/pers projects

• https://flask-restx.readthedocs.io/en/latest/parsing.html
• https://flask-restx.readthedocs.io/en/latest/swagger.html

see some ideas from #9

LOTS of libraries to do more out there

And maybe just use TK or similar...

Give some choices instead of expecting user to always enter a full date string

Related to #10 - basically create templates to deploy on basic infra anywhere

sqllite in permenant places

(not to be confused with #10 )

How to manage offline?

Add ability to search for a task by name and wake it up.

#39 will sort of eliminate some of this need.

Perhaps add search CLI or have search option at bottom of list

In the past, these kinds of projects have been plagued by trying to faithfully import/transform lots of data that is:

• old
• includes many needless tasks
• steeped in old pre-modes mentality
• attempting to be imported without a good user review strategy
• needed to be exported BACK into legacy format
• trying to preserve old features while adding new ones

The current "running" working lists for work and personal are both just basic text files, structured into blocks that maybe have some relevance to project or timeline.

The proposal is build a system that at least basically works - can do everything the text doc could, through the lens of #3 and then gradually bring in those in a semi-automatic, semi-manual fashion.

The importer need not read whole text file and know exactly what to do; however it should be able to read in blocks. So steps here....

1. Do all prereqs #3 #12 #9
2. Select pers or work to import first
3. Reevaluate current state of "running file"
4. Spec out here and develop code to import block at a time
5. Use it and use the list, create and resolve issues as they come, especially where it is inferior to text file
6. Import rest of blocks from that file
7. Repeat for other of pers or work, creating a new issue for that filetype if needed
8. Create an issue or task for major other legacy formats still lying around

• Collect
  • Import
  • Email
  • Write in
  • Recycle from closed
• Triage
  • Dependencies
  • Contexts
  • Count pomorodors
• Schedule
  • Timeline to wake in
  • Stage or not stage
• Stage
  • "warm tasks"
  • cycle back to former sched or triage
• Execute
  • "live tasks"
• Close
  • Recycle

A few ways:

• write or forward an email email to a specific box, tm reads it and adds it as a task
  • next level of this - write an email to request digest, mark complete, etc - i.e. a whole email based UI
• email integration in sense that it monitors user inbox or tied in with email UI and emails can be flagged/labelled to create a task
  • next level - wake up task when another email comes in thread

Allow web API to submit a parameter with either update UUID or timestamp.
If it doesn't match current, reject

User story:
I want a JSON file with my tasks from the API

How:
New export subcommand, either to STDOUT or JSON file

Related to #48 (but can be done in parallel)

• Given a "time since" show all closed
• optionally also in progress
• optional tie in with status report system

DB should probably be UTC... UI should be local

What about API... UTC or local?

Quite challenging right now...reqparse, etc...

Or do we just use flask+marshmellow?

Create a list client library object... For reprioritizing or bulk operations

User story:
I have a JSON file with multiple tasks that I want to import into TM. Maybe it came from another TM instance, maybe I read them from another service, etc.

How:

• Add new import subcommand, which works with a JSON file of one or more tasks
• Leverage #48
• Output one or more task IDs

Log all changes; web API visible

Yes/no confirm before making any changes in CLI