General FOLIO DevOps

The main “FOLIO DevOps” team attends to the general development operations and infrastructure.

For general assistance, use the Slack channel #devops.

For anything beyond simple assistance, please create a Jira ticket. The DevOps teams are small and busy, so requests will need to be queued.

(The FAQ How to request GitHub user or team access has separate explanations for those tasks.)

To raise Jira tickets, be familiar with the Issue tracker overview and Guidelines.

Use the Jira project key FOLIO.

Set the “Issue type” to be “Task”.

Set the “Development Team” field to be FOLIO DevOps.

Set the “Sprint” field to be “DevOps Requests”.

Do not set “Priority” or “Assignee” or “Labels” or a specific numbered “Sprint”. Those will be handled and scheduled by the team.

Please do not clone old tickets. It just tends to make a mess by applying old settings, and re-sending irrelevant old notifications.

For tickets related to the FOLIO Developers website, do follow the above-mentioned instructions and the additional specific notes.

Rancher scratch environments

The “Kitfox” team attends to the Rancher developer scratch environments.

Be familiar with the FAQ How to get started with Rancher environment.

For general assistance, use the Slack channel #rancher-support and your team-specific channel.

For anything beyond simple assistance, please create a Jira ticket. The DevOps teams are small and busy, so requests will need to be queued.

To raise Jira tickets, be familiar with the Issue tracker overview and Guidelines.

Use the Jira project key RANCHER. (See other tickets.)

Set the “Issue type” to be “Task”.

Set the “Development Team” field to be Kitfox.

Do not set “Priority” or “Assignee” or “Labels” or a specific numbered “Sprint”. Those will be handled and scheduled by the team.