Ali-Akber Saifee

Hi, I'm not familiar with `jira-addons`. could you point me to a link ?

@lucianocheng I guess we'd have to add support both in issue creation and issue update

@lucianocheng for creating an issue that has an epic, you could handle it in a similar manner to how issues with parents are created (https://github.com/alisaifee/jira-cli/blob/master/jiracli/bridge/rest.py#L96)

For updating existing issues, something similar to https://github.com/alisaifee/jira-cli/blob/master/jiracli/bridge/rest.py#L158 could work

@lebe-dev : sub-tasks can already be created by using `jira-cli new --type=sub-task --parent=XYZ-123 ...` To list available sub-task types use `jira-cli list subtask_types`

Some background: [coredis](https://github.com/alisaifee/coredis) was actually forked from [aredis](https://github.com/NoneGG/aredis) so that async redis support could be added to `limits`. `aredis` was the only single async redis client that had all the...

Some added context, `aredis` (and thus, `coredis`) was originally picked instead of `aioredis` since the latter did not have cluster support. The async implementation in redis-py is adapted from `aioredis`...

The original design behind the `FixedWindowElasticExpiryRateLimiter` wasn't well thought through at all and I'm actually surprised it's in use. I'd be happy to take a pull request that improves it...

Some minor improvements have been made in the thread safety of the memory storage - however, it's still basically a toy implementation for local development or tests. ~~When using~~

> @alisaifee The second the paragraph in your response above cuts a bit short. Are you saying that memory storage should not be used in production in multi-thread environments? @tuukkamustonen...