Our use of jira.osiam.org (in the core development project)

[Thorsten Roßner]

Hi all,

to provide a common understanding how we use "Epics" on jira.osiam.org I would like to explain quickly how the Jira standard behaviour looks like (as me may switch to it later) and what our current approach is:

First a quick overview of the item hierarchy Jira has:

- Level 1: Version

- Level 2: Epic

- Level 3: Story, Bug, Enhancement, New Feature, Task

- Level 4: Sub-Task

The Jira standard process is to plan a Version that contains serveral Epics. An Epic contains a bunch of Stories (or other level 3 items). While working on a Story you would create Sub-Tasks that certain team members are working on. Once you completed all the Epics in a Version - by completing the contained Level 3 and Level 4 items - you would can publish the Version.

Our process is currently simpler: We ignore level 1 (Version), we use Epics to group stories under a certain topic (like you would do it with labels, but it's more visible using Epics) and we create releases after every sprint.

If you see room for improvement or reasons why we should use the standard process right away please let me know!

Cheers

Thorsten