Radek Antoniuk

Well, I guess the problem is that package doesn't show up at all: https://atom.io/packages/search?q=space-pen

Just for reference: https://github.com/TypeStrong/ts-node/releases/tag/v10.8.2

I'm currently working on creating a Lambda that will react on S3 changes that would solve this, I'm happy to contribute this back if you wish.

@mrvcmrvc don't worry about SonarCloud, I'll handle that. Just add the tests and it will re ready to go :)

Thanks for reporting this and doing research. Indeed the workaround to disable the resolver should work. For me to try to reproduce this, what Jira version are you connecting to?

How about extending JiraEnvironmentContributingAction + JiraEnvironmentVariableBuilder to provide issue number in ENV from the used AbstractIssueSelector?

1. see https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraEnvironmentContributingAction.java#L14 I would use JIRA_ISSUES_SIZE 2. Yes, the argument for using it multiple times is a valid one. I'm curious what's your use case for this?

1. agreed, if you want to code it then I'm fine :) 2. 👍

@mupakoz ping, are you able to address review comments?

@mupakoz ping? :-)