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
My expectation of this new feature used in this way is that only those JIRA tickets that have been updated since the last time I did a sync would be passed into the formatter code. In the same way if the sync is to fetch-all with the --markdown option, then all JIRA tickets would be regenerated into my designated markdown directory.
The --custom-data-path option should also be available.
The text was updated successfully, but these errors were encountered:
An enhancement I'd like to see is merging the jira-format-issue functionality with the main sync components so that I could do this:
My expectation of this new feature used in this way is that only those JIRA tickets that have been updated since the last time I did a sync would be passed into the formatter code. In the same way if the sync is to fetch-all with the --markdown option, then all JIRA tickets would be regenerated into my designated markdown directory.
The --custom-data-path option should also be available.
The text was updated successfully, but these errors were encountered: