Many organizations using orbs would most likely want to publish their orbs privately. I assume orbs will be scoped to your GitHub org as namespace? So it would be great if we can publish orbs to foobar/wizzle (assuming GH org foobar), and to have those be only visible to users / jobs within org "foobar" CCI-I-606

As a company we often have parts of our build process that must remain private. It would be nice to be able to share configuration through orbs versus copying and pasting YAML from project to project however, we would not want this in the public registry. Is there or can their be support for hosting a private orb registry. If that is not available, offer private namespaces in the current registry? CCI-I-819

It'd be useful to allow handling lists of values for a parameter, without having to resort to workarounds like parsing comma-separated lists in string types. I think it would be useful to be able to specify something like: steps: - myorb/foo: bar: - baz - qux And have the myorb/foo command called with a bar parameter equal to [ "baz", "qux" ] . CCI-I-701

It would be great if you could "install" an orb on an organisation level.This way you can specify some default values for the orb, fx. api-key/url etc. without having to specify that each time you want to use the orb. CCI-I-1497

I want to be able to define an entire workflow in an orb, using the jobs of my orb and allowing parameters to conditionally choose which jobs to run and allow parameterization of branch and tag filters as well. CCI-I-615

The Jira Orb ( https://circleci.com/orbs/registry/orb/circleci/jira ) notifies on git commits, but it appears GitHub releases are treated similar to tags therefore the Jira Orb can't notify on releases. It does look like the GitHub releases endpoint ( https://developer.github.com/v3/repos/releases/#response ) has a "body" field (description)

Under security settings, we would like to allow certified orbs as well as partner orbs but disallow other orb usage or publishing of orbs. The context is within partners we trust such as Snyk but we want to prevent usage of other orbs without a better way to check they are secure or a way to know where they come from. We understand we can copy/paste the orb source into projects, that is not so usable with hundreds of projects though. CCI-I-1332

https://circleci.com/docs/2.0/configuration-reference/#the-when-attribute While the when attribute can be attached to individual commands, it can not be directly attached to orb commands. The orb would require an additional parameter which would then need to be passed down into each sub-command of that orb command.example: run: name: Upload CodeCov.io Data command: bash <(curl -s https://codecov.io/bash ) -F unittests when: always # Uploads code coverage results, pass or fail namespace/orb: when: always # This is not a valid parameter CCI-I-1360

Add Discord as a method for the chatroom integration feature. CCI-I-826

Notify command no longer works reliably on 2.0 Customers using notify for Phabricator are without a workaround. CCI-I-934