szymonkozak / tempomat Goto Github PK

Idea: smart aliases could use command output as a task number. For example a git alias would load the task number from the current git branch name.

In some Jira configurations (see #30) custom work attributes are required. They could be loaded from a new config file (see #37).

Release should be automated (for example by Github Actions).

Most likely GH actions. As a first step, we can use just for tests and lint in PRs. Sometime in the future, we could add package publishing based on tags.

I've just started using this, and it's working great, but it would be good to be able to be able to have shortcut aliases for more things than just accounts. It would also be useful if more than just yesterday was understood as a date.

• day for 7h30m
• half for 3h45m

Some examples of what I'd like to be able to do:

• tempo log <account> day
• tempo log <account> half tomorrow - to book time for tomorrow
• tempo log <account> day last-tuesday - To book against Tuesday of the previous week
• tempo log <account> day last-tuesday - To book against Tuesday of the previous week
• tempo log <account> half this-tuesday - To book against Tuesday of this week
• tempo log <account> half next-tuesday - To book against Tuesday of next week
• tempo ls this - To list all time this month

Currently, I cannot track the same task with tracker:start, because only one tracker per task is allowed, and tracker:resume doesn't have a possibility to add a description.

Could you allow using multiple trackers for a task (with a unique task and description) or adding a different description when resuming a particular tracker?

Configuration handling needs some love. We should standardize it so it can be easily editable and extensible. One of the propositions we discussed was to use a YAML file.

version: 1
selectedAccount: default
accounts:
  default:
    jiraName: somename
    accountId: 123
    token: 345
    config:
      settings:
        someFlag: true
        defaultRemainingEstimate: 1h
      aliases:
        sm: abc-123
        daily: abc-123
        lunch: abc-321
      attributes:
        _EXTERNALREF_: foo
        _COLOR_: green
  jake:
    jiraName: somename
    accountId: 123
    token: 345
    config:
      settings:
        defaultRemainingEstimate: 1h
      aliases: []
      attributes:
        _EXTERNALREF_: foo
        _COLOR_: green
config:
  settings:
    defaultRemainingEstimate: 0h
  aliases:
    sm: abc-123
    daily: abc-123
    lunch: abc-321
  attributes:
    _EXTERNALREF_: foo
    _COLOR_: green

While it would serve its purpose I'm not the biggest fan of the YAML format. I'd like us to consider TOML or HOCON which in my opinion have better syntaxes.

Can't log the time because some additional fields are required, but can't find the way to add them to the command, hence I'm getting an error:

Failure. Reason: Request failed with status code 400. Errors: Remaining estimate must not be empty, Work attribute 'Activity type' (_Developmentactivities_) is required

Is there a chance that parameters mentioned above would be supported? Also it would be great to calculate remaining estimate automatically when logging time.

Currently, whenever there is an issue with a worklog, I need to delete and recreate it.
It would be great if a worklog could be edited (description, start time, duration, ...) to make it easier to fix typos or mistakes in initial logs.

CLI should provide option to switch between multiple Jira accounts.

It would be nice to be able to find gaps in the 'current period', with a command like tempo gaps. That way I could see what I still need to log time against, and it would be particularly helpful when trying to find an hour I've missed somewhere.

This piggybacks on #5. I often know when something happened relative to today but I'm frustrated that I have to check the date and so on. While #5 is an interesting and cool approach it requires some effort to parse timestamp inputs. I'd like to propose a simpler solution that can be used alternatively.

We could use t+N to determine the date based on today. For example tempo log ABC-123 5h t-3 would log 5 hours 3 days in the past.