You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently this is pretty difficult because it involves parsing the note itself. If there were optionally (i.e. enabled via configuration) another column to put an issue ID in, then it would make parsing the entries trivial by some script that could push the timesheet to something like JIRA.
The text was updated successfully, but these errors were encountered:
As suggested by @cj123, this could be interpreted when a user adds an entry. For example, a message like the following:
$ tid start "TID-11: Parsing issue IDs"
...could easily be parsed into 2 pieces of information. The ticket ID TID-11 and the actual note Parsing issue IDs.
Of course, other commands would also have to play nice with this. It's probably best when dealing with management commands to actually be able to update the individual pieces of information. For example:
$ tid e u 9f2e00d --note="Parsing ticket numbers" --issue="TID-12"
Currently this is pretty difficult because it involves parsing the note itself. If there were optionally (i.e. enabled via configuration) another column to put an issue ID in, then it would make parsing the entries trivial by some script that could push the timesheet to something like JIRA.
The text was updated successfully, but these errors were encountered: