Destinations
A destination is the part of a request type that says where its issues go. It is the one setting a portal cannot work without.
| Field | Required | What it does |
|---|---|---|
| Repository | Yes | The repository the issue is created in. It must be one the GitHub connection covers. |
| Labels | No | Labels applied on creation. Pealboard creates a label that does not exist yet. |
| Project | No | A project the new issue is added to as an item. |
| Initial field values | No | Values set on that project’s fields at creation, for example Status = Triage. |
| Issue type | No | The organization’s issue type, if your organization uses them. |
The portal label
Section titled “The portal label”Every issue a portal creates also carries the label portal:<slug>, added
automatically and not removable from this screen. It is how an engineer looking
at a repository in GitHub can tell which portal an issue came from, and how a
filter in Pealboard finds every issue from one portal.
Choosing a repository
Section titled “Choosing a repository”Pick the repository the engineers who will do the work actually watch. A request cannot be moved to another repository later, because GitHub’s API has no way to move an issue between repositories. If a request lands in the wrong place, close it and ask for a new one, or open a new issue in the right repository and share that issue to the portal.
When a destination is wrong
Section titled “When a destination is wrong”- Repository not in the connection: the submission is refused when the customer sends it, in GitHub’s own words, and nothing is created. Only repositories with sync turned on can be chosen as a destination, so this happens when a repository leaves the GitHub connection after the request type was set up.
- Project deleted in GitHub: the issue is still created, without the project item.
- GitHub refuses the write: the customer sees that the request was not created and is asked to try again. Nothing partial is left behind.
Different destinations for different types
Section titled “Different destinations for different types”That is the normal case. Bug report goes to acme/app with the label bug;
Feature request goes to acme/app with the label enhancement and into the
roadmap project at Status = Triage; Question goes to acme/support.