Jira

Jira is—with some exceptions—the tool where we track our work, transparently visible to all VSHNeers (and customers via https://control.vshn.net, our customer portal).

Our Jira is available at vshnticket.atlassian.net .

Exceptions from Using Jira

Some specific work (roles) might require other tools to plan and track work.

Examples

The Recruiting Process uses Recruitee
Sales uses the Odoo CRM app
Domain Marketing and Partner Management use the Odoo project and tasks modules

Implications

Before using a different tool than Jira, it’s important to ensure all affected VSHNeers are involved in making this decision.
Any VSHNeer still needs to know Jira and be able to collaborate in Jira with other roles who primarily work in Jira.

How We Use Jira

INFO: How exactly we use Jira is always somewhat in flux and is also used differently between Product and Solution Business teams, as well as by team-independent roles using Jira.

General structure in Jira

Each customer gets a Jira Space (formerly called Project) named "Customer: NAME," with an ID composed of three or four characters, easily associated with the name.
For scoped work, we use the Epic issue type as the parent for all tasks needed to deliver the scope defined in the Epic.
Every solution (one or more per customer) has an Operations issue type as the parent for all isolated tasks such as changes, incidents, improvements, etc., that are NOT part of a defined larger scope (Epic).

Additional documentation