/
Use Cases & Features

Use Cases & Features

DRAFT

Idea

Framing of use cases. Why do they exist instead of (only) plain individual feature configuration?

Why are there still options to configure individual features AND use cases parallelly?

  • Real work does not happen in isolated features, but in end-to-end processes (planning, communication, execution, tracking, reporting)

  • Features describe capabilities. Use cases describe outcomes. Users need solutions no tools.

  • Users are guided and start from their specific work scenario / challenge. And not from individual configuration options which require deep understanding of how to connect them meaningfully.

 

Page content

When you connect Jira with Microsoft 365, you’re not just switching on a set of features. You’re connecting how people actually work across tools.

In practice however, we offer both use cases and individual feature configuration, because they serve different, but equally important needs.

Why both exist

  • Use cases

    • What: Provide “out of the box workflows” that reflect common company scenarios.

    • Benefit: They help you start quickly as each individual use case comes with a predefined set / combination of features tailored to that specific scope of application

    • Example: Depending on the use case you’re selecting, the priority of feature configuration might differ. So for incident management it is more important to have your Teams portal installed rather than setting up your Jira board in Microsoft Teams.

  • Individual features

    • What: Give you full flexibility to tailor the integration to your specific processes, tools, and team setup.

    • Benefit: Configuring our features individually is recommended, if you know how to adjust them successfully and correctly to achieve your desired outcome. This assumes familiarity with our product and your own workflows.

Both approaches are valid.
One focuses on speed and guidance, the other on control and customization.

How to decide what to use

A simple rule of thumb:

  • Start with a use case, if you want to get up and running quickly, explore best practices, or you’re working with a common workflow.

  • Use feature configuration, if you already know exactly what you need, want to fine-tune behavior, or have specific internal processes to match.

  • Combine both when needed: use a use case as your foundation, then adjust individual features to fit your environment.